All of lore.kernel.org
 help / color / mirror / Atom feed
From: Paolo Bonzini <pbonzini@redhat.com>
To: Laszlo Ersek <lersek@redhat.com>,
	"Michael S. Tsirkin" <mst@redhat.com>,
	Sergio Lopez Pascual <slp@redhat.com>,
	Peter Maydell <peter.maydell@linaro.org>,
	qemu-devel <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [RFC] virtio-mmio: implement modern (v2) personality (virtio-1)
Date: Thu, 1 Aug 2019 01:58:35 +0200	[thread overview]
Message-ID: <9953cc99-80b3-814c-f75e-a16c987c23e5@redhat.com> (raw)
In-Reply-To: <932a0c3c-b6cb-540f-ca07-1559c8fe9049@redhat.com>

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


  reply	other threads:[~2019-07-31 23:59 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 [this message]
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=9953cc99-80b3-814c-f75e-a16c987c23e5@redhat.com \
    --to=pbonzini@redhat.com \
    --cc=lersek@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.