summaryrefslogtreecommitdiffstats
path: root/include/linux/lockd
diff options
context:
space:
mode:
authorMark McLoughlin <markmc@redhat.com>2008-12-02 12:16:33 +0000
committerAvi Kivity <avi@redhat.com>2008-12-31 16:55:47 +0200
commitdefaf1587c5d7dff828f6f11c8941e5bcef00f50 (patch)
treefe4bcf162e203ee80916a5d168d838ef8aa62d25 /include/linux/lockd
parenteb64f1e8cd5c3cae912db30a77d062367f7a11a6 (diff)
downloadop-kernel-dev-defaf1587c5d7dff828f6f11c8941e5bcef00f50.zip
op-kernel-dev-defaf1587c5d7dff828f6f11c8941e5bcef00f50.tar.gz
KVM: fix handling of ACK from shared guest IRQ
If an assigned device shares a guest irq with an emulated device then we currently interpret an ack generated by the emulated device as originating from the assigned device leading to e.g. "Unbalanced enable for IRQ 4347" from the enable_irq() in kvm_assigned_dev_ack_irq(). The fix is fairly simple - don't enable the physical device irq unless it was previously disabled. Of course, this can still lead to a situation where a non-assigned device ACK can cause the physical device irq to be reenabled before the device was serviced. However, being level sensitive, the interrupt will merely be regenerated. Signed-off-by: Mark McLoughlin <markmc@redhat.com> Signed-off-by: Avi Kivity <avi@redhat.com>
Diffstat (limited to 'include/linux/lockd')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud