On 3/19/21 10:09 AM, Janosch Frank wrote:
On 3/18/21 2:26 PM, Pierre Morel wrote:
When waiting for an interrupt we may need to check the cause of
the interrupt depending on the test case.
Let's provide the tests the possibility to check if the last valid
IRQ received is for the expected instruction.
s/instruction/command/?
Right, instruction may not be the optimal wording.
I/O architecture description have some strange (for me) wording, the
best is certainly to stick on this.
Then I will use "the expected function" here.
We're checking for some value in an IO structure, right?
Instruction makes me expect an actual processor instruction.
Is there another word that can be used to describe what we're checking
here? If yes please also add it to the "pending" variable. "pending_fc"
or "pending_scsw_fc" for example.
Pending is used to specify that the instruction has been accepted but
the according function is still pending, i.e. not finished and will stay
pending for a normal operation until the device active bit is set.
So pending is not the right word, what we check here is the function
control, indicating the function the status refers too.
...snip...
* Only report failures.
*/
-int wait_and_check_io_completion(int schid)
+int wait_and_check_io_completion(int schid, uint32_t pending)
Consequently I will change "pending" with "function_ctrl"
Thanks for forcing clarification
I hope Connie will agree with this :)
Regards,
Pierre
--
Pierre Morel
IBM Lab Boeblingen
