All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jason Gunthorpe via iommu <iommu@lists.linux-foundation.org>
To: Yi Liu <yi.l.liu@intel.com>
Cc: "Tian, Kevin" <kevin.tian@intel.com>,
	"Raj, Ashok" <ashok.raj@intel.com>,
	Robin Murphy <robin.murphy@arm.com>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	Christoph Hellwig <hch@infradead.org>,
	Jean-Philippe Brucker <jean-philippe@linaro.com>,
	"iommu@lists.linux-foundation.org"
	<iommu@lists.linux-foundation.org>,
	"Pan, Jacob jun" <jacob.jun.pan@intel.com>,
	Will Deacon <will@kernel.org>
Subject: Re: [PATCH RFC v2 02/11] iommu: Add iommu_group_singleton_lockdown()
Date: Fri, 1 Apr 2022 08:52:12 -0300	[thread overview]
Message-ID: <20220401115212.GJ2120790@nvidia.com> (raw)
In-Reply-To: <81ea9536-ba36-deef-b849-6b407b5409e0@intel.com>

On Fri, Apr 01, 2022 at 02:20:23PM +0800, Yi Liu wrote:
> 
> 
> On 2022/3/29 19:42, Jason Gunthorpe wrote:
> > On Tue, Mar 29, 2022 at 08:42:13AM +0000, Tian, Kevin wrote:
> > 
> > > btw I'm not sure whether this is what SVA requires. IIRC the problem with
> > > SVA is because PASID TLP prefix is not counted in PCI packet routing thus
> > > a DMA target address with PASID might be treated as P2P if the address
> > > falls into the MMIO BAR of other devices in the group. This is why the
> > > original code needs to strictly apply SVA in a group containing a single
> > > device, instead of a group attached by a single driver, unless we want to
> > > reserve those MMIO ranges in CPU VA space.
> > 
> > I think it is not such a good idea to mix up group with this test
> > 
> > Here you want to say that all TLPs from the RID route to the host
> > bridge - ie ACS is on/etc. This is subtly different from a group with
> > a single device. Specifically it is an immutable property of the
> > fabric and doesn't change after hot plug events.
> 
> so the group size can be immutable for specific topology. right? I think for
> non-multi-function devices plugged behind an PCIE bridge which has enabled
> ACS, such devices should have their own groups. Under such topology the
> group size should be 1 constantly. May just enable SVA for such devices.

Like I said, you should stop thinking about group size.

You need to know that 100% of TLPs translate through the IOMMU to
enable SVA, nothing less will do, and that property has nothing to do
with group size.

> > ie if we have a singleton group that doesn't have ACS and someone
> > hotplugs in another device on a bridge, then our SVA is completely
> > broken and we get data corruption.
> 
> I think this may be a device plugged in a PCIE-to-PCI bridge, and then
> hotplug a device to this bridge. The group size is variable. right? Per my
> understanding, maybe such a bridge cannot support PASID Prefix at all, hence
> no SVA support for such devices.

Any PCIE-to-PCIE bridge will do, don't ned to involve legacy PCI here
to have hotplug problems.

Jason
_______________________________________________
iommu mailing list
iommu@lists.linux-foundation.org
https://lists.linuxfoundation.org/mailman/listinfo/iommu

WARNING: multiple messages have this Message-ID (diff)
From: Jason Gunthorpe <jgg@nvidia.com>
To: Yi Liu <yi.l.liu@intel.com>
Cc: "Tian, Kevin" <kevin.tian@intel.com>,
	Lu Baolu <baolu.lu@linux.intel.com>,
	Joerg Roedel <joro@8bytes.org>,
	Christoph Hellwig <hch@infradead.org>,
	"Raj, Ashok" <ashok.raj@intel.com>, Will Deacon <will@kernel.org>,
	Robin Murphy <robin.murphy@arm.com>,
	Jean-Philippe Brucker <jean-philippe@linaro.com>,
	Eric Auger <eric.auger@redhat.com>,
	"Pan, Jacob jun" <jacob.jun.pan@intel.com>,
	"iommu@lists.linux-foundation.org"
	<iommu@lists.linux-foundation.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH RFC v2 02/11] iommu: Add iommu_group_singleton_lockdown()
Date: Fri, 1 Apr 2022 08:52:12 -0300	[thread overview]
Message-ID: <20220401115212.GJ2120790@nvidia.com> (raw)
In-Reply-To: <81ea9536-ba36-deef-b849-6b407b5409e0@intel.com>

