From: Baolu Lu <baolu.lu@linux.intel.com>
To: "Tian, Kevin" <kevin.tian@intel.com>,
Jason Gunthorpe <jgg@nvidia.com>,
Robin Murphy <robin.murphy@arm.com>
Cc: baolu.lu@linux.intel.com,
"iommu@lists.linux.dev" <iommu@lists.linux.dev>,
Joerg Roedel <joro@8bytes.org>, Will Deacon <will@kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 1/1] iommu/vt-d: Add opt-in for ATS support on discrete devices
Date: Fri, 3 Mar 2023 17:51:00 +0800 [thread overview]
Message-ID: <6e60e491-e3db-6342-28be-8cdce2843543@linux.intel.com> (raw)
In-Reply-To: <BN9PR11MB5276F192BCECE567DBFE21C08CB39@BN9PR11MB5276.namprd11.prod.outlook.com>
On 2023/3/3 16:19, Tian, Kevin wrote:
> But Baolu, seems there is a small bug on handling satcu->atc_required.
> This indicates that ATS must be enabled as a functional requirement.
> Then we should handle the failure of pci_enable_ats() on such device.
Yes. We have people working on this. For example, when pci=noats is opt-
in, pci_enable_ats() definitely will return failure.
Best regards,
baolu
next prev parent reply other threads:[~2023-03-03 9:51 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-28 2:33 [PATCH 1/1] iommu/vt-d: Add opt-in for ATS support on discrete devices Lu Baolu
2023-02-28 12:23 ` Jason Gunthorpe
2023-03-01 4:22 ` Baolu Lu
2023-03-01 14:04 ` Jason Gunthorpe
2023-03-01 17:15 ` Robin Murphy
2023-03-01 17:42 ` Jason Gunthorpe
2023-03-01 18:19 ` Robin Murphy
2023-03-02 2:30 ` Baolu Lu
2023-03-03 8:19 ` Tian, Kevin
2023-03-03 9:51 ` Baolu Lu [this message]
2023-03-03 13:18 ` Jason Gunthorpe
2023-03-07 5:20 ` Tian, Kevin
2023-03-02 1:56 ` Baolu Lu
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=6e60e491-e3db-6342-28be-8cdce2843543@linux.intel.com \
--to=baolu.lu@linux.intel.com \
--cc=iommu@lists.linux.dev \
--cc=jgg@nvidia.com \
--cc=joro@8bytes.org \
--cc=kevin.tian@intel.com \
--cc=linux-kernel@vger.kernel.org \
--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 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.