| commit | 393ad2a4a15db3836698de0e11249b4ec9dafb11 | |
| author | Christian Borntraeger <borntraeger@de.ibm.com> | |
| Mon, 6 Jun 2016 14:57:50 +0000 (6 16:57 +0200) | ||
| committer | Cornelia Huck <cornelia.huck@de.ibm.com> | |
| Tue, 14 Jun 2016 12:00:05 +0000 (14 14:00 +0200) | ||
| tree | e3c198dc788355b3b97fd0ca7539bfe8c06950ff | treesnapshot (tar.gz zip) |
| parent | dcddc75e4756eac166bb002f71dfb09aca9b59fc | commitdiff |
s390x/kvm: Fixup interrupt type for non-adapter I/O interrupts
The current algorithm for I/O interrupts would result in a wrong
interrupt type for subchannel numbers fffe and ffff. In addition
a non adapter interrupt might look like an adapter interrupt for
any subchannel number that has the 0x0400 bit set.
No kernel has ever used the type outside logging - and the logging
was wrong all the time. For everything else the kernel used the
interrupt parameters.
Let's use the KVM_S390_INT_IO macro as for adapter interrupts.
Signed-off-by: Christian Borntraeger <borntraeger@de.ibm.com>
Reviewed-by: David Hildenbrand <dahi@linux.vnet.ibm.com>
Acked-by: Cornelia Huck <cornelia.huck@de.ibm.com>
Signed-off-by: Cornelia Huck <cornelia.huck@de.ibm.com>
The current algorithm for I/O interrupts would result in a wrong
interrupt type for subchannel numbers fffe and ffff. In addition
a non adapter interrupt might look like an adapter interrupt for
any subchannel number that has the 0x0400 bit set.
No kernel has ever used the type outside logging - and the logging
was wrong all the time. For everything else the kernel used the
interrupt parameters.
Let's use the KVM_S390_INT_IO macro as for adapter interrupts.
Signed-off-by: Christian Borntraeger <borntraeger@de.ibm.com>
Reviewed-by: David Hildenbrand <dahi@linux.vnet.ibm.com>
Acked-by: Cornelia Huck <cornelia.huck@de.ibm.com>
Signed-off-by: Cornelia Huck <cornelia.huck@de.ibm.com>
| target-s390x/kvm.c | diffblobblamehistory |