All of lore.kernel.org
 help / color / mirror / Atom feed
From: Alex Williamson <alex.williamson@redhat.com>
To: Peter Xu <peterx@redhat.com>
Cc: qemu-devel@nongnu.org, tianyu.lan@intel.com,
	kevin.tian@intel.com, mst@redhat.com, jan.kiszka@siemens.com,
	jasowang@redhat.com, David Gibson <david@gibson.dropbear.id.au>,
	bd.aviv@gmail.com
Subject: Re: [Qemu-devel] [PATCH v6 03/18] vfio: allow to notify unmap for very large region
Date: Fri, 3 Feb 2017 10:20:36 -0700	[thread overview]
Message-ID: <20170203102036.21faba1e@t450s.home> (raw)
In-Reply-To: <1486110164-13797-4-git-send-email-peterx@redhat.com>

On Fri,  3 Feb 2017 16:22:29 +0800
Peter Xu <peterx@redhat.com> wrote:

> Linux vfio driver supports to do VFIO_IOMMU_UNMAP_DMA for a very big
> region. This can be leveraged by QEMU IOMMU implementation to cleanup
> existing page mappings for an entire iova address space (by notifying
> with an IOTLB with extremely huge addr_mask). However current
> vfio_iommu_map_notify() does not allow that. It make sure that all the
> translated address in IOTLB is falling into RAM range.
> 
> The check makes sense, but it should only be a sensible checker for
> mapping operations, and mean little for unmap operations.
> 
> This patch moves this check into map logic only, so that we'll get
> faster unmap handling (no need to translate again), and also we can then
> better support unmapping a very big region when it covers non-ram ranges
> or even not-existing ranges.
> 
> Signed-off-by: Peter Xu <peterx@redhat.com>
> ---
>  hw/vfio/common.c | 7 +++----
>  1 file changed, 3 insertions(+), 4 deletions(-)


Acked-by: Alex Williamson <alex.williamson@redhat.com>


> diff --git a/hw/vfio/common.c b/hw/vfio/common.c
> index 42c4790..f3ba9b9 100644
> --- a/hw/vfio/common.c
> +++ b/hw/vfio/common.c
> @@ -352,11 +352,10 @@ static void vfio_iommu_map_notify(IOMMUNotifier *n, IOMMUTLBEntry *iotlb)
>  
>      rcu_read_lock();
>  
> -    if (!vfio_get_vaddr(iotlb, &vaddr, &read_only)) {
> -        goto out;
> -    }
> -
>      if ((iotlb->perm & IOMMU_RW) != IOMMU_NONE) {
> +        if (!vfio_get_vaddr(iotlb, &vaddr, &read_only)) {
> +            goto out;
> +        }
>          /*
>           * vaddr is only valid until rcu_read_unlock(). But after
>           * vfio_dma_map has set up the mapping the pages will be

  reply	other threads:[~2017-02-03 17:20 UTC|newest]

Thread overview: 43+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-02-03  8:22 [Qemu-devel] [PATCH v6 00/18] VT-d: vfio enablement and misc enhances Peter Xu
2017-02-03  8:22 ` [Qemu-devel] [PATCH v6 01/18] vfio: trace map/unmap for notify as well Peter Xu
2017-02-06  1:27   ` David Gibson
2017-02-03  8:22 ` [Qemu-devel] [PATCH v6 02/18] vfio: introduce vfio_get_vaddr() Peter Xu
2017-02-03 17:20   ` Alex Williamson
2017-02-06  2:10   ` David Gibson
2017-02-03  8:22 ` [Qemu-devel] [PATCH v6 03/18] vfio: allow to notify unmap for very large region Peter Xu
2017-02-03 17:20   ` Alex Williamson [this message]
2017-02-03  8:22 ` [Qemu-devel] [PATCH v6 04/18] intel_iommu: add "caching-mode" option Peter Xu
2017-02-07  2:31   ` Jason Wang
2017-02-03  8:22 ` [Qemu-devel] [PATCH v6 05/18] intel_iommu: simplify irq region translation Peter Xu
2017-02-07  5:23   ` Jason Wang
2017-02-03  8:22 ` [Qemu-devel] [PATCH v6 06/18] intel_iommu: renaming gpa to iova where proper Peter Xu
2017-02-07  5:27   ` Jason Wang
2017-02-07  6:16     ` Peter Xu
2017-02-07  6:21       ` Jason Wang
2017-02-03  8:22 ` [Qemu-devel] [PATCH v6 07/18] intel_iommu: fix trace for inv desc handling Peter Xu
2017-02-07  5:38   ` Jason Wang
2017-02-07  6:08     ` Peter Xu
2017-02-07  6:20       ` Jason Wang
2017-02-03  8:22 ` [Qemu-devel] [PATCH v6 08/18] intel_iommu: fix trace for addr translation Peter Xu
2017-02-07  5:40   ` Jason Wang
2017-02-07  6:25     ` Peter Xu
2017-02-07  6:34       ` Jason Wang
2017-02-03  8:22 ` [Qemu-devel] [PATCH v6 09/18] intel_iommu: vtd_slpt_level_shift check level Peter Xu
2017-02-07  5:42   ` Jason Wang
2017-02-07  8:03     ` Peter Xu
2017-02-03  8:22 ` [Qemu-devel] [PATCH v6 10/18] memory: add section range info for IOMMU notifier Peter Xu
2017-02-03 17:22   ` Alex Williamson
2017-02-03  8:22 ` [Qemu-devel] [PATCH v6 11/18] memory: provide IOMMU_NOTIFIER_FOREACH macro Peter Xu
2017-02-03  8:22 ` [Qemu-devel] [PATCH v6 12/18] memory: provide iommu_replay_all() Peter Xu
2017-02-03  8:22 ` [Qemu-devel] [PATCH v6 13/18] memory: introduce memory_region_notify_one() Peter Xu
2017-02-03  8:22 ` [Qemu-devel] [PATCH v6 14/18] memory: add MemoryRegionIOMMUOps.replay() callback Peter Xu
2017-02-03  8:22 ` [Qemu-devel] [PATCH v6 15/18] intel_iommu: provide its own replay() callback Peter Xu
2017-02-07  6:10   ` Jason Wang
2017-02-07  8:05     ` Peter Xu
2017-02-03  8:22 ` [Qemu-devel] [PATCH v6 16/18] intel_iommu: do replay when context invalidate Peter Xu
2017-02-07  6:16   ` Jason Wang
2017-02-07  8:12     ` Peter Xu
2017-02-03  8:22 ` [Qemu-devel] [PATCH v6 17/18] intel_iommu: allow dynamic switch of IOMMU region Peter Xu
2017-02-07  6:13   ` Jason Wang
2017-02-03  8:22 ` [Qemu-devel] [PATCH v6 18/18] intel_iommu: enable vfio devices Peter Xu
2017-02-07  6:19   ` 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=20170203102036.21faba1e@t450s.home \
    --to=alex.williamson@redhat.com \
    --cc=bd.aviv@gmail.com \
    --cc=david@gibson.dropbear.id.au \
    --cc=jan.kiszka@siemens.com \
    --cc=jasowang@redhat.com \
    --cc=kevin.tian@intel.com \
    --cc=mst@redhat.com \
    --cc=peterx@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=tianyu.lan@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 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.