From: Paolo Bonzini <pbonzini@redhat.com>
To: "Michael S. Tsirkin" <mst@redhat.com>, Peter Xu <peterx@redhat.com>
Cc: qemu-devel@nongnu.org, jan.kiszka@siemens.com,
qemu-stable@nongnu.org, alex.williamson@redhat.com,
changlimin@h3c.com
Subject: Re: [Qemu-devel] [PATCH v2] pci-assign: sync MSI/MSI-X cap and table with PCIDevice
Date: Mon, 28 Nov 2016 15:09:42 +0100 [thread overview]
Message-ID: <2a94553d-86ab-dbaf-fadb-442c8d40b8a1@redhat.com> (raw)
In-Reply-To: <20161125190447-mutt-send-email-mst@kernel.org>
On 25/11/2016 18:05, Michael S. Tsirkin wrote:
> On Fri, Nov 25, 2016 at 10:55:22AM +0800, Peter Xu wrote:
>> Since commit e1d4fb2d ("kvm-irqchip: x86: add msi route notify fn"),
>> kvm_irqchip_add_msi_route() starts to use pci_get_msi_message() to fetch
>> MSI info. This requires that we setup MSI related fields in PCIDevice.
>> For most devices, that won't be a problem, as long as we are using
>> general interfaces like msi_init()/msix_init().
>>
>> However, for pci-assign devices, MSI/MSI-X is treated differently - PCI
>> assign devices are maintaining its own MSI table and cap information in
>> AssignedDevice struct. however that's not synced up with PCIDevice's
>> fields. That will leads to pci_get_msi_message() failed to find correct
>> MSI capability, even with an NULL msix_table.
>>
>> A quick fix is to sync up the two places: both the capability bits and
>> table address for MSI/MSI-X.
>>
>> Reported-by: Changlimin <changlimin@h3c.com>
>> Tested-by: Changlimin <changlimin@h3c.com>
>> Cc: qemu-stable@nongnu.org
>> Fixes: e1d4fb2d ("kvm-irqchip: x86: add msi route notify fn")
>> Signed-off-by: Peter Xu <peterx@redhat.com>
>
>
> Reviewed-by: Michael S. Tsirkin <mst@redhat.com>
>
> Paolo, want to pick this up?
Yes.
Paolo
>
>> ---
>> Do we still support pci-assign?
>>
>> v2:
>> - add (uint8_t *) for msix_table assignment [Limin]
>> ---
>> hw/i386/kvm/pci-assign.c | 4 ++++
>> 1 file changed, 4 insertions(+)
>>
>> diff --git a/hw/i386/kvm/pci-assign.c b/hw/i386/kvm/pci-assign.c
>> index 8238fbc..87dcbdd 100644
>> --- a/hw/i386/kvm/pci-assign.c
>> +++ b/hw/i386/kvm/pci-assign.c
>> @@ -1251,6 +1251,7 @@ static int assigned_device_pci_cap_init(PCIDevice *pci_dev, Error **errp)
>> error_propagate(errp, local_err);
>> return -ENOTSUP;
>> }
>> + dev->dev.cap_present |= QEMU_PCI_CAP_MSI;
>> dev->cap.available |= ASSIGNED_DEVICE_CAP_MSI;
>> /* Only 32-bit/no-mask currently supported */
>> ret = pci_add_capability2(pci_dev, PCI_CAP_ID_MSI, pos, 10,
>> @@ -1285,6 +1286,7 @@ static int assigned_device_pci_cap_init(PCIDevice *pci_dev, Error **errp)
>> error_propagate(errp, local_err);
>> return -ENOTSUP;
>> }
>> + dev->dev.cap_present |= QEMU_PCI_CAP_MSIX;
>> dev->cap.available |= ASSIGNED_DEVICE_CAP_MSIX;
>> ret = pci_add_capability2(pci_dev, PCI_CAP_ID_MSIX, pos, 12,
>> &local_err);
>> @@ -1648,6 +1650,7 @@ static void assigned_dev_register_msix_mmio(AssignedDevice *dev, Error **errp)
>> dev->msix_table = NULL;
>> return;
>> }
>> + dev->dev.msix_table = (uint8_t *)dev->msix_table;
>>
>> assigned_dev_msix_reset(dev);
>>
>> @@ -1665,6 +1668,7 @@ static void assigned_dev_unregister_msix_mmio(AssignedDevice *dev)
>> error_report("error unmapping msix_table! %s", strerror(errno));
>> }
>> dev->msix_table = NULL;
>> + dev->dev.msix_table = NULL;
>> }
>>
>> static const VMStateDescription vmstate_assigned_device = {
>> --
>> 2.7.4
>>
prev parent reply other threads:[~2016-11-28 14:09 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-25 2:55 [Qemu-devel] [PATCH v2] pci-assign: sync MSI/MSI-X cap and table with PCIDevice Peter Xu
2016-11-25 17:05 ` Michael S. Tsirkin
2016-11-28 14:09 ` Paolo Bonzini [this message]
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=2a94553d-86ab-dbaf-fadb-442c8d40b8a1@redhat.com \
--to=pbonzini@redhat.com \
--cc=alex.williamson@redhat.com \
--cc=changlimin@h3c.com \
--cc=jan.kiszka@siemens.com \
--cc=mst@redhat.com \
--cc=peterx@redhat.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 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).