summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorMark McLoughlin <markmc@redhat.com>2008-12-01 13:57:45 +0000
committerAvi Kivity <avi@redhat.com>2008-12-31 16:55:06 +0200
commit844c7a9ff404d8fc88bb77b06461644621d2c985 (patch)
treebfcb1fb36c1276f8adead47dedaaf12b92f62821
parentefff9e538f6bfa8ee2ca03f7e9a55d98df115186 (diff)
KVM: remove the IRQ ACK notifier assertions
We will obviously never pass a NULL struct kvm_irq_ack_notifier* to this functions. They are always embedded in the assigned device structure, so the assertion add nothing. The irqchip_in_kernel() assertion is very out of place - clearly this little abstraction needs to know nothing about the upper layer details. Signed-off-by: Mark McLoughlin <markmc@redhat.com> Signed-off-by: Avi Kivity <avi@redhat.com>
-rw-r--r--virt/kvm/irq_comm.c3
1 files changed, 0 insertions, 3 deletions
diff --git a/virt/kvm/irq_comm.c b/virt/kvm/irq_comm.c
index 9fbbdea3d1d..973df997ea6 100644
--- a/virt/kvm/irq_comm.c
+++ b/virt/kvm/irq_comm.c
@@ -58,9 +58,6 @@ void kvm_notify_acked_irq(struct kvm *kvm, unsigned gsi)
void kvm_register_irq_ack_notifier(struct kvm *kvm,
struct kvm_irq_ack_notifier *kian)
{
- /* Must be called with in-kernel IRQ chip, otherwise it's nonsense */
- ASSERT(irqchip_in_kernel(kvm));
- ASSERT(kian);
hlist_add_head(&kian->link, &kvm->arch.irq_ack_notifier_list);
}