From: "Michael S. Tsirkin" <mst@redhat.com>
To: Eduardo Habkost <ehabkost@redhat.com>
Cc: "Markus Armbruster" <armbru@redhat.com>,
"Laine Stump" <laine@redhat.com>,
"Daniel P. Berrangé" <berrange@redhat.com>,
"Caio Carrara" <ccarrara@redhat.com>,
"Fabian Deutsch" <fdeutsch@redhat.com>,
qemu-devel@nongnu.org,
"Wainer dos Santos Moschetta" <wainersm@redhat.com>,
Gonglei <arei.gonglei@huawei.com>,
"Gerd Hoffmann" <kraxel@redhat.com>,
"Andrea Bolognani" <abologna@redhat.com>,
"Cleber Rosa" <crosa@redhat.com>,
"Philippe Mathieu-Daudé" <philmd@redhat.com>,
"Marcel Apfelbaum" <marcel.apfelbaum@gmail.com>
Subject: Re: [Qemu-devel] No more chameleon devices (was: [PATCH] virtio: Provide version-specific variants of virtio PCI devices)
Date: Wed, 17 Oct 2018 12:38:29 -0400 [thread overview]
Message-ID: <20181017122840-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <20181017155637.GC31060@habkost.net>
On Wed, Oct 17, 2018 at 12:56:37PM -0300, Eduardo Habkost wrote:
> (CCing Marcel, in case he has extra details on the complex
> Conventional/Express bus/device plugging rules)
>
> On Wed, Oct 17, 2018 at 07:57:39AM +0200, Markus Armbruster wrote:
> > Laine Stump <laine@redhat.com> writes:
> >
> > [...]
> > > In the end, having a device that changed PCI ID depending on what kind
> > > of slot it was plugged into was an idea "too clever for its own good",
> > > should be avoided when new devices are added in the future, and we
> > > should at least provide an alternative that doesn't do that for existing
> > > devices.
> >
> > That means for each chameleon PCI/PCIe device:
> >
> > * create a pair of devices that can only go into one kind of slot
> >
> > * deprecate the chameleon
> >
> > Yes, please! Volunteers?
> >
> > Do we have similar chameleons outside PCI?
>
> I'm worried that we could be trying to address multiple issues at
> the same time, and I'm not sure yet if we should address all of
> them in one take.
>
> Right now we need to differentiate non-transitional and
> transitional virtio devices, for a few reasons:
> * They have different PCI IDs;
> * Legacy drivers don't work with non-transitional devices;
> * Transitional virtio devices can be plugged to Conventional PCI
> buses; non-transitional ones can't.
No that last point isn't true at all.
> This patch addresses that problem.
>
> You seem to be talking about a different issue:
> * Some devices (including transitional virtio) can be plugged on
> both Conventional PCI and PCI Express buses (I will call those
> devices "hybrid PCI devices").
>
> The former is a practical problem: management software needs to
> be able to ask for a transitional virtio device, depending o the
> guest OS being run.
>
> Addressing the latter seems more complex (it would affect other
> devices, not just virtio), and I don't see which practical
> problems it would solve.
>
> I see some problems it wouldn't solve, though: the system
> wouldn't be able to represent the fact that transitional virtio
> devices can still work on PCI Express buses, as long as they
> support PIO bars; or that Conventional PCI devices can be plugged
> to PCI Express root buses.
>
> I don't see problems caused by hybrid conventional/express PCI
> devices. The original problem with virtio devices was just not
> being hybrid, it was lying about being hybrid: non-transitional
> virtio devices are hybrid, but transitional virtio devices
> aren't.
>
> I wouldn't be against abolishing hybrid PCI devices completely if
> somebody volunteers to do the work. I just don't see which
> problems this would solve.
>
> --
> Eduardo
next prev parent reply other threads:[~2018-10-17 16:38 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-13 2:54 [Qemu-devel] [PATCH] virtio: Provide version-specific variants of virtio PCI devices Eduardo Habkost
2018-10-14 21:35 ` Michael S. Tsirkin
2018-10-15 18:14 ` Eduardo Habkost
2018-10-16 8:39 ` Cornelia Huck
2018-10-16 13:32 ` Eduardo Habkost
2018-10-16 15:51 ` Cornelia Huck
2018-10-16 17:02 ` Daniel P. Berrangé
2018-10-16 19:12 ` Laine Stump
2018-10-17 5:57 ` [Qemu-devel] No more chameleon devices (was: [PATCH] virtio: Provide version-specific variants of virtio PCI devices) Markus Armbruster
2018-10-17 6:34 ` Gerd Hoffmann
2018-10-17 11:56 ` [Qemu-devel] No more chameleon devices Markus Armbruster
2018-10-17 15:56 ` [Qemu-devel] No more chameleon devices (was: [PATCH] virtio: Provide version-specific variants of virtio PCI devices) Eduardo Habkost
2018-10-17 16:38 ` Michael S. Tsirkin [this message]
2018-10-17 19:19 ` Eduardo Habkost
2018-10-18 14:11 ` [Qemu-devel] No more chameleon devices Marcel Apfelbaum
2018-10-18 14:15 ` Peter Maydell
2018-10-18 14:38 ` Daniel P. Berrangé
2018-10-18 14:41 ` Peter Maydell
2018-10-18 14:45 ` Marcel Apfelbaum
2018-10-18 14:48 ` Peter Maydell
2018-10-18 15:39 ` Marcel Apfelbaum
2018-10-18 18:07 ` Eduardo Habkost
2018-10-17 10:43 ` [Qemu-devel] [PATCH] virtio: Provide version-specific variants of virtio PCI devices Andrea Bolognani
2018-10-17 15:01 ` Eduardo Habkost
2018-10-17 15:06 ` Michael S. Tsirkin
2018-10-17 15:57 ` Eduardo Habkost
2018-10-18 10:25 ` Andrea Bolognani
2018-10-18 10:27 ` Daniel P. Berrangé
2018-11-14 18:20 ` Eduardo Habkost
2018-10-15 8:16 ` Gerd Hoffmann
2018-10-15 10:27 ` Michael S. Tsirkin
2018-10-15 23:03 ` Eduardo Habkost
2018-10-16 6:48 ` Gerd Hoffmann
2018-10-16 13:39 ` Eduardo Habkost
2018-10-16 18:42 ` Gerd Hoffmann
2018-10-17 5:49 ` [Qemu-devel] "no-user" for properties (was: [PATCH] virtio: Provide version-specific variants of virtio PCI devices) Markus Armbruster
2018-10-15 9:45 ` [Qemu-devel] [PATCH] virtio: Provide version-specific variants of virtio PCI devices Cornelia Huck
2018-10-15 23:32 ` Eduardo Habkost
2018-10-17 9:22 ` Stefan Hajnoczi
2018-10-17 15:10 ` Eduardo Habkost
2018-10-17 15:32 ` Michael S. Tsirkin
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=20181017122840-mutt-send-email-mst@kernel.org \
--to=mst@redhat.com \
--cc=abologna@redhat.com \
--cc=arei.gonglei@huawei.com \
--cc=armbru@redhat.com \
--cc=berrange@redhat.com \
--cc=ccarrara@redhat.com \
--cc=crosa@redhat.com \
--cc=ehabkost@redhat.com \
--cc=fdeutsch@redhat.com \
--cc=kraxel@redhat.com \
--cc=laine@redhat.com \
--cc=marcel.apfelbaum@gmail.com \
--cc=philmd@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=wainersm@redhat.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.