From: Halil Pasic <pasic@linux.ibm.com>
To: "Michael S. Tsirkin" <mst@redhat.com>
Cc: Kevin Wolf <kwolf@redhat.com>, Cornelia Huck <cohuck@redhat.com>,
Brijesh Singh <brijesh.singh@amd.com>,
Jason Wang <jasowang@redhat.com>,
Daniel Henrique Barboza <danielhb413@gmail.com>,
qemu-devel@nongnu.org, qemu-stable@nongnu.org,
Halil Pasic <pasic@linux.ibm.com>,
Daniel Henrique Barboza <danielhb@linux.ibm.com>,
Jakob Naucke <Jakob.Naucke@ibm.com>
Subject: Re: [PATCH v3 1/1] virtio: fix the condition for iommu_platform not supported
Date: Wed, 2 Feb 2022 14:16:45 +0100 [thread overview]
Message-ID: <20220202141645.1f784f19.pasic@linux.ibm.com> (raw)
In-Reply-To: <20220202020543-mutt-send-email-mst@kernel.org>
On Wed, 2 Feb 2022 02:06:12 -0500
"Michael S. Tsirkin" <mst@redhat.com> wrote:
[..]
> > In my opinion not forcing the guest to negotiate IOMMU_PLATFORM when
> > ->get_dma_as() is not set is at least unfortunate. Please observe, that
> > virtio-pci is not affected by this omission because for virtio-pci
> > devices ->get_dma_as != NULL always holds. And what is the deal for
> > devices that don't implement get_dma_as() (and don't need address
> > translation)? If iommu_platform=on is justified (no user error) then
> > the device does not have access to the entire guest memory. Which
> > means it more than likely needs cooperation form the guest (driver).
> > So detecting that the guest does not support IOMMU_PLATFORM and failing
> > gracefully via virtio_validate_features() instead of carrying on
> > in good faith and failing in ugly ways when the host attempts to access
> > guest memory to which it does not have access to. If we assume user
> > error, that is the host can access at least all the memory it needs
> > to access to make that device work, then it is probably still a
> > good idea to fail the device and thus help the user correct his
> > error.
> >
> > IMHO the best course of action is
> > diff --git a/hw/virtio/virtio-bus.c b/hw/virtio/virtio-bus.c
> > index 34f5a0a664..1d0eb16d1c 100644
> > --- a/hw/virtio/virtio-bus.c
> > +++ b/hw/virtio/virtio-bus.c
> > @@ -80,7 +80,6 @@ void virtio_bus_device_plugged(VirtIODevice *vdev, Error **errp)
> >
> > vdev_has_iommu = virtio_host_has_feature(vdev, VIRTIO_F_IOMMU_PLATFORM);
> > if (klass->get_dma_as != NULL && has_iommu) {
> > - virtio_add_feature(&vdev->host_features, VIRTIO_F_IOMMU_PLATFORM);
> > vdev->dma_as = klass->get_dma_as(qbus->parent);
> > if (!vdev_has_iommu && vdev->dma_as != &address_space_memory) {
> > error_setg(errp,
> > @@ -89,6 +88,7 @@ void virtio_bus_device_plugged(VirtIODevice *vdev, Error **errp)
> > } else {
> > vdev->dma_as = &address_space_memory;
> > }
> > + virtio_add_feature(&vdev->host_features, VIRTIO_F_IOMMU_PLATFORM);
> > }
> >
> > which would be a separate patch, as this is a separate issue. Jason,
> > Michael, Connie, what do you think?
>
> Do you mean just force VIRTIO_F_IOMMU_PLATFORM for everyone?
> Or am I misreading the patch?
Yes. Where force means: prevent the driver from setting FEATURES_OK
if it cleared VIRTIO_F_IOMMU_PLATFORM. I really don't see the case
where the device offering but the driver not accepting
VIRTIO_F_IOMMU_PLATFORM is good and useful.
Regards,
Halil
>
>
> > Regards,
> > Halil
>
>
next prev parent reply other threads:[~2022-02-02 13:51 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-01 13:39 [PATCH v3 1/1] virtio: fix the condition for iommu_platform not supported Halil Pasic
2022-02-01 15:36 ` Daniel Henrique Barboza
2022-02-01 18:33 ` Halil Pasic
2022-02-01 19:31 ` Daniel Henrique Barboza
2022-02-02 1:15 ` Halil Pasic
2022-02-02 7:06 ` Michael S. Tsirkin
2022-02-02 13:16 ` Halil Pasic [this message]
2022-02-02 13:24 ` Daniel Henrique Barboza
2022-02-02 16:23 ` Halil Pasic
2022-02-02 16:27 ` Daniel Henrique Barboza
2022-02-02 16:50 ` Michael S. Tsirkin
2022-02-01 16:05 ` Halil Pasic
2022-02-01 16:47 ` Cornelia Huck
2022-02-01 16:52 ` Michael S. Tsirkin
2022-02-01 17:50 ` Halil Pasic
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=20220202141645.1f784f19.pasic@linux.ibm.com \
--to=pasic@linux.ibm.com \
--cc=Jakob.Naucke@ibm.com \
--cc=brijesh.singh@amd.com \
--cc=cohuck@redhat.com \
--cc=danielhb413@gmail.com \
--cc=danielhb@linux.ibm.com \
--cc=jasowang@redhat.com \
--cc=kwolf@redhat.com \
--cc=mst@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-stable@nongnu.org \
/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).