From: Marc Zyngier <maz@kernel.org>
To: Lorenzo Pieralisi <lorenzo.pieralisi@arm.com>
Cc: kvm@vger.kernel.org, Will Deacon <will@kernel.org>,
Julien Thierry <julien.thierry.kdev@gmail.com>,
Jean-Philippe Brucker <jean-philippe@linaro.org>,
Andre Przywara <andre.przywara@arm.com>,
Alexandru Elisei <alexandru.elisei@arm.com>
Subject: Re: [PATCH kvmtool] vfio: fix multi-MSI vector handling
Date: Fri, 24 Apr 2020 14:54:37 +0100 [thread overview]
Message-ID: <dcae31aedd7286e5679ca570a1149f27@kernel.org> (raw)
In-Reply-To: <20200424134024.12543-1-lorenzo.pieralisi@arm.com>
Hi Lorenzo,
On 2020-04-24 14:40, Lorenzo Pieralisi wrote:
> A PCI device with a MSI capability enabling Multiple MSI messages
> (through the Multiple Message Enable field in the Message Control
> register[6:4]) is expected to drive the Message Data lower bits (number
> determined by the number of selected vectors) to generate the
> corresponding MSI messages writes on the PCI bus.
>
> Therefore, KVM expects the MSI data lower bits (a number of
> bits that depend on bits [6:4] of the Message Control
> register - which in turn control the number of vectors
> allocated) to be set-up by kvmtool while programming the
> MSI IRQ routing entries to make sure the MSI entries can
> actually be demultiplexed by KVM and IRQ routes set-up
> accordingly so that when an actual HW fires KVM can
> route it to the correct entry in the interrupt controller
> (and set-up a correct passthrough route for directly
> injected interrupt).
>
> Current kvmtool code does not set-up Message data entries
> correctly for multi-MSI vectors - the data field is left
> as programmed in the MSI capability by the guest for all
> vector entries, triggering IRQs misrouting.
>
> Fix it.
>
> Signed-off-by: Lorenzo Pieralisi <lorenzo.pieralisi@arm.com>
> Cc: Will Deacon <will@kernel.org>
> Cc: Julien Thierry <julien.thierry.kdev@gmail.com>
> ---
> vfio/pci.c | 6 ++++++
> 1 file changed, 6 insertions(+)
>
> diff --git a/vfio/pci.c b/vfio/pci.c
> index 76e24c1..b43e522 100644
> --- a/vfio/pci.c
> +++ b/vfio/pci.c
> @@ -434,6 +434,12 @@ static void vfio_pci_msi_cap_write(struct kvm
> *kvm, struct vfio_device *vdev,
>
> for (i = 0; i < nr_vectors; i++) {
> entry = &pdev->msi.entries[i];
> +
> + if (nr_vectors > 1) {
> + msg.data &= ~(nr_vectors - 1);
> + msg.data |= i;
> + }
> +
This matches my own understanding of how MultiMSI works.
Small nit: you don't need to check the condition for the number
of vectors, as this expression is valid for any nr_vectors
that is a power of 2 (as required by the spec).
> entry->config.msg = msg;
> vfio_pci_update_msi_entry(kvm, vdev, entry);
> }
FWIW:
Acked-by: Marc Zyngier <maz@kernel.org>
M.
--
Jazz is not dead. It just smells funny...
next prev parent reply other threads:[~2020-04-24 13:54 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-24 13:40 [PATCH kvmtool] vfio: fix multi-MSI vector handling Lorenzo Pieralisi
2020-04-24 13:54 ` Marc Zyngier [this message]
2020-04-24 15:00 ` Will Deacon
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=dcae31aedd7286e5679ca570a1149f27@kernel.org \
--to=maz@kernel.org \
--cc=alexandru.elisei@arm.com \
--cc=andre.przywara@arm.com \
--cc=jean-philippe@linaro.org \
--cc=julien.thierry.kdev@gmail.com \
--cc=kvm@vger.kernel.org \
--cc=lorenzo.pieralisi@arm.com \
--cc=will@kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.