qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Andrea Bolognani <abologna@redhat.com>
To: Cornelia Huck <cohuck@redhat.com>
Cc: peter.maydell@linaro.org, qemu-devel@nongnu.org,
	Sergio Lopez <slp@redhat.com>,
	mst@redhat.com
Subject: Re: [Qemu-devel] [RFC] virtio-mmio: implement modern (v2) personality (virtio-1)
Date: Tue, 30 Jul 2019 14:17:48 +0200	[thread overview]
Message-ID: <09e5ceb5e7c03f74f05307a3b9f9a4df035ff74f.camel@redhat.com> (raw)
In-Reply-To: <20190730133546.056f8b19.cohuck@redhat.com>

On Tue, 2019-07-30 at 13:35 +0200, Cornelia Huck wrote:
> On Tue, 30 Jul 2019 12:25:30 +0200
> Andrea Bolognani <abologna@redhat.com> wrote:
> > Can you please make sure virtio-mmio uses the existing interface
> > instead of introducing a new one?
> 
> FWIW, I really hate virtio-pci's disable-modern/disable-legacy... for a
> starter, what is 'modern'? Will we have 'ultra-modern' in the future?

AIUI the modern/legacy terminology is part of the VirtIO spec, so
while I agree that it's not necessarily the least prone to ambiguity
at least it's well defined.

> It is also quite backwards with the 'disable' terminology.

That's also true. I never claimed the way virtio-pci does it is
perfect!

> We also have a different mechanism for virtio-ccw ('max_revision',
> which covers a bit more than virtio-1; it doesn't have a 'min_revision',
> as negotiating the revision down is fine), so I don't see why
> virtio-mmio should replicate the virtio-pci mechanism.
> 
> Also, IIUC, virtio-mmio does not have transitional devices, but either
> version 1 (legacy) or version 2 (virtio-1). It probably makes more
> sense to expose the device version instead; either as an exact version
> (especially if it isn't supposed to go up without incompatible
> changes), or with some min/max concept (where version 1 would stand a
> bit alone, so that would probably be a bit awkward.)

I think that if reinventing the wheel is generally agreed not to be
a good idea, then it stands to reason that reinventing it twice can
only be described as absolute madness :)

We should have a single way to control the VirtIO protocol version
that works for all VirtIO devices, regardless of transport. We might
even want to have virtio-*-{device,ccw}-non-transitional to mirror
the existing virtio-*-pci-non-transitional.

FWIW, libvirt already implements support for (non)-transitional
virtio-pci devices using either the dedicated devices or the base
virtio-pci plus the disable-{modern,legacy} attributes.

-- 
Andrea Bolognani / Red Hat / Virtualization



  reply	other threads:[~2019-07-30 12: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 [this message]
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
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=09e5ceb5e7c03f74f05307a3b9f9a4df035ff74f.camel@redhat.com \
    --to=abologna@redhat.com \
    --cc=cohuck@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 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).