From: "Michael S. Tsirkin" <mst@redhat.com>
To: Eric Auger <eric.auger@redhat.com>
Cc: "Duan, Zhenzhong" <zhenzhong.duan@intel.com>,
"eric.auger.pro@gmail.com" <eric.auger.pro@gmail.com>,
"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>,
"qemu-arm@nongnu.org" <qemu-arm@nongnu.org>,
"jean-philippe@linaro.org" <jean-philippe@linaro.org>,
"alex.williamson@redhat.com" <alex.williamson@redhat.com>,
"clg@redhap.com" <clg@redhap.com>,
"bharat.bhushan@nxp.com" <bharat.bhushan@nxp.com>,
"peter.maydell@linaro.org" <peter.maydell@linaro.org>
Subject: Re: [PATCH 2/2] virtio-iommu: Rework the trace in virtio_iommu_set_page_size_mask()
Date: Thu, 6 Jul 2023 14:52:39 -0400 [thread overview]
Message-ID: <20230706145221-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <a11b8c79-9efc-6686-6405-863abb8824ae@redhat.com>
On Wed, Jul 05, 2023 at 03:16:31PM +0200, Eric Auger wrote:
> Hi Zhenghong,
>
> On 7/5/23 10:17, Duan, Zhenzhong wrote:
> >
> >> -----Original Message-----
> >> From: Duan, Zhenzhong
> >> Sent: Wednesday, July 5, 2023 12:56 PM
> >> Subject: RE: [PATCH 2/2] virtio-iommu: Rework the trace in
> >> virtio_iommu_set_page_size_mask()
> >>
> >>
> >>
> >>> -----Original Message-----
> >>> From: Eric Auger <eric.auger@redhat.com>
> >>> Sent: Tuesday, July 4, 2023 7:15 PM
> >>> To: eric.auger.pro@gmail.com; eric.auger@redhat.com; qemu-
> >>> devel@nongnu.org; qemu-arm@nongnu.org; mst@redhat.com; jean-
> >>> philippe@linaro.org; Duan, Zhenzhong <zhenzhong.duan@intel.com>
> >>> Cc: alex.williamson@redhat.com; clg@redhap.com;
> >> bharat.bhushan@nxp.com;
> >>> peter.maydell@linaro.org
> >>> Subject: [PATCH 2/2] virtio-iommu: Rework the trace in
> >>> virtio_iommu_set_page_size_mask()
> >>>
> >>> The current error messages in virtio_iommu_set_page_size_mask() sound
> >>> quite similar for different situations and miss the IOMMU memory region
> >>> that causes the issue.
> >>>
> >>> Clarify them and rework the comment.
> >>>
> >>> Also remove the trace when the new page_size_mask is not applied as the
> >>> current frozen granule is kept. This message is rather confusing for
> >>> the end user and anyway the current granule would have been used by the
> >>> driver
> >>>
> >>> Signed-off-by: Eric Auger <eric.auger@redhat.com>
> >>> ---
> >>> hw/virtio/virtio-iommu.c | 19 +++++++------------
> >>> 1 file changed, 7 insertions(+), 12 deletions(-)
> >>>
> >>> diff --git a/hw/virtio/virtio-iommu.c b/hw/virtio/virtio-iommu.c index
> >>> 1eaf81bab5..0d9f7196fe 100644
> >>> --- a/hw/virtio/virtio-iommu.c
> >>> +++ b/hw/virtio/virtio-iommu.c
> >>> @@ -1101,29 +1101,24 @@ static int
> >>> virtio_iommu_set_page_size_mask(IOMMUMemoryRegion *mr,
> >>> new_mask);
> >>>
> >>> if ((cur_mask & new_mask) == 0) {
> >>> - error_setg(errp, "virtio-iommu page mask 0x%"PRIx64
> >>> - " is incompatible with mask 0x%"PRIx64, cur_mask, new_mask);
> >>> + error_setg(errp, "virtio-iommu %s reports a page size mask 0x%"PRIx64
> >>> + " incompatible with currently supported mask 0x%"PRIx64,
> >>> + mr->parent_obj.name, new_mask, cur_mask);
> >>> return -1;
> >>> }
> >>>
> >>> /*
> >>> * Once the granule is frozen we can't change the mask anymore. If by
> >>> * chance the hotplugged device supports the same granule, we can still
> >>> - * accept it. Having a different masks is possible but the guest will use
> >>> - * sub-optimal block sizes, so warn about it.
> >>> + * accept it.
> >>> */
> >>> if (s->granule_frozen) {
> >>> - int new_granule = ctz64(new_mask);
> >>> int cur_granule = ctz64(cur_mask);
> >>>
> >>> - if (new_granule != cur_granule) {
> >>> - error_setg(errp, "virtio-iommu page mask 0x%"PRIx64
> >>> - " is incompatible with mask 0x%"PRIx64, cur_mask,
> >>> - new_mask);
> >>> + if (!(BIT(cur_granule) & new_mask)) {
> > Sorry, I read this piece code again and got a question, if new_mask has finer
> > granularity than cur_granule, should we allow it to pass even though
> > BIT(cur_granule) is not set?
> I think this should work but this is not straightforward to test.
> virtio-iommu would use the current granule for map/unmap. In map/unmap
> notifiers, this is split into pow2 ranges and cascaded to VFIO through
> vfio_dma_map/unmap. The iova and size are aligned with the smaller
> supported granule.
Maybe add a comment down the road. Not urgent.
> Jean, do you share this understanding or do I miss something.
>
> Nevertheless the current code would have rejected that case and nobody
> complained at that point ;-)
>
> thanks
>
> Eric
>
> >
> > Thanks
> > Zhenzhong
> >
> >> Good catch.
> >>
> >> Reviewed-by: Zhenzhong Duan <zhenzhong.duan@intel.com>
> >>
> >> Thanks
> >> Zhenzhong
> >>
> >>> + error_setg(errp, "virtio-iommu %s does not support frozen
> >>> + granule
> >>> 0x%"PRIx64,
> >>> + mr->parent_obj.name, BIT(cur_granule));
> >>> return -1;
> >>> - } else if (new_mask != cur_mask) {
> >>> - warn_report("virtio-iommu page mask 0x%"PRIx64
> >>> - " does not match 0x%"PRIx64, cur_mask, new_mask);
> >>> }
> >>> return 0;
> >>> }
> >>> --
> >>> 2.38.1
prev parent reply other threads:[~2023-07-06 18:53 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-04 11:15 [PATCH 0/2] VIRTIO-IOMMU/VFIO page size related fixes Eric Auger
2023-07-04 11:15 ` [PATCH 1/2] virtio-iommu: Fix 64kB host page size VFIO device assignment Eric Auger
2023-07-05 4:52 ` Duan, Zhenzhong
2023-07-05 6:19 ` Eric Auger
2023-07-05 8:11 ` Duan, Zhenzhong
2023-07-05 8:29 ` Jean-Philippe Brucker
2023-07-05 10:13 ` Duan, Zhenzhong
2023-07-05 11:33 ` Jean-Philippe Brucker
2023-07-06 9:00 ` Duan, Zhenzhong
2023-07-04 11:15 ` [PATCH 2/2] virtio-iommu: Rework the trace in virtio_iommu_set_page_size_mask() Eric Auger
2023-07-05 4:55 ` Duan, Zhenzhong
2023-07-05 8:17 ` Duan, Zhenzhong
2023-07-05 13:16 ` Eric Auger
2023-07-06 8:56 ` Duan, Zhenzhong
2023-07-06 14:35 ` Jean-Philippe Brucker
2023-07-06 15:38 ` Eric Auger
2023-07-07 2:34 ` Duan, Zhenzhong
2023-07-06 18:52 ` Michael S. Tsirkin [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=20230706145221-mutt-send-email-mst@kernel.org \
--to=mst@redhat.com \
--cc=alex.williamson@redhat.com \
--cc=bharat.bhushan@nxp.com \
--cc=clg@redhap.com \
--cc=eric.auger.pro@gmail.com \
--cc=eric.auger@redhat.com \
--cc=jean-philippe@linaro.org \
--cc=peter.maydell@linaro.org \
--cc=qemu-arm@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=zhenzhong.duan@intel.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).