mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Vasant Hegde <vasant.hegde@amd.com>
To: "Mario Limonciello (AMD)" <superm1@kernel.org>,
	Jason Gunthorpe <jgg@ziepe.ca>
Cc: Alex Deucher <alexander.deucher@amd.com>,
	Joerg Roedel <joro@8bytes.org>,
	Suravee Suthikulpanit <suravee.suthikulpanit@amd.com>,
	"open list:RADEON and AMDGPU DRM DRIVERS"
	<amd-gfx@lists.freedesktop.org>,
	open list <linux-kernel@vger.kernel.org>,
	"open list:AMD IOMMU (AMD-VI)" <iommu@lists.linux.dev>
Subject: Re: [PATCH v4] iommu/amd: Make PerfOpt compulsory
Date: Thu, 22 Oct 2026 16:31:33 +0530	[thread overview]
Message-ID: <db52eac7-d3c2-45fe-ad95-ec7e0dda6a1a@amd.com> (raw)
In-Reply-To: <20261001182410.1525285-1-superm1@kernel.org>

Mario,


On 10/1/2026 11:54 PM, Mario Limonciello (AMD) wrote:
> PerfOpt is only a feature usable by integrated GPUs and only in identity
> mode.  Instead of leaving a policy knob in amdgpu, just turn it on when
> an integrated GPU is in identity.
> 
> PerfOpt locks the GPU into identity mode where the DTE is ignored, so mark
> it require_direct (blocks VFIO/iommufd claims) and disable PASID (no GCR3
> table in the fast path).
> 
> This drops quite a bit of compatibility glue.  There was a refcounting
> system, exported symbols, and device attach/detach logic.  By just setting
> it immediately it's a lot more straightforward.

I believe its good to get this merged in this cycle itself so that we can get
rid of the command line options introduced earlier.

I have looked into this patch again. How about somthing like below:

  - Do not call amd_iommu_perfopt_set() in early_enable_iommu() path
    Because it enables feature on all IOMMUs even though it may not have iGPUs

  - amd_iommu_def_domain_type:
    mark device PerfOpt-eligible
    select identity

  - identity attach:
    Enable IOMMU perfOpt feature

  - DMA / Blocked domain
    Disable IOMMU perfOpt feature

  - resume:
    restore hardware bit


-Vasant


      parent reply	other threads:[~2026-10-22 11:01 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-01 18:24 Mario Limonciello (AMD)
2026-10-02  3:44 ` Vasant Hegde
2026-10-02  3:57   ` Mario Limonciello
2026-10-02 11:46     ` Jason Gunthorpe
2026-10-22 11:01 ` Vasant Hegde [this message]

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=db52eac7-d3c2-45fe-ad95-ec7e0dda6a1a@amd.com \
    --to=vasant.hegde@amd.com \
    --cc=alexander.deucher@amd.com \
    --cc=amd-gfx@lists.freedesktop.org \
    --cc=iommu@lists.linux.dev \
    --cc=jgg@ziepe.ca \
    --cc=joro@8bytes.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=superm1@kernel.org \
    --cc=suravee.suthikulpanit@amd.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®