On Fri, Apr 01, 2022 at 02:20:23PM +0800, Yi Liu wrote:
> 
> 
> On 2022/3/29 19:42, Jason Gunthorpe wrote:
> > On Tue, Mar 29, 2022 at 08:42:13AM +0000, Tian, Kevin wrote:
> > 
> > > btw I'm not sure whether this is what SVA requires. IIRC the problem with
> > > SVA is because PASID TLP prefix is not counted in PCI packet routing thus
> > > a DMA target address with PASID might be treated as P2P if the address
> > > falls into the MMIO BAR of other devices in the group. This is why the
> > > original code needs to strictly apply SVA in a group containing a single
> > > device, instead of a group attached by a single driver, unless we want to
> > > reserve those MMIO ranges in CPU VA space.
> > 
> > I think it is not such a good idea to mix up group with this test
> > 
> > Here you want to say that all TLPs from the RID route to the host
> > bridge - ie ACS is on/etc. This is subtly different from a group with
> > a single device. Specifically it is an immutable property of the
> > fabric and doesn't change after hot plug events.
> 
> so the group size can be immutable for specific topology. right? I think for
> non-multi-function devices plugged behind an PCIE bridge which has enabled
> ACS, such devices should have their own groups. Under such topology the
> group size should be 1 constantly. May just enable SVA for such devices.

Like I said, you should stop thinking about group size.

You need to know that 100% of TLPs translate through the IOMMU to
enable SVA, nothing less will do, and that property has nothing to do
with group size.

> > ie if we have a singleton group that doesn't have ACS and someone
> > hotplugs in another device on a bridge, then our SVA is completely
> > broken and we get data corruption.
> 
> I think this may be a device plugged in a PCIE-to-PCI bridge, and then
> hotplug a device to this bridge. The group size is variable. right? Per my
> understanding, maybe such a bridge cannot support PASID Prefix at all, hence
> no SVA support for such devices.

Any PCIE-to-PCIE bridge will do, don't ned to involve legacy PCI here
to have hotplug problems.

Jason

  reply	other threads:[~2022-04-01 11:52 UTC|newest]

