From: Cornelia Huck <cohuck@redhat.com>
To: "Michael S. Tsirkin" <mst@redhat.com>
Cc: Eric Auger <eric.auger@redhat.com>,
"Dr. David Alan Gilbert" <dgilbert@redhat.com>,
Stefan Hajnoczi <stefanha@redhat.com>,
qemu-devel@nongnu.org
Subject: Re: [PATCH RFC] virtio-fs: force virtio 1.x usage
Date: Wed, 1 Jul 2020 15:58:19 +0200 [thread overview]
Message-ID: <20200701155819.55c64224.cohuck@redhat.com> (raw)
In-Reply-To: <20200630074918-mutt-send-email-mst@kernel.org>
On Tue, 30 Jun 2020 09:02:31 -0400
"Michael S. Tsirkin" <mst@redhat.com> wrote:
> On Tue, Jun 30, 2020 at 01:30:43PM +0200, Cornelia Huck wrote:
> > On Tue, 30 Jun 2020 06:45:42 -0400
> > "Michael S. Tsirkin" <mst@redhat.com> wrote:
> >
> > > On Tue, Jun 30, 2020 at 11:35:27AM +0200, Cornelia Huck wrote:
> > > > First, I noticed that virtio-iommu does not force virtio-1, either; I
> > > > think it should? Eric?
> > > >
> > > > Then, there's the mechanism using different names for transitional and
> > > > non-transitional devices. Devices that support both usually define both
> > > > names (with disable_legacy and disable_modern set appropriately) and a
> > > > base name (where the properties can be set manually for the desired
> > > > effect). Most virtio-1 only devices set neither the non-transitional
> > > > nor the transitional name and rely on virtio_pci_force_virtio_1() to
> > > > disable legacy support. But there are outliers:
> > > >
> > > > * this device: it has only a non-transitional name
> > > > ("vhost-user-fs-pci"), which means we automatically get the correct
> > > > configuration; in order to define a transitional/legacy device, you
> > > > would need to use the base name "vhost-user-fs-pci-base" explicitly,
> > > > and it's unlikely that someone has been doing that.
> > > > * virtio-iommu (which I *think* is a virtio-1 only device): it defines
> > > > the full set of transitional, non-transitional, and base names.
> > > >
> > > > How should we proceed?
> > > > * With this patch here, we can fence off the very unlikely possibility
> > > > of somebody configuring a non-modern virtio-fs device for pci. We
> > > > probably should do it, but I don't think we need compat handling.
> > > > * For virtio-iommu, we should get an agreement what the desired state
> > > > is. If it really should be modern only, we need compat handling, as
> > > > the device had been added in 5.0. (And we need to figure out how to
> > > > apply that compat handling.)
> > >
> > >
> > > Well I know it's not really used on x86 yet, so no problem there.
> > >
> > > Which machines are actually affected?
> >
> > I'd suspect ARM, but breaking even a subset is not nice.
>
> OK so MMIO does not have transitional at all right?
IIRC, yes.
But I think there are ARM machines that use virtio-pci as well, right?
next prev parent reply other threads:[~2020-07-01 14:10 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-29 10:27 [PATCH RFC] virtio-fs: force virtio 1.x usage Cornelia Huck
2020-06-29 14:53 ` Michael S. Tsirkin
2020-06-29 15:39 ` Cornelia Huck
2020-06-29 15:45 ` Michael S. Tsirkin
2020-06-30 9:35 ` Cornelia Huck
2020-06-30 10:45 ` Michael S. Tsirkin
2020-06-30 11:30 ` Cornelia Huck
2020-06-30 13:02 ` Michael S. Tsirkin
2020-07-01 13:58 ` Cornelia Huck [this message]
2020-07-02 10:24 ` Michael S. Tsirkin
2020-06-29 17:05 ` Dr. David Alan Gilbert
2020-06-30 12:10 ` Stefan Hajnoczi
2020-06-30 12:25 ` Cornelia Huck
2020-06-30 13:04 ` Michael S. Tsirkin
2020-07-01 16:19 ` Cornelia Huck
2020-07-02 10:16 ` Michael S. Tsirkin
2020-07-02 10:45 ` Cornelia Huck
2020-07-02 11:22 ` Michael S. Tsirkin
2020-07-02 11:55 ` Cornelia Huck
2020-07-02 13:22 ` Michael S. Tsirkin
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=20200701155819.55c64224.cohuck@redhat.com \
--to=cohuck@redhat.com \
--cc=dgilbert@redhat.com \
--cc=eric.auger@redhat.com \
--cc=mst@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@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.