From: Alexey Kardashevskiy <aik@ozlabs.ru>
To: qemu-devel@nongnu.org
Cc: Alexey Kardashevskiy <aik@ozlabs.ru>,
qemu-ppc@nongnu.org, Alexander Graf <agraf@suse.de>,
Anthony Liguori <anthony@codemonkey.ws>,
David Gibson <david@gibson.dropbear.id.au>
Subject: [Qemu-devel] [PATCH v5 13/14] xics-kvm: enable irqfd for MSI
Date: Thu, 26 Sep 2013 16:18:47 +1000 [thread overview]
Message-ID: <1380176328-21320-14-git-send-email-aik@ozlabs.ru> (raw)
In-Reply-To: <1380176328-21320-1-git-send-email-aik@ozlabs.ru>
This enables IRQFD support for sPAPR. The feature decreases the latency
of interrupt handling.
To enable IRQFD for MSI, this sets kvm_gsi_direct_mapping to true which
enables direct MSI mapping.
To enable IRQFD for LSI (level triggered INTx interrupts), a PCI host bus
callback is required. The patch for that is coming next.
Signed-off-by: Alexey Kardashevskiy <aik@ozlabs.ru>
---
hw/intc/xics_kvm.c | 6 ++++++
1 file changed, 6 insertions(+)
diff --git a/hw/intc/xics_kvm.c b/hw/intc/xics_kvm.c
index a2ccafa..c203646 100644
--- a/hw/intc/xics_kvm.c
+++ b/hw/intc/xics_kvm.c
@@ -441,6 +441,12 @@ static void xics_kvm_realize(DeviceState *dev, Error **errp)
goto fail;
}
}
+
+ kvm_kernel_irqchip = true;
+ kvm_irqfds_allowed = true;
+ kvm_msi_via_irqfd_allowed = true;
+ kvm_gsi_direct_mapping = true;
+
return;
fail:
--
1.8.4.rc4
next prev parent reply other threads:[~2013-09-26 6:19 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-26 6:18 [Qemu-devel] [PATCH v5 00/14] xics: reworks and in-kernel support Alexey Kardashevskiy
2013-09-26 6:18 ` [Qemu-devel] [PATCH v5 01/14] target-ppc: Add helper for KVM_PPC_RTAS_DEFINE_TOKEN Alexey Kardashevskiy
2013-09-27 4:54 ` David Gibson
2013-09-26 6:18 ` [Qemu-devel] [PATCH v5 02/14] xics: move reset and cpu_setup Alexey Kardashevskiy
2013-09-27 5:05 ` David Gibson
2013-09-26 6:18 ` [Qemu-devel] [PATCH v5 03/14] spapr: move cpu_setup after kvmppc_set_papr Alexey Kardashevskiy
2013-09-27 5:15 ` David Gibson
2013-09-26 6:18 ` [Qemu-devel] [PATCH v5 04/14] xics: replace fprintf with error_report Alexey Kardashevskiy
2013-09-27 5:15 ` David Gibson
2013-09-26 6:18 ` [Qemu-devel] [PATCH v5 05/14] xics: add pre_save/post_load dispatchers Alexey Kardashevskiy
2013-10-02 8:23 ` David Gibson
2013-09-26 6:18 ` [Qemu-devel] [PATCH v5 06/14] xics: convert init() to realize() Alexey Kardashevskiy
2013-09-26 6:18 ` [Qemu-devel] [PATCH v5 07/14] xics: add missing const specifiers to TypeInfo Alexey Kardashevskiy
2013-09-26 6:18 ` [Qemu-devel] [PATCH v5 08/14] xics: split to xics and xics-common Alexey Kardashevskiy
2013-09-26 6:18 ` [Qemu-devel] [PATCH v5 09/14] xics: add cpu_setup callback Alexey Kardashevskiy
2013-09-26 6:18 ` [Qemu-devel] [PATCH v5 10/14] xics-kvm: Support for in-kernel XICS interrupt controller Alexey Kardashevskiy
2013-09-26 6:18 ` [Qemu-devel] [PATCH v5 11/14] xics: Implement H_IPOLL Alexey Kardashevskiy
2013-09-26 6:18 ` [Qemu-devel] [PATCH v5 12/14] xics: Implement H_XIRR_X Alexey Kardashevskiy
2013-09-26 6:18 ` Alexey Kardashevskiy [this message]
2013-09-26 6:18 ` [Qemu-devel] [PATCH v5 14/14] spapr-pci: enable irqfd for INTx Alexey Kardashevskiy
2013-09-30 17:31 ` [Qemu-devel] [PATCH v5 00/14] xics: reworks and in-kernel support Alexander Graf
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1380176328-21320-14-git-send-email-aik@ozlabs.ru \
--to=aik@ozlabs.ru \
--cc=agraf@suse.de \
--cc=anthony@codemonkey.ws \
--cc=david@gibson.dropbear.id.au \
--cc=qemu-devel@nongnu.org \
--cc=qemu-ppc@nongnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).