diff options
author | Tony Krowiak <akrowiak@linux.ibm.com> | 2023-08-15 14:43:23 -0400 |
---|---|---|
committer | Heiko Carstens <hca@linux.ibm.com> | 2023-08-18 15:09:28 +0200 |
commit | 7aa7b2a80cb70d528785f06a54d6c8148826006d (patch) | |
tree | a9a4a030bd82754dd146966c87c2ffe4f27bb528 /scripts/gdb/linux/config.py | |
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 <akrowiak@linux.ibm.com>
Suggested-by: Halil Pasic <pasic@linux.ibm.com>
Reviewed-by: Jason J. Herne <jjherne@linux.ibm.com>
Acked-by: Halil Pasic <pasic@linux.ibm.com>
Acked-by: Janosch Frank <frankja@linux.ibm.com>
Tested-by: Viktor Mihajlovski <mihajlov@linux.ibm.com>
Link: https://lore.kernel.org/r/20230815184333.6554-3-akrowiak@linux.ibm.com
Signed-off-by: Heiko Carstens <hca@linux.ibm.com>
Diffstat (limited to 'scripts/gdb/linux/config.py')
0 files changed, 0 insertions, 0 deletions