From: Auger Eric <eric.auger@redhat.com>
To: eric.auger.pro@gmail.com, peter.maydell@linaro.org,
alex.williamson@redhat.com, qemu-arm@nongnu.org,
qemu-devel@nongnu.org
Cc: christoffer.dall@linaro.org, agraf@suse.de,
pranavkumar@linaro.org, drjones@redhat.com, wei@redhat.com,
Feng Kan <fkan@apm.com>
Subject: Re: [Qemu-devel] [PATCH RESEND v3 0/3] Generic PCIe host bridge INTx determination for INTx routing
Date: Fri, 1 Sep 2017 09:37:09 +0200 [thread overview]
Message-ID: <ef76ffc0-0303-9227-7b05-0325e443819f@redhat.com> (raw)
In-Reply-To: <1499634139-20399-1-git-send-email-eric.auger@redhat.com>
Hi,
On 09/07/2017 23:02, Eric Auger wrote:
> This series implements INTx to gsi routing for ARM VIRT/Gpex. This is
> a respin of [1] which was lost in limbo.
>
> ARM virt uses GPEX PCIe bridge. This latter does not implement INTx
> to GSI routing. PCIe/INTx assignment works but the consequence is
> irqfd is not used along with INTx interrupts and VFIO INTx handlers
> are executed on userspace leading to an important performance degradation.
>
> This issue is witnessed by the following messages;
>
> qemu-system-aarch64: -device vfio-pci,host=0006:90:00.0: PCI: Bug -
> unimplemented PCI INTx routing (gpex-pcihost)
> qemu-system-aarch64: PCI: Bug - unimplemented PCI INTx routing (gpex-pcihost)
> qemu-system-aarch64: PCI: Bug - unimplemented PCI INTx routing (gpex-pcihost)
>
> So with this series, irqfd is set up for PCIe/INTx passthrough and we get
> the optimal performance. Also we get rid of the above messages.
If I haven't missed anything, I have not received any comment on this
series despite ping and resend since mid June. Now most of the 2.10 rush
is behind, please can anyone have a look?
The BUG message hits when your assign a PF and performance is largely
decreased whenever INTx are used during passthrough.
Thanks
Eric
>
> This series can be found at:
> https://github.com/eauger/qemu/tree/v2.9-gpex-intx-v3
>
> References:
> [1] Generic PCIe host bridge INTx determination for INTx routing
> https://lists.gnu.org/archive/html/qemu-devel/2015-09/msg04975.html
>
>
> Pranavkumar Sawargaonkar (3):
> hw/pci-host/gpex: Set INTx index/gsi mapping
> hw/arm/virt: Set INTx/gsi mapping
> hw/pci-host/gpex: Implement PCI INTx routing
>
> hw/arm/virt.c | 4 ++++
> hw/pci-host/gpex.c | 22 ++++++++++++++++++++++
> include/hw/pci-host/gpex.h | 3 +++
> 3 files changed, 29 insertions(+)
>
next prev parent reply other threads:[~2017-09-01 7:37 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-09 21:02 [Qemu-devel] [PATCH RESEND v3 0/3] Generic PCIe host bridge INTx determination for INTx routing Eric Auger
2017-07-09 21:02 ` [Qemu-devel] [PATCH RESEND v3 1/3] hw/pci-host/gpex: Set INTx index/gsi mapping Eric Auger
2017-09-11 12:41 ` Andrew Jones
2017-07-09 21:02 ` [Qemu-devel] [PATCH RESEND v3 2/3] hw/arm/virt: Set INTx/gsi mapping Eric Auger
2017-09-11 12:42 ` Andrew Jones
2017-07-09 21:02 ` [Qemu-devel] [PATCH RESEND v3 3/3] hw/pci-host/gpex: Implement PCI INTx routing Eric Auger
2017-09-11 12:52 ` Andrew Jones
2017-09-01 7:37 ` Auger Eric [this message]
2017-09-01 14:45 ` [Qemu-devel] [PATCH RESEND v3 0/3] Generic PCIe host bridge INTx determination for " Feng Kan
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=ef76ffc0-0303-9227-7b05-0325e443819f@redhat.com \
--to=eric.auger@redhat.com \
--cc=agraf@suse.de \
--cc=alex.williamson@redhat.com \
--cc=christoffer.dall@linaro.org \
--cc=drjones@redhat.com \
--cc=eric.auger.pro@gmail.com \
--cc=fkan@apm.com \
--cc=peter.maydell@linaro.org \
--cc=pranavkumar@linaro.org \
--cc=qemu-arm@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=wei@redhat.com \
/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).