From: Lu Baolu <baolu.lu@linux.intel.com>
To: "Tian, Kevin" <kevin.tian@intel.com>, Joerg Roedel <joro@8bytes.org>
Cc: baolu.lu@linux.intel.com, "Raj, Ashok" <ashok.raj@intel.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"iommu@lists.linux-foundation.org"
<iommu@lists.linux-foundation.org>, Will Deacon <will@kernel.org>
Subject: Re: [PATCH v2 3/3] iommu/vt-d: Apply SATC policy
Date: Thu, 4 Feb 2021 10:13:55 +0800 [thread overview]
Message-ID: <c6956ddc-31d8-33dd-f99d-63d0ac006b8e@linux.intel.com> (raw)
In-Reply-To: <MWHPR11MB1886133A35BA369F7EF3014A8CB39@MWHPR11MB1886.namprd11.prod.outlook.com>
Hi Kevin,
On 2/4/21 9:59 AM, Tian, Kevin wrote:
>> From: Lu Baolu
>> Sent: Wednesday, February 3, 2021 5:33 PM
>>
>> From: Yian Chen<yian.chen@intel.com>
>>
>> Starting from Intel VT-d v3.2, Intel platform BIOS can provide a new SATC
>> table structure. SATC table lists a set of SoC integrated devices that
>> require ATC to work (VT-d specification v3.2, section 8.8). Furthermore,
> This statement is not accurate. The purpose of SATC is to tell whether a
> SoC integrated device has been validated to meet the isolation requirements
> of using device TLB. All devices listed in SATC can have ATC safely enabled by
> OS. In addition, there is a flag for each listed device for whether ATC is a
> functional requirement. However, above description only captured the last
> point.
You are right. This series only addresses the devices with the flag set
which have functional requirement for ATS.
>
>> the new version of IOMMU supports SoC device ATS in both its Scalable
>> mode
>> and legacy mode.
>>
>> When IOMMU is working in scalable mode, software must enable device ATS
>> support.
> "must enable" is misleading here. You need describe the policies for three
> categories:
>
> - SATC devices with ATC_REQUIRED=1
> - SATC devices with ATC_REQUIRED=0
> - devices not listed in SATC, or when SATC is missing
Yian is working on this part. We planed it for v5.13. He will bring it
up for discussion later.
>
>> On the other hand, when IOMMU is in legacy mode for whatever
>> reason, the hardware managed ATS will automatically take effect and the
>> SATC required devices can work transparently to the software. As the
> No background about hardware-managed ATS.
>
>> result, software shouldn't enable ATS on that device, otherwise duplicate
>> device TLB invalidations will occur.
> This description draws a equation between legacy mode and hardware
> managed ATS. Do we care about the scenario where there is no hardware
> managed ATS but people also want to turn on ATC in legacy mode?
The hardware managed ATS is defined in the platform specific
specification. The purpose of this hardware design is backward
compatibility - legacy OSes with no SM or ATS awareness still running
well on them.
>
> Thanks
> Kevin
>
Best regards,
baolu
next prev parent reply other threads:[~2021-02-04 2:24 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-03 9:33 [PATCH v2 0/3] iommu/vt-d: Add support for ACPI/SATC table Lu Baolu
2021-02-03 9:33 ` [PATCH v2 1/3] iommu/vt-d: Add new enum value and structure for SATC Lu Baolu
2021-02-03 9:33 ` [PATCH v2 2/3] iommu/vt-d: Parse SATC reporting structure Lu Baolu
2021-02-03 9:33 ` [PATCH v2 3/3] iommu/vt-d: Apply SATC policy Lu Baolu
2021-02-04 1:59 ` Tian, Kevin
2021-02-04 2:13 ` Lu Baolu [this message]
2021-02-03 9:48 ` [PATCH v2 0/3] iommu/vt-d: Add support for ACPI/SATC table 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=c6956ddc-31d8-33dd-f99d-63d0ac006b8e@linux.intel.com \
--to=baolu.lu@linux.intel.com \
--cc=ashok.raj@intel.com \
--cc=iommu@lists.linux-foundation.org \
--cc=joro@8bytes.org \
--cc=kevin.tian@intel.com \
--cc=linux-kernel@vger.kernel.org \
--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