From: Peter Xu <peterx@redhat.com>
To: Jason Wang <jasowang@redhat.com>
Cc: mst@redhat.com, qemu-devel@nongnu.org, eric.auger@redhat.com,
viktor@daynix.com
Subject: Re: [PATCH 3/3] intel-iommu: build iova tree during IOMMU translation
Date: Fri, 23 Dec 2022 11:22:24 -0500 [thread overview]
Message-ID: <Y6XVwMXooIIQJZms@x1n> (raw)
In-Reply-To: <CACGkMEtgZY_2CHQwivuyMp+C=uJ7+Vom3WrDYqZesMonWKtd4A@mail.gmail.com>
On Fri, Dec 23, 2022 at 04:02:29PM +0800, Jason Wang wrote:
> On Tue, Dec 6, 2022 at 9:58 PM Peter Xu <peterx@redhat.com> wrote:
> >
> > On Tue, Dec 06, 2022 at 11:18:03AM +0800, Jason Wang wrote:
> > > On Tue, Dec 6, 2022 at 7:19 AM Peter Xu <peterx@redhat.com> wrote:
> > > >
> > > > Jason,
> > > >
> > > > On Mon, Dec 05, 2022 at 12:12:04PM +0800, Jason Wang wrote:
> > > > > I'm fine to go without iova-tree. Would you mind to post patches for
> > > > > fix? I can test and include it in this series then.
> > > >
> > > > One sample patch attached, only compile tested.
> > >
> > > I don't see any direct connection between the attached patch and the
> > > intel-iommu?
> >
> > Sorry! Wrong tree dumped... Trying again.
>
> The HWADDR breaks memory_region_notify_iommu_one():
>
> qemu-system-x86_64: ../softmmu/memory.c:1991:
> memory_region_notify_iommu_one: Assertion `entry->iova >=
> notifier->start && entry_end <= notifier->end' failed.
>
> I wonder if we need either:
>
> 1) remove the assert
I vote for this one. Not only removing the assertion, we should probably
crop the range too just like dev-iotlb unmaps?
Thanks,
>
> or
>
> 2) introduce a new memory_region_notify_unmap_all() to unmap from
> notifier->start to notifier->end.
--
Peter Xu
next prev parent reply other threads:[~2022-12-23 16:23 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-29 8:10 [PATCH 0/3] Fix UNMAP notifier for intel-iommu Jason Wang
2022-11-29 8:10 ` [PATCH 1/3] intel-iommu: fail MAP notifier without caching mode Jason Wang
2022-11-29 15:35 ` Peter Xu
2022-11-30 6:23 ` Jason Wang
2022-11-30 15:06 ` Peter Xu
2022-12-01 8:46 ` Jason Wang
2022-12-06 13:23 ` Eric Auger
2022-11-29 8:10 ` [PATCH 2/3] intel-iommu: fail DEVIOTLB_UNMAP without dt mode Jason Wang
2022-11-29 15:38 ` Peter Xu
2022-12-01 16:03 ` Peter Xu
2023-02-23 3:19 ` Jason Wang
2022-12-06 13:33 ` Eric Auger
2023-02-03 9:08 ` Laurent Vivier
2023-02-07 16:17 ` Laurent Vivier
2023-02-07 16:35 ` Peter Xu
2022-11-29 8:10 ` [PATCH 3/3] intel-iommu: build iova tree during IOMMU translation Jason Wang
2022-11-29 15:57 ` Peter Xu
2022-11-30 6:33 ` Jason Wang
2022-11-30 15:17 ` Peter Xu
2022-12-01 8:35 ` Jason Wang
2022-12-01 14:58 ` Peter Xu
2022-12-05 4:12 ` Jason Wang
2022-12-05 23:18 ` Peter Xu
2022-12-06 3:18 ` Jason Wang
2022-12-06 13:58 ` Peter Xu
2022-12-23 8:02 ` Jason Wang
2022-12-23 16:22 ` Peter Xu [this message]
2022-11-30 16:37 ` [PATCH 0/3] Fix UNMAP notifier for intel-iommu Michael S. Tsirkin
2022-12-01 8:29 ` Jason Wang
2022-12-20 13:53 ` Michael S. Tsirkin
2022-12-21 3:17 ` Jason Wang
2023-01-15 23:30 ` Viktor Prutyanov
2023-01-16 7:06 ` Jason Wang
2023-01-27 13:17 ` Michael S. Tsirkin
2023-01-29 5:43 ` Jason Wang
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=Y6XVwMXooIIQJZms@x1n \
--to=peterx@redhat.com \
--cc=eric.auger@redhat.com \
--cc=jasowang@redhat.com \
--cc=mst@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=viktor@daynix.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).