From: Gerd Hoffmann <kraxel@redhat.com>
To: Ladi Prosek <lprosek@redhat.com>, "Michael S. Tsirkin" <mst@redhat.com>
Cc: Yan Vugenfirer <yvugenfi@redhat.com>,
qemu-devel <qemu-devel@nongnu.org>,
Vadim Rozenfeld <vrozenfe@redhat.com>
Subject: Re: [Qemu-devel] [PATCH] virtio-pci: Don't force Subsystem Vendor ID = Vendor ID
Date: Mon, 06 Nov 2017 10:18:07 +0100 [thread overview]
Message-ID: <1509959887.30277.8.camel@redhat.com> (raw)
In-Reply-To: <CABdb734DG_itxuUjCiANz_ps+j5EdJj287HXrd8Xa_akyGAsaA@mail.gmail.com>
Hi,
> > So in my humble opinion the right thing for people to do is simply
> > to
> > avoid legacy devices. Is something preventing that?
>
> The same reasons why the concept of transitional devices exists at
> all?
We discussing future driver versions running on future qemu versions,
so we should have virtio 1.0 support on both ends. So IMO the question
isn't that silly ...
But by default qemu uses transitional by default for non-express
devices, i.e. for all i440fx machines types. Which implies virtio-
legacy compatible pci ids.
If we want change this we need a transitional/modern virtio config
switch. Not only in qemu, but for the whole management stack too.
I don't think it is a good idea to go that route.
cheers,
Gerd
next prev parent reply other threads:[~2017-11-06 9:18 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-02 13:31 [Qemu-devel] [PATCH] virtio-pci: Don't force Subsystem Vendor ID = Vendor ID Ladi Prosek
2017-11-02 14:52 ` Michael S. Tsirkin
2017-11-03 6:25 ` Ladi Prosek
2017-11-03 7:20 ` Gerd Hoffmann
2017-11-03 8:23 ` Ladi Prosek
2017-11-03 8:44 ` Vadim Rozenfeld
2017-11-03 15:11 ` Michael S. Tsirkin
2017-11-06 9:02 ` Ladi Prosek
2017-11-06 9:18 ` Gerd Hoffmann [this message]
2017-11-06 16:53 ` Michael S. Tsirkin
2017-11-06 16:51 ` Michael S. Tsirkin
2017-11-07 8:30 ` Ladi Prosek
2017-11-03 15:03 ` 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=1509959887.30277.8.camel@redhat.com \
--to=kraxel@redhat.com \
--cc=lprosek@redhat.com \
--cc=mst@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=vrozenfe@redhat.com \
--cc=yvugenfi@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 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).