All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jason Gunthorpe <jgg@nvidia.com>
To: "Deucher, Alexander" <Alexander.Deucher@amd.com>
Cc: "Hegde, Vasant" <Vasant.Hegde@amd.com>,
	Baolu Lu <baolu.lu@linux.intel.com>,
	"iommu@lists.linux.dev" <iommu@lists.linux.dev>,
	"joro@8bytes.org" <joro@8bytes.org>,
	"Suthikulpanit, Suravee" <Suravee.Suthikulpanit@amd.com>,
	"Huang2, Wei" <Wei.Huang2@amd.com>,
	"jsnitsel@redhat.com" <jsnitsel@redhat.com>,
	"Kuehling, Felix" <Felix.Kuehling@amd.com>
Subject: Re: [PATCH v3 1/5] iommu/amd: Remove iommu_v2 module
Date: Mon, 25 Sep 2023 13:37:49 -0300	[thread overview]
Message-ID: <20230925163749.GI13733@nvidia.com> (raw)
In-Reply-To: <BL1PR12MB5144CE1D387F3903D121AAA9F7FCA@BL1PR12MB5144.namprd12.prod.outlook.com>

On Mon, Sep 25, 2023 at 04:31:50PM +0000, Deucher, Alexander wrote:

> > On 9/22/2023 5:30 PM, Jason Gunthorpe wrote:
> > > On Fri, Sep 22, 2023 at 02:22:11PM +0530, Vasant Hegde wrote:
> > >>> 2) PCI device supports ATS and PASID
> > >>>    In this case, ATS is required for PRI, so we should enable it
> > >>> even if
> > >>>    the default domain has been configured to PASSTHROUGH mode.
> > >>
> > >> IMO we should enable ATS along with enable_feature(PRI).
> > >
> > > Definately not. ATS is valuable and importnat without PRI.
> >
> > I get that. But I am not sure whether I understood the usecase when domain is
> > in passthrough mode. Do you have any usecase to enable ATS when device is
> > in pass through mode?
> 
> It should still reduce latency.  Even in 1:1 mode, there is still an
> address lookup that can be cached.

Oh, on a lot of devices the ATS bits just enable device's PCI to issue
ATS, it doesn't mean that *every* operation has to be ATS.

So the non-SVA transactions can freely run in non-ATS mode with 1:1
while only SVA operations use ATS.

IIRC most IOMMU still have a lookup for a translated request to
validate that the RID is authorized to use them. So there is no
savings, just overhead.

Jason

  reply	other threads:[~2023-09-25 16:37 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-21  9:31 [PATCH v3 0/5] iommu/amd: SVA Support (part 2) - deprecate iommu_v2 module Vasant Hegde
2023-09-21  9:31 ` [PATCH v3 1/5] iommu/amd: Remove " Vasant Hegde
2023-09-21 14:05   ` Deucher, Alexander
2023-09-21 14:14     ` Jason Gunthorpe
2023-09-21 15:15       ` Deucher, Alexander
2023-09-21 16:31         ` Jason Gunthorpe
2023-09-22  2:23           ` Baolu Lu
2023-09-22  8:52             ` Vasant Hegde
2023-09-22 12:00               ` Jason Gunthorpe
2023-09-25 15:11                 ` Vasant Hegde
2023-09-25 15:57                   ` Jason Gunthorpe
2023-09-25 16:31                   ` Deucher, Alexander
2023-09-25 16:37                     ` Jason Gunthorpe [this message]
2023-09-22 11:59             ` Jason Gunthorpe
2023-09-22 12:13               ` Baolu Lu
2023-09-22 12:18                 ` Jason Gunthorpe
2023-09-22 12:42                   ` Baolu Lu
2023-09-22 12:43                     ` Jason Gunthorpe
2023-09-25  9:04                   ` joro
2023-09-25 15:40                     ` Vasant Hegde
2023-09-28 14:52                     ` Deucher, Alexander
2023-10-05 11:29                       ` Vasant Hegde
2023-10-06 15:19                         ` Deucher, Alexander
2023-09-22 18:08                 ` Deucher, Alexander
2023-09-22 18:15           ` Deucher, Alexander
2023-09-22  6:45         ` Vasant Hegde
2023-09-22 18:13           ` Deucher, Alexander
2023-09-25 15:30             ` Vasant Hegde
2023-09-21  9:31 ` [PATCH v3 2/5] iommu/amd: Remove PPR support Vasant Hegde
2023-09-21  9:31 ` [PATCH v3 3/5] iommu/amd: Remove amd_iommu_device_info() Vasant Hegde
2023-09-21  9:31 ` [PATCH v3 4/5] iommu/amd: Remove unused EXPORT_SYMBOLS Vasant Hegde
2023-09-21  9:31 ` [PATCH v3 5/5] Revert "iommu: Fix false ownership failure on AMD systems with PASID activated" Vasant Hegde
2023-10-02  6:32 ` [PATCH v3 0/5] iommu/amd: SVA Support (part 2) - deprecate iommu_v2 module Joerg Roedel
2023-10-05 11:30   ` Vasant Hegde

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=20230925163749.GI13733@nvidia.com \
    --to=jgg@nvidia.com \
    --cc=Alexander.Deucher@amd.com \
    --cc=Felix.Kuehling@amd.com \
    --cc=Suravee.Suthikulpanit@amd.com \
    --cc=Vasant.Hegde@amd.com \
    --cc=Wei.Huang2@amd.com \
    --cc=baolu.lu@linux.intel.com \
    --cc=iommu@lists.linux.dev \
    --cc=joro@8bytes.org \
    --cc=jsnitsel@redhat.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.