All of lore.kernel.org
 help / color / mirror / Atom feed
From: Paolo Bonzini <pbonzini@redhat.com>
To: "Michael S. Tsirkin" <mst@redhat.com>, Jan Kiszka <jan.kiszka@web.de>
Cc: qemu-devel <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [PATCH] pci: Don't deliver MSI/MSI-X messages if bus master support is off
Date: Mon, 21 Jul 2014 11:31:13 +0200	[thread overview]
Message-ID: <53CCDDE1.9050206@redhat.com> (raw)
In-Reply-To: <20140720194842.GA2536@redhat.com>

Il 20/07/2014 21:48, Michael S. Tsirkin ha scritto:
> I guess an alternative is for callers to check before
> invoking msi_notify. Please note is this is only option
> when using e.g. irqfd, so this has some advantages.
> Is there a specific device that is affected by this?
> I would expect drivers to disable msi before clearing
> bus master bit ...
> 
>> > ---
>> >  hw/pci/msi.c  | 4 ++++
>> >  hw/pci/msix.c | 4 ++++
>> >  2 files changed, 8 insertions(+)
>> > 
>> > diff --git a/hw/pci/msi.c b/hw/pci/msi.c
>> > index a4a3040..36b651b 100644
>> > --- a/hw/pci/msi.c
>> > +++ b/hw/pci/msi.c
>> > @@ -285,6 +285,10 @@ void msi_notify(PCIDevice *dev, unsigned int vector)
>> >          return;
>> >      }
>> >  
>> > +    if (!(pci_get_word(dev->config + PCI_COMMAND) & PCI_COMMAND_MASTER)) {
>> > +        return;
>> > +    }
>> > +
>> >      msg = msi_get_message(dev, vector);
>> >  
>> >      MSI_DEV_PRINTF(dev,
>> > diff --git a/hw/pci/msix.c b/hw/pci/msix.c
>> > index 5c49bfc..c77ae7d 100644
>> > --- a/hw/pci/msix.c
>> > +++ b/hw/pci/msix.c
>> > @@ -437,6 +437,10 @@ void msix_notify(PCIDevice *dev, unsigned vector)
>> >          return;
>> >      }
>> >  
>> > +    if (!(pci_get_word(dev->config + PCI_COMMAND) & PCI_COMMAND_MASTER)) {
>> > +        return;
>> > +    }
>> > +
>> >      msg = msix_get_message(dev, vector);
>> >  
>> >      stl_le_phys(&address_space_memory, msg.address, msg.data);


I think a better way to do this, is to use the PCI bus master address
space instead of address_space_memory.

Even if it doesn't fix irqfd, it will make the MSI write go through the
IOMMU as it should.

Paolo

      parent reply	other threads:[~2014-07-21  9:31 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-19 16:55 [Qemu-devel] [PATCH] pci: Don't deliver MSI/MSI-X messages if bus master support is off Jan Kiszka
2014-07-20 19:48 ` Michael S. Tsirkin
2014-07-20 21:45   ` Jan Kiszka
2014-07-20 21:03     ` Michael S. Tsirkin
2014-07-20 22:04       ` Jan Kiszka
2014-07-22 19:06         ` Michael S. Tsirkin
2014-07-23  7:55           ` Jan Kiszka
2014-07-21  9:31   ` 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=53CCDDE1.9050206@redhat.com \
    --to=pbonzini@redhat.com \
    --cc=jan.kiszka@web.de \
    --cc=mst@redhat.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 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.