From: "Michael S. Tsirkin" <mst@redhat.com>
To: Marcel Apfelbaum <marcel@redhat.com>
Cc: Alexander Bezzubikov <zuban32s@gmail.com>,
qemu-devel@nongnu.org, Kevin OConnor <kevin@koconnor.net>,
lersek@redhat.com, seabios@seabios.org,
Gerd Hoffmann <kraxel@redhat.com>,
Igor Mammedov <imammedo@redhat.com>,
pbonzini@redhat.com, rth@twiddle.net, ehabkost@redhat.com
Subject: Re: [Qemu-devel] [PATCH v3 2/5] hw/pci: introduce pcie-pci-bridge device
Date: Tue, 1 Aug 2017 18:51:18 +0300 [thread overview]
Message-ID: <20170801184904-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <789fdbb3-73b8-9308-5d94-b3944fd70d03@redhat.com>
On Tue, Aug 01, 2017 at 06:45:13PM +0300, Marcel Apfelbaum wrote:
> On 01/08/2017 18:32, Michael S. Tsirkin wrote:
> > On Mon, Jul 31, 2017 at 09:40:41PM +0300, Alexander Bezzubikov wrote:
> > > > > +typedef struct PCIEPCIBridge {
> > > > > + /*< private >*/
> > > > > + PCIBridge parent_obj;
> > > > > +
> > > > > + bool msi_enable;
> > > >
> > > >
> > > > Please rename the msi_enable property to "msi" in order
> > > > to be aligned with the existent PCIBridgeDev and
> > > > consider making it OnOffAuto for the same reason.
> > > > (I am not sure about the last part though, we have
> > > > no meaning for "auto" here)
> > > >
> > >
> > > Agreed about "msi", but OnOffAuto looks weird to me
> > > as we always want MSI to be enabled.
> >
>
> Hi Michael,
>
> > Why even have a property then? Can't you enable it unconditionally?
> >
>
> Because of a current bug in Linux kernel:
> https://www.spinics.net/lists/linux-pci/msg63052.html
> msi will not work until the patch is merged. Even when
> it will be merged, not all linux kernels will contain the patch.
You should Cc stable to make sure they all gain it eventually.
> Disabling msi is a workaround for the above case.
>
> Thanks,
> Marcel
Really enabling MSI without bus master is a bug that I'm not 100% sure
it even worth working around. But I guess it's not too bad to have a
work-around given it's this simple.
--
MST
next prev parent reply other threads:[~2017-08-01 15:51 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-28 23:37 [Qemu-devel] [PATCH v3 0/5] Generic PCIE-PCI Bridge Aleksandr Bezzubikov
2017-07-28 23:37 ` [Qemu-devel] [PATCH v3 1/5] hw/i386: allow SHPC for Q35 machine Aleksandr Bezzubikov
2017-07-31 11:03 ` Marcel Apfelbaum
2017-08-03 12:52 ` Michael S. Tsirkin
2017-08-03 12:55 ` Alexander Bezzubikov
2017-08-03 13:05 ` Marcel Apfelbaum
2017-07-28 23:37 ` [Qemu-devel] [PATCH v3 2/5] hw/pci: introduce pcie-pci-bridge device Aleksandr Bezzubikov
2017-07-31 11:23 ` Marcel Apfelbaum
2017-07-31 18:40 ` Alexander Bezzubikov
2017-08-01 15:32 ` Michael S. Tsirkin
2017-08-01 15:45 ` Marcel Apfelbaum
2017-08-01 15:51 ` Michael S. Tsirkin [this message]
2017-08-01 15:59 ` Marcel Apfelbaum
2017-07-28 23:37 ` [Qemu-devel] [PATCH v3 3/5] hw/pci: introduce bridge-only vendor-specific capability to provide some hints to firmware Aleksandr Bezzubikov
2017-07-31 11:29 ` Marcel Apfelbaum
2017-07-31 18:43 ` Alexander Bezzubikov
2017-07-28 23:37 ` [Qemu-devel] [PATCH v3 4/5] hw/pci: add QEMU-specific PCI capability to Generic PCI Express Root Port Aleksandr Bezzubikov
2017-07-31 11:43 ` Marcel Apfelbaum
2017-07-31 18:45 ` Alexander Bezzubikov
2017-07-28 23:37 ` [Qemu-devel] [PATCH v3 5/5] docs: update documentation considering PCIE-PCI bridge Aleksandr Bezzubikov
2017-07-31 11:56 ` Marcel Apfelbaum
2017-08-01 20:31 ` Laszlo Ersek
2017-08-01 21:33 ` Alexander Bezzubikov
2017-08-01 21:39 ` Michael S. Tsirkin
2017-08-01 22:23 ` Laszlo Ersek
2017-08-02 12:30 ` Marcel Apfelbaum
2017-08-02 13:47 ` Michael S. Tsirkin
2017-08-02 14:16 ` Laszlo Ersek
2017-08-02 14:21 ` Marcel Apfelbaum
2017-08-02 15:36 ` Marcel Apfelbaum
2017-08-02 16:26 ` Michael S. Tsirkin
2017-08-02 17:58 ` Marcel Apfelbaum
2017-08-03 2:41 ` Laine Stump
2017-08-03 10:29 ` Marcel Apfelbaum
2017-08-03 13:58 ` Laine Stump
2017-08-03 18:59 ` Marcel Apfelbaum
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=20170801184904-mutt-send-email-mst@kernel.org \
--to=mst@redhat.com \
--cc=ehabkost@redhat.com \
--cc=imammedo@redhat.com \
--cc=kevin@koconnor.net \
--cc=kraxel@redhat.com \
--cc=lersek@redhat.com \
--cc=marcel@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=rth@twiddle.net \
--cc=seabios@seabios.org \
--cc=zuban32s@gmail.com \
/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.