From: Cornelia Huck <cohuck@redhat.com>
To: "Michael S. Tsirkin" <mst@redhat.com>
Cc: peter.maydell@linaro.org, Andrea Bolognani <abologna@redhat.com>,
Sergio Lopez <slp@redhat.com>,
qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [RFC] virtio-mmio: implement modern (v2) personality (virtio-1)
Date: Thu, 1 Aug 2019 10:18:13 +0200 [thread overview]
Message-ID: <20190801101813.75391e35.cohuck@redhat.com> (raw)
In-Reply-To: <20190731150448-mutt-send-email-mst@kernel.org>
On Wed, 31 Jul 2019 15:06:11 -0400
"Michael S. Tsirkin" <mst@redhat.com> wrote:
> On Wed, Jul 31, 2019 at 03:55:51PM +0200, Cornelia Huck wrote:
> > On Tue, 30 Jul 2019 16:18:52 -0400
> > "Michael S. Tsirkin" <mst@redhat.com> wrote:
> > > Make sure your guests
> > > are all up to date in preparation to the day when legacy will go away.
> >
> > If legacy goes away, legacy guests will be busted anyway :)
>
> It'll take a while for it to go away. But we can try to
> push guests in the direction of coding up modern
> support e.g. by forcing modern by default.
Actually, ccw defaulted to transitional devices right back when we
introduced support for virtio-1 - starting with QEMU 2.5.
I'm not sure how many (if any) supported guest OSs (various variants of
Linux) support virtio-ccw devices in legacy mode only. We can probably
neglect that issue, but I would not really complain if someone
submitted a patch to optionally turn off legacy support for ccw.
next prev parent reply other threads:[~2019-08-01 8:18 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-29 12:57 [Qemu-devel] [RFC] virtio-mmio: implement modern (v2) personality (virtio-1) Sergio Lopez
2019-07-29 13:10 ` no-reply
2019-07-30 7:06 ` Stefan Hajnoczi
2019-07-30 8:34 ` Michael S. Tsirkin
2019-07-31 12:22 ` Sergio Lopez
2019-07-31 19:34 ` Michael S. Tsirkin
2019-07-31 21:22 ` Eduardo Habkost
2019-07-30 10:25 ` Andrea Bolognani
2019-07-30 11:35 ` Cornelia Huck
2019-07-30 12:17 ` Andrea Bolognani
2019-07-30 13:14 ` Cornelia Huck
2019-07-30 20:02 ` Michael S. Tsirkin
2019-07-30 20:18 ` Michael S. Tsirkin
2019-07-31 11:04 ` Sergio Lopez
2019-07-31 13:55 ` Cornelia Huck
2019-07-31 19:06 ` Michael S. Tsirkin
2019-08-01 8:18 ` Cornelia Huck [this message]
2019-07-31 11:02 ` Sergio Lopez
2019-08-01 12:17 ` Michael S. Tsirkin
2019-07-30 16:06 ` Laszlo Ersek
2019-07-31 23:58 ` Paolo Bonzini
2019-08-01 19:45 ` Michael S. Tsirkin
2019-08-02 9:24 ` Paolo Bonzini
2019-08-02 0:26 ` Laszlo Ersek
2019-08-02 9:20 ` Peter Maydell
2019-08-02 22:33 ` Laszlo Ersek
2019-08-01 8:37 ` Sergio Lopez
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=20190801101813.75391e35.cohuck@redhat.com \
--to=cohuck@redhat.com \
--cc=abologna@redhat.com \
--cc=mst@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=slp@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.