From: Hanjun Guo <guohanjun@huawei.com>
To: Jason Gunthorpe <jgg@ziepe.ca>, Vidya Sagar <vidyas@nvidia.com>
Cc: <rafael@kernel.org>, <lenb@kernel.org>, <saket.dumbre@intel.com>,
<lpieralisi@kernel.org>, <sudeep.holla@kernel.org>,
<will@kernel.org>, <catalin.marinas@arm.com>, <joro@8bytes.org>,
<robin.murphy@arm.com>, <nicolinc@nvidia.com>, <praan@google.com>,
<vsethi@nvidia.com>, <sdonthineni@nvidia.com>,
<kthota@nvidia.com>, <sagar.tv@gmail.com>,
<linux-acpi@vger.kernel.org>,
<linux-arm-kernel@lists.infradead.org>,
<acpica-devel@lists.linux.dev>, <iommu@lists.linux.dev>,
<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH V1 1/3] ACPICA: IORT: Add Root Complex PASID Flags field
Date: Tue, 28 Apr 2026 20:32:12 +0800 [thread overview]
Message-ID: <e092b85e-9ac2-22ef-b213-1b2a32fbf784@huawei.com> (raw)
In-Reply-To: <20260423224318.GT3611611@ziepe.ca>
On 2026/4/24 6:43, Jason Gunthorpe wrote:
> On Fri, Apr 24, 2026 at 12:44:15AM +0530, Vidya Sagar wrote:
>> The IORT spec, Issue E.c (ARM DEN 0049E.c, January 2022), bumps the
>> Root Complex Node to revision 4 and adds two PASID descriptors:
>>
>> - PASID Capabilities at byte offset 33 (2 bytes), bits[4:0] of which
>> report the Max PASID Width supported by the Root Complex.
>> - Flags at byte offset 36 (4 bytes), bit 0 of which reports whether
>> the Root Complex itself supports PASID. This is distinct from the
>> existing ATS Attribute bit 2 (at offset 24) that only reports
>> whether the RC forwards PASID information on translated
>> transactions.
>>
>> The ACPICA struct in include/acpi/actbl2.h was updated for the E.c
>> PASID Capabilities descriptor (offset 33) but stops short with a
>> trailing 'u8 reserved[]' flexible array, so the new Flags field at
>> offset 36 is unreachable and the existing ACPI_IORT_PASID_*
>> definitions have no consumer.
>>
>> Replace the trailing flexible array with a fixed 'u8 reserved[1]'
>> followed by 'u32 flags' so the struct fully covers RC node revision 4,
>> and add the ACPI_IORT_RC_PASID_SUPPORTED mask for bit 0 of the new
>> field. With #pragma pack(1) in effect for actbl2.h, this lands the new
>> field at the spec-mandated absolute offset 36.
>>
>> Signed-off-by: Vidya Sagar <vidyas@nvidia.com>
>> ---
>> include/acpi/actbl2.h | 6 +++++-
>> 1 file changed, 5 insertions(+), 1 deletion(-)
>
> There is a whole process to change this file, I went through it once
> for canwbs..
>
> https://lore.kernel.org/acpica-devel/2-v3-e2e16cd7467f+2a6a1-smmuv3_nesting_jgg@nvidia.com/
>
> You have to make a pull request here:
>
> https://github.com/acpica/acpica/pulls
Yes, please get this patch merged in ACPICA first.
Thanks
Hanjun
next prev parent reply other threads:[~2026-04-28 12:34 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-23 19:14 [PATCH V1 0/3] ACPI/IORT: Honor Root Complex PASID descriptors on SMMUv3 Vidya Sagar
2026-04-23 19:14 ` [PATCH V1 1/3] ACPICA: IORT: Add Root Complex PASID Flags field Vidya Sagar
2026-04-23 22:43 ` Jason Gunthorpe
2026-04-28 12:32 ` Hanjun Guo [this message]
2026-04-23 19:14 ` [PATCH V1 2/3] ACPI/IORT: Plumb Root Complex PASID descriptors into iommu_fwspec Vidya Sagar
2026-04-23 19:14 ` [PATCH V1 3/3] iommu/arm-smmu-v3: Honor IORT Root Complex PASID descriptors Vidya Sagar
2026-04-23 22:45 ` Jason Gunthorpe
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=e092b85e-9ac2-22ef-b213-1b2a32fbf784@huawei.com \
--to=guohanjun@huawei.com \
--cc=acpica-devel@lists.linux.dev \
--cc=catalin.marinas@arm.com \
--cc=iommu@lists.linux.dev \
--cc=jgg@ziepe.ca \
--cc=joro@8bytes.org \
--cc=kthota@nvidia.com \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lpieralisi@kernel.org \
--cc=nicolinc@nvidia.com \
--cc=praan@google.com \
--cc=rafael@kernel.org \
--cc=robin.murphy@arm.com \
--cc=sagar.tv@gmail.com \
--cc=saket.dumbre@intel.com \
--cc=sdonthineni@nvidia.com \
--cc=sudeep.holla@kernel.org \
--cc=vidyas@nvidia.com \
--cc=vsethi@nvidia.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