From: "Michael S. Tsirkin" <mst@redhat.com>
To: Alex Williamson <alex.williamson@redhat.com>
Cc: jan.kiszka@siemens.com, qemu-devel@nongnu.org, qemu-stable@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] pci-assign: Enable MSIX on device to match guest
Date: Thu, 20 Dec 2012 18:38:58 +0200 [thread overview]
Message-ID: <20121220163858.GB316@redhat.com> (raw)
In-Reply-To: <20121220160107.3975.53264.stgit@bling.home>
On Thu, Dec 20, 2012 at 09:05:50AM -0700, Alex Williamson wrote:
> When a guest enables MSIX on a device we evaluate the MSIX vector
> table, typically find no unmasked vectors and don't switch the device
> to MSIX mode. This generally works fine and the device will be
> switched once the guest enables and therefore unmasks a vector.
> Unfortunately some drivers enable MSIX, then use interfaces to send
> commands between VF & PF or PF & firmware that act based on the host
> state of the device. These therefore break when MSIX is managed
> lazily. This change re-enables the previous test used to enable MSIX
> (see qemu-kvm a6b402c9), which basically guesses whether a vector
> will be used based on the data field of the vector table.
>
> Cc: qemu-stable@nongnu.org
> Signed-off-by: Alex Williamson <alex.williamson@redhat.com>
Same question: can't we enable and mask MSIX through config sysfs?
In this case it can be done in userspace ...
> ---
> hw/kvm/pci-assign.c | 17 +++++++++++++++--
> 1 file changed, 15 insertions(+), 2 deletions(-)
>
> I think we might be able to do a little better than this, but I think
> this is the right fix for stable and we can build on it to perhaps only
> enable a single vector.
>
> diff --git a/hw/kvm/pci-assign.c b/hw/kvm/pci-assign.c
> index e80dad0..12a219b 100644
> --- a/hw/kvm/pci-assign.c
> +++ b/hw/kvm/pci-assign.c
> @@ -1025,6 +1025,19 @@ static bool assigned_dev_msix_masked(MSIXTableEntry *entry)
> return (entry->ctrl & cpu_to_le32(0x1)) != 0;
> }
>
> +/*
> + * When MSI-X is first enabled the vector table typically has all the
> + * vectors masked, so we can't use that as the obvious test to figure out
> + * how many vectors to initially enable. Instead we look at the data field
> + * because this is what worked for pci-assign for a long time. This makes
> + * sure the physical MSI-X state tracks the guest's view, which is important
> + * for some VF/PF and PF/fw communication channels.
> + */
> +static bool assigned_dev_msix_skipped(MSIXTableEntry *entry)
> +{
> + return !entry->data;
> +}
> +
> static int assigned_dev_update_msix_mmio(PCIDevice *pci_dev)
> {
> AssignedDevice *adev = DO_UPCAST(AssignedDevice, dev, pci_dev);
> @@ -1035,7 +1048,7 @@ static int assigned_dev_update_msix_mmio(PCIDevice *pci_dev)
>
> /* Get the usable entry number for allocating */
> for (i = 0; i < adev->msix_max; i++, entry++) {
> - if (assigned_dev_msix_masked(entry)) {
> + if (assigned_dev_msix_skipped(entry)) {
> continue;
> }
> entries_nr++;
> @@ -1064,7 +1077,7 @@ static int assigned_dev_update_msix_mmio(PCIDevice *pci_dev)
> for (i = 0; i < adev->msix_max; i++, entry++) {
> adev->msi_virq[i] = -1;
>
> - if (assigned_dev_msix_masked(entry)) {
> + if (assigned_dev_msix_skipped(entry)) {
> continue;
> }
>
next prev parent reply other threads:[~2012-12-20 16:36 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-20 16:05 [Qemu-devel] [PATCH] pci-assign: Enable MSIX on device to match guest Alex Williamson
2012-12-20 16:38 ` Michael S. Tsirkin [this message]
2012-12-20 22:15 ` Alex Williamson
2012-12-21 12:17 ` Michael S. Tsirkin
2012-12-21 15:46 ` Alex Williamson
2013-01-02 15:49 ` Alex Williamson
2013-01-06 13:23 ` Michael S. Tsirkin
2013-01-06 15:57 ` Alex Williamson
2013-01-07 15:02 ` Michael S. Tsirkin
2013-01-07 15:09 ` Alex Williamson
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=20121220163858.GB316@redhat.com \
--to=mst@redhat.com \
--cc=alex.williamson@redhat.com \
--cc=jan.kiszka@siemens.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-stable@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 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.