From: Thomas Huth <thuth@redhat.com>
To: Jason Wang <jasowang@redhat.com>, mst@redhat.com, peterx@redhat.com
Cc: qemu-devel@nongnu.org, eric.auger@redhat.com, viktor@daynix.com,
lvivier@redhat.com
Subject: Re: [PATCH V2 3/5] memory: introduce memory_region_unmap_iommu_notifier_range()
Date: Tue, 7 Mar 2023 14:19:29 +0100 [thread overview]
Message-ID: <06dc5ec1-9ccc-50a0-d80f-1c67f6147f0b@redhat.com> (raw)
In-Reply-To: <20230223065924.42503-4-jasowang@redhat.com>
On 23/02/2023 07.59, Jason Wang wrote:
> This patch introduces a new helper to unmap the range of a specific
> IOMMU notifier.
>
> Signed-off-by: Jason Wang <jasowang@redhat.com>
> ---
> include/exec/memory.h | 10 ++++++++++
> softmmu/memory.c | 13 +++++++++++++
> 2 files changed, 23 insertions(+)
>
> diff --git a/include/exec/memory.h b/include/exec/memory.h
> index 2e602a2fad..6fa0b071f0 100644
> --- a/include/exec/memory.h
> +++ b/include/exec/memory.h
> @@ -1731,6 +1731,16 @@ void memory_region_notify_iommu(IOMMUMemoryRegion *iommu_mr,
> void memory_region_notify_iommu_one(IOMMUNotifier *notifier,
> IOMMUTLBEvent *event);
>
> +/**
> + * memory_region_unmap_iommu_notifier_range: notify a unmap for an IOMMU
> + * translation that covers the
> + * range of a notifier
> + *
> + * @notifier: the notifier to be notified
> + */
> +void memory_region_unmap_iommu_notifier_range(IOMMUNotifier *n);
FWIW, this causes warning during the build process for me now:
../include/exec/memory.h:1741: warning: Function parameter or member 'n' not described in 'memory_region_unmap_iommu_notifier_range'
../include/exec/memory.h:1741: warning: Excess function parameter 'notifier' description in 'memory_region_unmap_iommu_notifier_range'
Thomas
next prev parent reply other threads:[~2023-03-07 13:20 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-23 6:59 [PATCH V2 0/5] Fix UNMAP notifier for intel-iommu Jason Wang
2023-02-23 6:59 ` [PATCH V2 1/5] intel-iommu: fail MAP notifier without caching mode Jason Wang
2023-02-23 6:59 ` [PATCH V2 2/5] intel-iommu: fail DEVIOTLB_UNMAP without dt mode Jason Wang
2023-02-23 6:59 ` [PATCH V2 3/5] memory: introduce memory_region_unmap_iommu_notifier_range() Jason Wang
2023-03-07 13:19 ` Thomas Huth [this message]
2023-03-08 1:02 ` Michael S. Tsirkin
2023-03-08 5:19 ` Jason Wang
2023-02-23 6:59 ` [PATCH V2 4/5] smmu: switch to use memory_region_unmap_iommu_notifier_range() Jason Wang
2023-02-23 6:59 ` [PATCH V2 5/5] intel-iommu: send UNMAP notifications for domain or global inv desc Jason Wang
2023-02-23 15:47 ` [PATCH V2 0/5] Fix UNMAP notifier for intel-iommu Peter Xu
2023-02-24 2:54 ` 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=06dc5ec1-9ccc-50a0-d80f-1c67f6147f0b@redhat.com \
--to=thuth@redhat.com \
--cc=eric.auger@redhat.com \
--cc=jasowang@redhat.com \
--cc=lvivier@redhat.com \
--cc=mst@redhat.com \
--cc=peterx@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).