From: Peter Maydell <peter.maydell@linaro.org>
To: Laszlo Ersek <lersek@redhat.com>
Cc: Paolo Bonzini <pbonzini@redhat.com>,
qemu-devel <qemu-devel@nongnu.org>,
Sergio Lopez Pascual <slp@redhat.com>,
"Michael S. Tsirkin" <mst@redhat.com>
Subject: Re: [Qemu-devel] [RFC] virtio-mmio: implement modern (v2) personality (virtio-1)
Date: Fri, 2 Aug 2019 10:20:17 +0100 [thread overview]
Message-ID: <CAFEAcA9fHPpsvwXeKMnUbbHYu_=F+v+SF9ttAm+vOcXOmPVhMA@mail.gmail.com> (raw)
In-Reply-To: <9b2acff6-8c6d-3aa0-8020-d6d831222496@redhat.com>
On Fri, 2 Aug 2019 at 01:26, Laszlo Ersek <lersek@redhat.com> wrote:
> But it's extra work, not entirely risk-free (regressions), and I can't
> tell if someone out there still uses virtio-mmio (despite me thinking
> that would be unreasonable). I wouldn't like to see more work sunk into
> it either way :)
The main reasons I still see people using virtio-mmio for
the 'virt' board are:
* still using old but working command lines
* newer setups that were put together working from older tutorials
that recommended virtio-mmio because they predated virtio-pci
support being widespread
* using older (eg distro) kernels -- for 32-bit kernels in
particular it was a while before the virtio-pci support
got built in the default configs I think, and then longer
again until those got into stable distro releases
I wouldn't be surprised if some of those applied also to
via-OVMF boot setups as well as direct kernel boot. So it
depends a bit what your tolerance for breaking existing
user setups is.
thanks
-- PMM
next prev parent reply other threads:[~2019-08-02 9:20 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
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 [this message]
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='CAFEAcA9fHPpsvwXeKMnUbbHYu_=F+v+SF9ttAm+vOcXOmPVhMA@mail.gmail.com' \
--to=peter.maydell@linaro.org \
--cc=lersek@redhat.com \
--cc=mst@redhat.com \
--cc=pbonzini@redhat.com \
--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 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).