diff options
author | Tony Krowiak <[email protected]> | 2023-08-15 14:43:23 -0400 |
---|---|---|
committer | Heiko Carstens <[email protected]> | 2023-08-18 15:09:28 +0200 |
commit | 7aa7b2a80cb70d528785f06a54d6c8148826006d (patch) | |
tree | a9a4a030bd82754dd146966c87c2ffe4f27bb528 /lib/memory-notifier-error-inject.c | |
parent | 680b7ddd7e2ab7638d431722432f6d02d75dade1 (diff) |
s390/vfio-ap: clean up irq resources if possible
The architecture does not specify whether interrupts are disabled as part
of the asynchronous reset or upon return from the PQAP/ZAPQ instruction.
If, however, PQAP/ZAPQ completes with APQSW response code 0 and the
interrupt bit in the status word is also 0, we know the interrupts are
disabled and we can go ahead and clean up the corresponding resources;
otherwise, we must wait until the asynchronous reset has completed.
Signed-off-by: Tony Krowiak <[email protected]>
Suggested-by: Halil Pasic <[email protected]>
Reviewed-by: Jason J. Herne <[email protected]>
Acked-by: Halil Pasic <[email protected]>
Acked-by: Janosch Frank <[email protected]>
Tested-by: Viktor Mihajlovski <[email protected]>
Link: https://lore.kernel.org/r/[email protected]
Signed-off-by: Heiko Carstens <[email protected]>
Diffstat (limited to 'lib/memory-notifier-error-inject.c')
0 files changed, 0 insertions, 0 deletions