From: "Michael S. Tsirkin" <mst@redhat.com>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: Peter Maydell <peter.maydell@linaro.org>,
Laszlo Ersek <lersek@redhat.com>,
qemu-devel <qemu-devel@nongnu.org>,
Sergio Lopez Pascual <slp@redhat.com>
Subject: Re: [Qemu-devel] [RFC] virtio-mmio: implement modern (v2) personality (virtio-1)
Date: Thu, 1 Aug 2019 15:45:33 -0400 [thread overview]
Message-ID: <20190801154456-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <9953cc99-80b3-814c-f75e-a16c987c23e5@redhat.com>
On Thu, Aug 01, 2019 at 01:58:35AM +0200, Paolo Bonzini wrote:
> On 30/07/19 18:06, Laszlo Ersek wrote:
> > On 07/29/19 14:57, Sergio Lopez wrote:
> >> Implement the modern (v2) personality, according to the VirtIO 1.0
> >> specification.
> >>
> >> Support for v2 among guests is not as widespread as it'd be
> >> desirable. While the Linux driver has had it for a while, support is
> >> missing, at least, from Tianocore EDK II, NetBSD and FreeBSD.
> >
> > That's right; not only are there no plans to implement virtio-mmio/1.0
> > for OVMF (to my knowledge), I'd even argue against such efforts.
> >
> > OVMF is a heavy-weight guest firmware, which I see entirely out of scope
> > for "micro VMs". And so virtio-mmio/1.0 would seem like a needless &
> > unwelcome complication, from the OVMF maintainership perspective.
>
> But given that, why not rip out virtio-mmio completely?
>
> Paolo
From OVMF?
--
MST
next prev parent reply other threads:[~2019-08-01 19:47 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 [this message]
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=20190801154456-mutt-send-email-mst@kernel.org \
--to=mst@redhat.com \
--cc=lersek@redhat.com \
--cc=pbonzini@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 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).