From: "PierreGondois" <pierre.gondois@arm.com>
To: devel@edk2.groups.io, sami.mujawar@arm.com
Cc: Alexei.Fedorov@arm.com, Matteo.Carlini@arm.com,
Ben.Adderson@arm.com, steven.price@arm.com,
Lorenzo.Pieralisi@arm.com, nd@arm.com
Subject: Re: [edk2-devel] [PATCH v2 7/8] DynamicTablesPkg: Update ArmNameSpaceObjects for IORT Rev E.b
Date: Mon, 18 Oct 2021 16:59:42 +0100 [thread overview]
Message-ID: <8a0c2fa7-2eb7-4a24-5c63-39e2f47f1285@arm.com> (raw)
In-Reply-To: <20210617095538.93280-8-sami.mujawar@arm.com>
Hi Sami,
With the small modifications:
Reviewed-by: Pierre Gondois <pierre.gondois@arm.com>
On 6/17/21 10:55, Sami Mujawar via groups.io wrote:
> Bugzilla: 3458 - Add support IORT Rev E.b specification updates
> (https://bugzilla.tianocore.org/show_bug.cgi?id=3458)
>
> The IO Remapping Table, Platform Design Document, Revision E.b,
> Feb 2021 (https://developer.arm.com/documentation/den0049/)
> introduces the following updates, collectively including the
> updates and errata fixes to Rev E and Rev E.a:
> - increments the IORT table revision to 3.
> - updates the node definition to add an 'Identifier' field.
> - adds definition of node type 6 - Reserved Memory Range node.
> - adds definition for Memory Range Descriptors.
> - adds flag to indicate PRI support for root complexes.
> - adds flag to indicate if the root complex supports forwarding
> of PASID information on translated transactions to the SMMU.
>
> Therefore, update the Arm namespace objects to:
> - add Identifier field to IORT nodes.
> - introduce enums to represent RMR nodes and Memory Range
> descriptors.
> - add definition of node type 6 - Reserved Memory Range node.
> - add definition for Memory Range Descriptors.
>
> Signed-off-by: Sami Mujawar <sami.mujawar@arm.com>
> ---
>
> Notes:
> v2:
> - No code change since v1. Re-sending with v2 series. [SAMI]
>
> DynamicTablesPkg/Include/ArmNameSpaceObjects.h | 58 ++++++++++++++++++++
> 1 file changed, 58 insertions(+)
>
> diff --git a/DynamicTablesPkg/Include/ArmNameSpaceObjects.h b/DynamicTablesPkg/Include/ArmNameSpaceObjects.h
> index 19dcae13b2191e5f0b03ea85edec1191d2a406bf..98143cb5df127273cdd75452170fa651372b3896 100644
> --- a/DynamicTablesPkg/Include/ArmNameSpaceObjects.h
> +++ b/DynamicTablesPkg/Include/ArmNameSpaceObjects.h
> @@ -58,6 +58,8 @@ typedef enum ArmObjectID {
> EArmObjGenericInitiatorAffinityInfo, ///< 34 - Generic Initiator Affinity
> EArmObjSerialPortInfo, ///< 35 - Generic Serial Port Info
> EArmObjCmn600Info, ///< 36 - CMN-600 Info
> + EArmObjRmr, ///< 37 - Reserved Memory Range Node
> + EArmObjMemoryRangeDescriptor, ///< 38 - Memory Range Descriptor
> EArmObjMax
> } EARM_OBJECT_ID;
>
> @@ -466,6 +468,9 @@ typedef struct CmArmItsGroupNode {
> UINT32 ItsIdCount;
> /// Reference token for the ITS identifier array
> CM_OBJECT_TOKEN ItsIdToken;
> +
> + /// Unique identifier for this node.
> + UINT32 Identifier;
Would it be possible to say in the description that this is part of the
common node header ?
As we cannot modify the order of the fields anymore, I understand this
cannot be upper, but this would help as the order is a bit confusing.
> } CM_ARM_ITS_GROUP_NODE;
>
> /** A structure that describes the
> @@ -497,6 +502,9 @@ typedef struct CmArmNamedComponentNode {
> the entry in the namespace for this object.
> */
> CHAR8* ObjectName;
> +
> + /// Unique identifier for this node.
> + UINT32 Identifier;
> } CM_ARM_NAMED_COMPONENT_NODE;
>
> /** A structure that describes the
> @@ -525,6 +533,9 @@ typedef struct CmArmRootComplexNode {
> UINT32 PciSegmentNumber;
> /// Memory address size limit
> UINT8 MemoryAddressSize;
> +
> + /// Unique identifier for this node.
> + UINT32 Identifier;
> } CM_ARM_ROOT_COMPLEX_NODE;
>
> /** A structure that describes the
> @@ -567,6 +578,9 @@ typedef struct CmArmSmmuV1SmmuV2Node {
> UINT32 SMMU_NSgCfgIrpt;
> /// SMMU_NSgCfgIrpt interrupt flags
> UINT32 SMMU_NSgCfgIrptFlags;
> +
> + /// Unique identifier for this node.
> + UINT32 Identifier;
> } CM_ARM_SMMUV1_SMMUV2_NODE;
>
> /** A structure that describes the
> @@ -603,6 +617,9 @@ typedef struct CmArmSmmuV3Node {
> UINT32 ProximityDomain;
> /// Index into the array of ID mapping
> UINT32 DeviceIdMappingIndex;
> +
> + /// Unique identifier for this node.
> + UINT32 Identifier;
> } CM_ARM_SMMUV3_NODE;
>
> /** A structure that describes the
> @@ -627,6 +644,9 @@ typedef struct CmArmPmcgNode {
>
> /// Reference token for the IORT node associated with this node
> CM_OBJECT_TOKEN ReferenceToken;
> +
> + /// Unique identifier for this node.
> + UINT32 Identifier;
> } CM_ARM_PMCG_NODE;
>
> /** A structure that describes the
> @@ -878,6 +898,44 @@ typedef struct CmArmCmn600Info {
> CM_ARM_EXTENDED_INTERRUPT DtcInterrupt[4];
> } CM_ARM_CMN_600_INFO;
>
> +/** A structure that describes the
> + RMR node for the Platform.
> +
> + ID: EArmObjRmr
> +*/
> +typedef struct CmArmRmrNode {
> + /// An unique token used to identify this object
> + CM_OBJECT_TOKEN Token;
> + /// Number of ID mappings
> + UINT32 IdMappingCount;
> + /// Reference token for the ID mapping array
> + CM_OBJECT_TOKEN IdMappingToken;
> +
> + /// Reserved Memory Range flags.
> + UINT32 Flags;
> +
> + /// Memory range descriptor count.
> + UINT32 MemRangeDescCount;
> + /// Reference token for the Memory Range descriptor array
> + CM_OBJECT_TOKEN MemRangeDescToken;
> +
> + /// Unique identifier for this node.
> + UINT32 Identifier;
The 'Identifier' field should be added above the 'Flags' as the
structure is a new and to respect the order of the spec.
> +} CM_ARM_RMR_NODE;
> +
> +/** A structure that describes the
> + Memory Range descriptor.
> +
> + ID: EArmObjMemoryRangeDescriptor
> +*/
> +typedef struct CmArmRmrDescriptor {
> + /// Base address.
> + UINT64 BaseAddress;
> +
> + /// Length.
> + UINT64 Length;
The exact names of the fields in the spec are:
-Physical Range offset
-Physical Range length
Would it be possible to add these names in the description ?
> +} CM_ARM_MEMORY_RANGE_DESCRIPTOR;
> +
> #pragma pack()
>
> #endif // ARM_NAMESPACE_OBJECTS_H_
next prev parent reply other threads:[~2021-10-18 15:59 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-17 9:55 [PATCH v2 0/8] IORT Rev E.b specification updates Sami Mujawar
2021-06-17 9:55 ` [PATCH v2 1/8] MdePkg: Fix IORT header file include guard Sami Mujawar
2021-06-17 18:19 ` Michael D Kinney
2021-06-21 11:08 ` [edk2-devel] " Sami Mujawar
2021-06-17 9:55 ` [PATCH v2 2/8] MdePkg: IORT header update for IORT Rev E.b spec Sami Mujawar
2021-06-28 7:53 ` Gao, Zhichao
2021-10-15 14:45 ` [edk2-devel] " PierreGondois
2021-06-17 9:55 ` [PATCH v2 3/8] ShellPkg: Acpiview: Abbreviate field names to preserve alignment Sami Mujawar
2021-06-28 7:53 ` Gao, Zhichao
2021-10-15 13:33 ` [edk2-devel] " PierreGondois
2021-06-17 9:55 ` [PATCH v2 4/8] ShellPkg: Acpiview: IORT parser update for IORT Rev E.b spec Sami Mujawar
2021-06-28 7:53 ` Gao, Zhichao
2021-06-17 9:55 ` [PATCH v2 5/8] DynamicTablesPkg: IORT set reference to Id array only if present Sami Mujawar
2021-10-15 15:22 ` [edk2-devel] " PierreGondois
2021-06-17 9:55 ` [PATCH v2 6/8] DynamicTablesPkg: IORT set reference to interrupt array " Sami Mujawar
2021-10-18 15:48 ` [edk2-devel] " PierreGondois
2021-06-17 9:55 ` [PATCH v2 7/8] DynamicTablesPkg: Update ArmNameSpaceObjects for IORT Rev E.b Sami Mujawar
2021-10-18 15:59 ` PierreGondois [this message]
2021-10-18 16:00 ` [edk2-devel] " PierreGondois
2021-06-17 9:55 ` [PATCH v2 8/8] DynamicTablesPkg: IORT generator updates for Rev E.b spec Sami Mujawar
2021-10-18 16:17 ` [edk2-devel] " PierreGondois
2021-06-18 0:49 ` 回复: [edk2-devel] [PATCH v2 0/8] IORT Rev E.b specification updates gaoliming
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-list 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=8a0c2fa7-2eb7-4a24-5c63-39e2f47f1285@arm.com \
--to=devel@edk2.groups.io \
/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