summaryrefslogtreecommitdiffstats
path: root/virt/kvm/irq_comm.c
diff options
context:
space:
mode:
authorMichael S. Tsirkin <mst@redhat.com>2010-01-13 18:58:09 +0200
committerMarcelo Tosatti <mtosatti@redhat.com>2010-01-25 12:26:37 -0200
commitf1d1c309f35e9b0fb961cffd70fbd04f450ec47c (patch)
treeb616c8bcd1d453c8dc4fcc5b927cc4a4f8a7e207 /virt/kvm/irq_comm.c
parent82b7005f0e72d8d1a8226e4c192cbb0850d10b3f (diff)
downloadop-kernel-dev-f1d1c309f35e9b0fb961cffd70fbd04f450ec47c.zip
op-kernel-dev-f1d1c309f35e9b0fb961cffd70fbd04f450ec47c.tar.gz
KVM: only allow one gsi per fd
Looks like repeatedly binding same fd to multiple gsi's with irqfd can use up a ton of kernel memory for irqfd structures. A simple fix is to allow each fd to only trigger one gsi: triggering a storm of interrupts in guest is likely useless anyway, and we can do it by binding a single gsi to many interrupts if we really want to. Cc: stable@kernel.org Signed-off-by: Michael S. Tsirkin <mst@redhat.com> Acked-by: Acked-by: Gregory Haskins <ghaskins@novell.com> Signed-off-by: Avi Kivity <avi@redhat.com>
Diffstat (limited to 'virt/kvm/irq_comm.c')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud