From: Nicolin Chen <nicolinc@nvidia.com>
To: Baolu Lu <baolu.lu@linux.intel.com>
Cc: <jgg@nvidia.com>, <will@kernel.org>, <robin.murphy@arm.com>,
<bhelgaas@google.com>, <joro@8bytes.org>, <praan@google.com>,
<kevin.tian@intel.com>, <miko.lenczewski@arm.com>,
<linux-arm-kernel@lists.infradead.org>, <iommu@lists.linux.dev>,
<linux-kernel@vger.kernel.org>, <linux-pci@vger.kernel.org>,
<dan.j.williams@intel.com>, <jonathan.cameron@huawei.com>
Subject: Re: [PATCH v2 1/3] PCI: Allow ATS to be always on for CXL.cache capable devices
Date: Tue, 3 Mar 2026 12:15:19 -0800 [thread overview]
Message-ID: <aadBVxa6xQrOLXDt@Asurada-Nvidia> (raw)
In-Reply-To: <102ceb37-c89d-4bb0-a471-42ccffb40c34@linux.intel.com>
On Tue, Mar 03, 2026 at 11:18:10AM +0800, Baolu Lu wrote:
> On 2/24/26 06:52, Nicolin Chen wrote:
> > +/**
> > + * pci_ats_always_on - Whether the PCI device requires ATS to be always enabled
> > + * @pdev: the PCI device
> > + *
> > + * Returns true, if the PCI device requires non-PASID ATS function on an IOMMU
> > + * bypassed configuration.
>
> Including iommu-specific policies and configurations here might cause
> confusion. How about making it simply as: "Returns true if the PCI
> device requires ATS to be enabled for functional operation"?
Yea, that sounds good to me. Thanks!
Nicolin
next prev parent reply other threads:[~2026-03-03 20:15 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-23 22:52 [PATCH v2 0/3] Allow ATS to be always on for certain ATS-capable devices Nicolin Chen
2026-02-23 22:52 ` [PATCH v2 1/3] PCI: Allow ATS to be always on for CXL.cache capable devices Nicolin Chen
2026-02-24 11:55 ` Jonathan Cameron
2026-02-24 18:43 ` Nicolin Chen
2026-03-03 3:18 ` Baolu Lu
2026-03-03 20:15 ` Nicolin Chen [this message]
2026-02-23 22:52 ` [PATCH v2 2/3] PCI: Allow ATS to be always on for pre-CXL devices Nicolin Chen
2026-02-23 22:52 ` [PATCH v2 3/3] iommu/arm-smmu-v3: Allow ATS to be always on Nicolin Chen
2026-02-24 12:06 ` Jonathan Cameron
2026-02-24 14:51 ` Jason Gunthorpe
2026-02-24 15:57 ` Jonathan Cameron
2026-02-24 16:09 ` Jason Gunthorpe
2026-03-02 14:54 ` Jonathan Cameron
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=aadBVxa6xQrOLXDt@Asurada-Nvidia \
--to=nicolinc@nvidia.com \
--cc=baolu.lu@linux.intel.com \
--cc=bhelgaas@google.com \
--cc=dan.j.williams@intel.com \
--cc=iommu@lists.linux.dev \
--cc=jgg@nvidia.com \
--cc=jonathan.cameron@huawei.com \
--cc=joro@8bytes.org \
--cc=kevin.tian@intel.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=miko.lenczewski@arm.com \
--cc=praan@google.com \
--cc=robin.murphy@arm.com \
--cc=will@kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox