All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Michael S. Tsirkin" <mst@redhat.com>
To: Jason Wang <jasowang@redhat.com>
Cc: peterx@redhat.com, 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 20:02:35 -0500	[thread overview]
Message-ID: <20230307200208-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <20230223065924.42503-4-jasowang@redhat.com>

On Thu, Feb 23, 2023 at 02:59:22PM +0800, 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);
> +
> +
>  /**
>   * memory_region_register_iommu_notifier: register a notifier for changes to
>   * IOMMU translation entries.

This causes doc warnings:

/scm/qemu/docs/../include/exec/memory.h:1741: warning: Function parameter or member 'n' not described in 'memory_region_unmap_iommu_notifier_range'
/scm/qemu/docs/../include/exec/memory.h:1741: warning: Excess function parameter 'notifier' description in 'memory_region_unmap_iommu_notifier_range'


please fix.


> diff --git a/softmmu/memory.c b/softmmu/memory.c
> index 9d64efca26..ba43b4474e 100644
> --- a/softmmu/memory.c
> +++ b/softmmu/memory.c
> @@ -1996,6 +1996,19 @@ void memory_region_notify_iommu_one(IOMMUNotifier *notifier,
>      }
>  }
>  
> +void memory_region_unmap_iommu_notifier_range(IOMMUNotifier *n)
> +{
> +    IOMMUTLBEvent event;
> +
> +    event.type = IOMMU_NOTIFIER_UNMAP;
> +    event.entry.target_as = &address_space_memory;
> +    event.entry.iova = n->start;
> +    event.entry.perm = IOMMU_NONE;
> +    event.entry.addr_mask = n->end - n->start;
> +
> +    memory_region_notify_iommu_one(n, &event);
> +}
> +
>  void memory_region_notify_iommu(IOMMUMemoryRegion *iommu_mr,
>                                  int iommu_idx,
>                                  IOMMUTLBEvent event)
> -- 
> 2.25.1



  parent reply	other threads:[~2023-03-08  1:03 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
2023-03-08  1:02   ` Michael S. Tsirkin [this message]
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=20230307200208-mutt-send-email-mst@kernel.org \
    --to=mst@redhat.com \
    --cc=eric.auger@redhat.com \
    --cc=jasowang@redhat.com \
    --cc=lvivier@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.