All of lore.kernel.org
 help / color / mirror / Atom feed
From: Joerg Roedel <joro-zLv9SwRftAIdnm+yROfE0A@public.gmane.org>
To: Shameer Kolothum
	<shameerali.kolothum.thodi-hv44wF8Li93QT0dZR+AlfA@public.gmane.org>
Cc: kvm-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
	pmorel-23VcF4HTsmIX0ybBhKVfKdBPR1lH4CV8@public.gmane.org,
	iommu-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org,
	linuxarm-hv44wF8Li93QT0dZR+AlfA@public.gmane.org,
	linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
	xuwei5-C8/M+/jPZTeaMJb+Lgu22Q@public.gmane.org
Subject: Re: [PATCH v6 4/7] iommu/dma: Move PCI window region reservation back into dma specific path.
Date: Thu, 3 May 2018 15:16:48 +0200	[thread overview]
Message-ID: <20180503131648.GX15462@8bytes.org> (raw)
In-Reply-To: <20180418114045.7968-5-shameerali.kolothum.thodi-hv44wF8Li93QT0dZR+AlfA@public.gmane.org>

On Wed, Apr 18, 2018 at 12:40:42PM +0100, Shameer Kolothum wrote:
> This pretty much reverts commit 273df9635385 ("iommu/dma: Make PCI
> window reservation generic")  by moving the PCI window region
> reservation back into the dma specific path so that these regions
> doesn't get exposed via the IOMMU API interface. With this change,
> the vfio interface will report only iommu specific reserved regions
> to the user space.
> 
> Cc: Joerg Roedel <joro-zLv9SwRftAIdnm+yROfE0A@public.gmane.org>
> Signed-off-by: Shameer Kolothum <shameerali.kolothum.thodi-hv44wF8Li93QT0dZR+AlfA@public.gmane.org>
> Reviewed-by: Robin Murphy <robin.murphy-5wv7dgnIgG8@public.gmane.org>
> ---
>  drivers/iommu/dma-iommu.c | 54 ++++++++++++++++++++++-------------------------
>  1 file changed, 25 insertions(+), 29 deletions(-)

Applied to my iommu/fixes branch.

Thanks,

	Joerg

WARNING: multiple messages have this Message-ID (diff)
From: Joerg Roedel <joro@8bytes.org>
To: Shameer Kolothum <shameerali.kolothum.thodi@huawei.com>
Cc: alex.williamson@redhat.com, eric.auger@redhat.com,
	pmorel@linux.vnet.ibm.com, kvm@vger.kernel.org,
	linux-kernel@vger.kernel.org, iommu@lists.linux-foundation.org,
	linuxarm@huawei.com, john.garry@huawei.com, xuwei5@hisilicon.com
Subject: Re: [PATCH v6 4/7] iommu/dma: Move PCI window region reservation back into dma specific path.
Date: Thu, 3 May 2018 15:16:48 +0200	[thread overview]
Message-ID: <20180503131648.GX15462@8bytes.org> (raw)
In-Reply-To: <20180418114045.7968-5-shameerali.kolothum.thodi@huawei.com>

On Wed, Apr 18, 2018 at 12:40:42PM +0100, Shameer Kolothum wrote:
> This pretty much reverts commit 273df9635385 ("iommu/dma: Make PCI
> window reservation generic")  by moving the PCI window region
> reservation back into the dma specific path so that these regions
> doesn't get exposed via the IOMMU API interface. With this change,
> the vfio interface will report only iommu specific reserved regions
> to the user space.
> 
> Cc: Joerg Roedel <joro@8bytes.org>
> Signed-off-by: Shameer Kolothum <shameerali.kolothum.thodi@huawei.com>
> Reviewed-by: Robin Murphy <robin.murphy@arm.com>
> ---
>  drivers/iommu/dma-iommu.c | 54 ++++++++++++++++++++++-------------------------
>  1 file changed, 25 insertions(+), 29 deletions(-)

Applied to my iommu/fixes branch.

Thanks,

	Joerg

  parent reply	other threads:[~2018-05-03 13:16 UTC|newest]

Thread overview: 42+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-04-18 11:40 [PATCH v6 0/7] vfio/type1: Add support for valid iova list management Shameer Kolothum
2018-04-18 11:40 ` Shameer Kolothum
2018-04-18 11:40 ` Shameer Kolothum
2018-04-18 11:40 ` [PATCH v6 5/7] vfio/type1: check dma map request is within a valid iova range Shameer Kolothum
2018-04-18 11:40   ` Shameer Kolothum
     [not found] ` <20180418114045.7968-1-shameerali.kolothum.thodi-hv44wF8Li93QT0dZR+AlfA@public.gmane.org>
2018-04-18 11:40   ` [PATCH v6 1/7] vfio/type1: Introduce iova list and add iommu aperture validity check Shameer Kolothum
2018-04-18 11:40     ` Shameer Kolothum
2018-04-18 11:40     ` Shameer Kolothum
2018-04-18 11:40   ` [PATCH v6 2/7] vfio/type1: Check reserve region conflict and update iova list Shameer Kolothum
2018-04-18 11:40     ` Shameer Kolothum
2018-04-18 11:40     ` Shameer Kolothum
2018-04-18 11:40   ` [PATCH v6 3/7] vfio/type1: Update iova list on detach Shameer Kolothum
2018-04-18 11:40     ` Shameer Kolothum
2018-04-18 11:40     ` Shameer Kolothum
2018-04-18 11:40   ` [PATCH v6 4/7] iommu/dma: Move PCI window region reservation back into dma specific path Shameer Kolothum
2018-04-18 11:40     ` Shameer Kolothum
2018-04-18 11:40     ` Shameer Kolothum
     [not found]     ` <20180418114045.7968-5-shameerali.kolothum.thodi-hv44wF8Li93QT0dZR+AlfA@public.gmane.org>
2018-04-24 13:16       ` Shameerali Kolothum Thodi
2018-04-24 13:16         ` Shameerali Kolothum Thodi
2018-04-24 13:16         ` Shameerali Kolothum Thodi
     [not found]         ` <5FC3163CFD30C246ABAA99954A238FA8386928A8-WFPaWmAhWqtUuCJht5byYAK1hpo4iccwjNknBlVQO8k@public.gmane.org>
2018-04-30 16:10           ` Alex Williamson
2018-04-30 16:10             ` Alex Williamson
2018-04-30 16:10             ` Alex Williamson
2018-05-03 13:16       ` Joerg Roedel [this message]
2018-05-03 13:16         ` Joerg Roedel
2018-04-18 11:40   ` [PATCH v6 6/7] vfio/type1: Add IOVA range capability support Shameer Kolothum
2018-04-18 11:40     ` Shameer Kolothum
2018-04-18 11:40     ` Shameer Kolothum
2018-04-18 11:40   ` [PATCH v6 7/7] vfio/type1: remove duplicate retrieval of reserved regions Shameer Kolothum
2018-04-18 11:40     ` Shameer Kolothum
2018-04-18 11:40     ` Shameer Kolothum
2018-05-24 18:20   ` [PATCH v6 0/7] vfio/type1: Add support for valid iova list management Alex Williamson
2018-05-24 18:20     ` Alex Williamson
2018-05-25  8:45     ` Shameerali Kolothum Thodi
     [not found]       ` <5FC3163CFD30C246ABAA99954A238FA8386EE591-WFPaWmAhWqtUuCJht5byYAK1hpo4iccwjNknBlVQO8k@public.gmane.org>
2018-05-25 20:54         ` Alex Williamson
2018-05-25 20:54           ` Alex Williamson
2018-05-25 20:54           ` Alex Williamson
2018-06-05 17:03           ` Alex Williamson
2018-06-06  6:52             ` Shameerali Kolothum Thodi
     [not found]               ` <5FC3163CFD30C246ABAA99954A238FA8386F783C-WFPaWmAhWqtUuCJht5byYAK1hpo4iccwjNknBlVQO8k@public.gmane.org>
2018-06-07 15:05                 ` Alex Williamson
2018-06-07 15:05                   ` Alex Williamson
2018-06-07 15:05                   ` Alex Williamson

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=20180503131648.GX15462@8bytes.org \
    --to=joro-zlv9swrftaidnm+yrofe0a@public.gmane.org \
    --cc=iommu-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org \
    --cc=kvm-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=linuxarm-hv44wF8Li93QT0dZR+AlfA@public.gmane.org \
    --cc=pmorel-23VcF4HTsmIX0ybBhKVfKdBPR1lH4CV8@public.gmane.org \
    --cc=shameerali.kolothum.thodi-hv44wF8Li93QT0dZR+AlfA@public.gmane.org \
    --cc=xuwei5-C8/M+/jPZTeaMJb+Lgu22Q@public.gmane.org \
    /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.