From: "Michael S. Tsirkin" <mst@redhat.com>
To: Anthony Liguori <anthony@codemonkey.ws>
Cc: jan.kiszka@siemens.com,
Alex Williamson <alex.williamson@redhat.com>,
qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH v2] pci-assign: Add MSI affinity support
Date: Mon, 20 May 2013 16:15:49 +0300 [thread overview]
Message-ID: <20130520131549.GA11716@redhat.com> (raw)
In-Reply-To: <87k3mtke5f.fsf@codemonkey.ws>
On Mon, May 20, 2013 at 07:51:40AM -0500, Anthony Liguori wrote:
> "Michael S. Tsirkin" <mst@redhat.com> writes:
>
> > On Mon, May 13, 2013 at 02:20:02PM -0600, Alex Williamson wrote:
> >> To support guest MSI affinity changes update the MSI message any time
> >> the guest writes to the address or data fields.
> >>
> >> Signed-off-by: Alex Williamson <alex.williamson@redhat.com>
> >
> > Seems the only way we can fix this for 1.5.
> >
> > Acked-by: Michael S. Tsirkin <mst@redhat.com>
>
> Is this a bug or a feature? Can someone describe the scenario in which
> the bug occurs?
>
> Regards,
>
> Anthony Liguori
It's a bug. Here's how it occurs w.g. with a linux guest:
- guest kernel enables MSI, interrupts are sent to CPU0
- irqbalance runs in guest and moves MSI to CPU1
- guest kernel updates MSI register with new data
without this patch interrupts keep getting sent to CPU0
in violation of the spec.
> >
> >> ---
> >>
> >> v2: Don't cache MSIMessage
> >>
> >> hw/i386/kvm/pci-assign.c | 18 ++++++++++++++++++
> >> 1 file changed, 18 insertions(+)
> >>
> >> diff --git a/hw/i386/kvm/pci-assign.c b/hw/i386/kvm/pci-assign.c
> >> index c1e08ec..ff85590 100644
> >> --- a/hw/i386/kvm/pci-assign.c
> >> +++ b/hw/i386/kvm/pci-assign.c
> >> @@ -1026,6 +1026,21 @@ static void assigned_dev_update_msi(PCIDevice *pci_dev)
> >> }
> >> }
> >>
> >> +static void assigned_dev_update_msi_msg(PCIDevice *pci_dev)
> >> +{
> >> + AssignedDevice *assigned_dev = DO_UPCAST(AssignedDevice, dev, pci_dev);
> >> + uint8_t ctrl_byte = pci_get_byte(pci_dev->config + pci_dev->msi_cap +
> >> + PCI_MSI_FLAGS);
> >> +
> >> + if (assigned_dev->assigned_irq_type != ASSIGNED_IRQ_MSI ||
> >> + !(ctrl_byte & PCI_MSI_FLAGS_ENABLE)) {
> >> + return;
> >> + }
> >> +
> >> + kvm_irqchip_update_msi_route(kvm_state, assigned_dev->msi_virq[0],
> >> + msi_get_message(pci_dev, 0));
> >> +}
> >> +
> >> static bool assigned_dev_msix_masked(MSIXTableEntry *entry)
> >> {
> >> return (entry->ctrl & cpu_to_le32(0x1)) != 0;
> >> @@ -1201,6 +1216,9 @@ static void assigned_dev_pci_write_config(PCIDevice *pci_dev, uint32_t address,
> >> if (range_covers_byte(address, len,
> >> pci_dev->msi_cap + PCI_MSI_FLAGS)) {
> >> assigned_dev_update_msi(pci_dev);
> >> + } else if (ranges_overlap(address, len, /* 32bit MSI only */
> >> + pci_dev->msi_cap + PCI_MSI_ADDRESS_LO, 6)) {
> >> + assigned_dev_update_msi_msg(pci_dev);
> >> }
> >> }
> >> if (assigned_dev->cap.available & ASSIGNED_DEVICE_CAP_MSIX) {
next prev parent reply other threads:[~2013-05-20 13:15 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-13 20:20 [Qemu-devel] [PATCH v2] pci-assign: Add MSI affinity support Alex Williamson
2013-05-19 14:00 ` Michael S. Tsirkin
2013-05-20 12:51 ` Anthony Liguori
2013-05-20 13:15 ` Michael S. Tsirkin [this message]
2013-05-22 22:59 ` Anthony Liguori
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=20130520131549.GA11716@redhat.com \
--to=mst@redhat.com \
--cc=alex.williamson@redhat.com \
--cc=anthony@codemonkey.ws \
--cc=jan.kiszka@siemens.com \
--cc=qemu-devel@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).