qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
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>,
	Jakob Naucke <Jakob.Naucke@ibm.com>
Subject: Re: [PATCH v4 1/1] virtio: fix the condition for iommu_platform not supported
Date: Mon, 7 Feb 2022 12:30:17 +0100	[thread overview]
Message-ID: <20220207123017.3d8a2ca8.pasic@linux.ibm.com> (raw)
In-Reply-To: <20220204201506-mutt-send-email-mst@kernel.org>

On Fri, 4 Feb 2022 20:15:27 -0500
"Michael S. Tsirkin" <mst@redhat.com> wrote:

> On Sat, Feb 05, 2022 at 01:02:05AM +0100, Halil Pasic wrote:
> > On Fri, 4 Feb 2022 08:05:25 -0500
> > "Michael S. Tsirkin" <mst@redhat.com> wrote:
> >   
> > > On Thu, Feb 03, 2022 at 05:06:35PM +0100, Halil Pasic wrote:  
> > > > On Wed,  2 Feb 2022 20:54:38 +0100
> > > > Halil Pasic <pasic@linux.ibm.com> wrote:
> > > >     
> > > > >      }
> > > > > @@ -82,9 +78,14 @@ void virtio_bus_device_plugged(VirtIODevice *vdev, Error **errp)
> > > > >          return;
> > > > >      }
> > > > >  
> > > > > +    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,
> > > > > +                       "iommu_platform=true is not supported by the device");
> > > > > +        }    
> > > > 
> > > > I'm wondering, would it be wise to change the message? Since this is now
> > > > dependent on the VM/bus the device is plugged into the message might be a
> > > > little misleading: i.e. the very same device could work perfectly fine
> > > > with iommu_platform=true if the "surroundings" are different.
> > > > 
> > > > Maybe "the device has no IOMMU support (iommu_platform=true)" would be a
> > > > better option. On the other hand changing the message has its downsides
> > > > as well.    
> > > 
> > > I personally don't care much frankly.
> > >   
> > > > Also I realized that keeping the return after error_setg() might have
> > > > been a good idea for the case more logic is added at the end of the
> > > > function.    
> > > 
> > > OK so you are sending v5 with this change then?  
> > 
> > As stated below, I would prefer to get this merged. If I change the
> > message, I guess I have to drop the r-b's and the I'm sure the if
> > somebody decides to add logic to the end of the function that person
> > will be careful enough.  
> 
> yes but you wrote about return after error_setg above.
> 

I've sent a v5 with the extra return. Please pick v5 or v4 whichever you
prefer :D

Cheers,
Halil


      reply	other threads:[~2022-02-07 11:47 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-02 19:54 [PATCH v4 1/1] virtio: fix the condition for iommu_platform not supported Halil Pasic
2022-02-03 16:06 ` Halil Pasic
2022-02-04 13:05   ` Michael S. Tsirkin
2022-02-05  0:02     ` Halil Pasic
2022-02-05  1:15       ` Michael S. Tsirkin
2022-02-07 11:30         ` Halil Pasic [this message]

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=20220207123017.3d8a2ca8.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=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).