Thread overview: 124+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-29  5:37 [PATCH RFC v2 00/11] iommu: SVA and IOPF refactoring Lu Baolu
2022-03-29  5:37 ` Lu Baolu
2022-03-29  5:37 ` [PATCH RFC v2 01/11] iommu: Add pasid_bits field in struct dev_iommu Lu Baolu
2022-03-29  5:37   ` Lu Baolu
2022-03-29 21:00   ` Jacob Pan
2022-03-29 21:00     ` Jacob Pan
2022-03-30  4:30     ` Lu Baolu
2022-03-30  4:30       ` Lu Baolu
2022-03-30  7:05   ` Tian, Kevin
2022-03-30  7:05     ` Tian, Kevin
2022-03-30 11:58     ` Lu Baolu
2022-03-30 11:58       ` Lu Baolu
2022-03-29  5:37 ` [PATCH RFC v2 02/11] iommu: Add iommu_group_singleton_lockdown() Lu Baolu
2022-03-29  5:37   ` Lu Baolu
2022-03-29  8:42   ` Tian, Kevin
2022-03-29  8:42     ` Tian, Kevin
2022-03-29 11:42     ` Jason Gunthorpe via iommu
2022-03-29 11:42       ` Jason Gunthorpe
2022-03-30  6:50       ` Tian, Kevin
2022-03-30  6:50         ` Tian, Kevin
2022-03-30 11:57         ` Lu Baolu
2022-03-30 11:57           ` Lu Baolu
2022-03-30 11:58         ` Jason Gunthorpe via iommu
2022-03-30 11:58           ` Jason Gunthorpe
2022-03-30 14:12           ` Tian, Kevin
2022-03-30 14:12             ` Tian, Kevin
2022-03-30 14:30             ` Jason Gunthorpe via iommu
2022-03-30 14:30               ` Jason Gunthorpe
2022-04-02  7:12               ` Tian, Kevin
2022-04-02  7:12                 ` Tian, Kevin
2022-04-02 23:29                 ` Jason Gunthorpe via iommu
2022-04-02 23:29                   ` Jason Gunthorpe
2022-04-06 10:02                 ` Lu Baolu
2022-04-06 10:02                   ` Lu Baolu
2022-04-06 10:44                   ` Tian, Kevin
2022-04-06 10:44                     ` Tian, Kevin
2022-04-06 11:03                     ` Lu Baolu
2022-04-06 11:03                       ` Lu Baolu
2022-04-06 23:56                       ` Tian, Kevin
2022-04-06 23:56                         ` Tian, Kevin
2022-03-30 14:18           ` Tian, Kevin
2022-03-30 14:18             ` Tian, Kevin
2022-03-30 15:04             ` Alex Williamson
2022-03-30 15:04               ` Alex Williamson
2022-04-04  5:43           ` Lu Baolu
2022-04-04  5:43             ` Lu Baolu
2022-04-04 17:24             ` Jason Gunthorpe via iommu
2022-04-04 17:24               ` Jason Gunthorpe
2022-04-05  6:12               ` Lu Baolu
2022-04-05  6:12                 ` Lu Baolu
2022-04-05 14:10                 ` Jason Gunthorpe via iommu
2022-04-05 14:10                   ` Jason Gunthorpe
2022-04-06  9:51                   ` Lu Baolu
2022-04-06  9:51                     ` Lu Baolu
2022-04-01  6:20       ` Yi Liu
2022-04-01  6:20         ` Yi Liu
2022-04-01 11:52         ` Jason Gunthorpe via iommu [this message]
2022-04-01 11:52           ` Jason Gunthorpe
2022-03-30  4:59     ` Lu Baolu
2022-03-30  4:59       ` Lu Baolu
2022-03-30  6:55       ` Tian, Kevin
2022-03-30  6:55         ` Tian, Kevin
2022-04-01  5:49     ` Yi Liu
2022-04-01  5:49       ` Yi Liu
2022-03-29  5:37 ` [PATCH RFC v2 03/11] iommu/sva: Add iommu_domain type for SVA Lu Baolu
2022-03-29  5:37   ` Lu Baolu
2022-03-29 21:38   ` Jacob Pan
2022-03-29 21:38     ` Jacob Pan
2022-03-30  4:35     ` Lu Baolu
2022-03-30  4:35       ` Lu Baolu
2022-03-30 19:02   ` Jason Gunthorpe via iommu
2022-03-30 19:02     ` Jason Gunthorpe
2022-04-02  8:43     ` Tian, Kevin
2022-04-02  8:43       ` Tian, Kevin
2022-04-02 23:32       ` Jason Gunthorpe via iommu
2022-04-02 23:32         ` Jason Gunthorpe
2022-04-04  6:09         ` Lu Baolu
2022-04-04  6:09           ` Lu Baolu
2022-04-06  1:00         ` Tian, Kevin
2022-04-06  1:00           ` Tian, Kevin
2022-04-06  1:23           ` Jason Gunthorpe via iommu
2022-04-06  1:23             ` Jason Gunthorpe
2022-04-06  5:58             ` Tian, Kevin
2022-04-06  5:58               ` Tian, Kevin
2022-04-06 12:32               ` Robin Murphy
2022-04-06 12:32                 ` Robin Murphy
2022-04-06 13:06                 ` Jason Gunthorpe via iommu
2022-04-06 13:06                   ` Jason Gunthorpe
2022-04-06 13:37                   ` Robin Murphy
2022-04-06 13:37                     ` Robin Murphy
2022-04-06 14:01                     ` Jason Gunthorpe via iommu
2022-04-06 14:01                       ` Jason Gunthorpe
2022-04-07  0:11                 ` Tian, Kevin
2022-04-07  0:11                   ` Tian, Kevin
2022-03-29  5:37 ` [PATCH RFC v2 04/11] iommu: Add attach/detach_dev_pasid domain ops Lu Baolu
2022-03-29  5:37   ` Lu Baolu
2022-03-30 19:08   ` Jason Gunthorpe via iommu
2022-03-30 19:08     ` Jason Gunthorpe
2022-04-04  6:47     ` Lu Baolu
2022-04-04  6:47       ` Lu Baolu
2022-03-29  5:37 ` [PATCH RFC v2 05/11] iommu/vt-d: Remove SVM_FLAG_SUPERVISOR_MODE suport Lu Baolu
2022-03-29  5:37   ` Lu Baolu
2022-03-29  5:37 ` [PATCH RFC v2 06/11] iommu/vt-d: Add SVA domain support Lu Baolu
2022-03-29  5:37   ` Lu Baolu
2022-03-30 19:09   ` Jason Gunthorpe via iommu
2022-03-30 19:09     ` Jason Gunthorpe
2022-04-04  6:52     ` Lu Baolu
2022-04-04  6:52       ` Lu Baolu
2022-03-29  5:37 ` [PATCH RFC v2 07/11] arm-smmu-v3/sva: " Lu Baolu
2022-03-29  5:37   ` Lu Baolu
2022-03-29  5:37 ` [PATCH RFC v2 08/11] iommu/sva: Use attach/detach_pasid_dev in SVA interfaces Lu Baolu
2022-03-29  5:37   ` Lu Baolu
2022-03-31 20:59   ` Jacob Pan
2022-03-31 20:59     ` Jacob Pan
2022-03-31 22:26     ` Jason Gunthorpe via iommu
2022-03-31 22:26       ` Jason Gunthorpe
2022-04-04  5:55       ` Lu Baolu
2022-04-04  5:55         ` Lu Baolu
2022-03-29  5:37 ` [PATCH RFC v2 09/11] iommu: Remove SVA related callbacks from iommu ops Lu Baolu
2022-03-29  5:37   ` Lu Baolu
2022-03-29  5:37 ` [PATCH RFC v2 10/11] iommu: Per-domain I/O page fault handling Lu Baolu
2022-03-29  5:37   ` Lu Baolu
2022-03-29  5:38 ` [PATCH RFC v2 11/11] iommu: Rename iommu-sva-lib.{c,h} Lu Baolu
2022-03-29  5:38   ` Lu Baolu

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=20220401115212.GJ2120790@nvidia.com \
    --to=iommu@lists.linux-foundation.org \
    --cc=ashok.raj@intel.com \
    --cc=hch@infradead.org \
    --cc=jacob.jun.pan@intel.com \
    --cc=jean-philippe@linaro.com \
    --cc=jgg@nvidia.com \
    --cc=kevin.tian@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=robin.murphy@arm.com \
    --cc=will@kernel.org \
    --cc=yi.l.liu@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.