From: "Ashish Singhal via groups.io" <ashishsingha=nvidia.com@groups.io>
To: Laszlo Ersek <lersek@redhat.com>,
"devel@edk2.groups.io" <devel@edk2.groups.io>,
"quic_llindhol@quicinc.com" <quic_llindhol@quicinc.com>,
"ardb+tianocore@kernel.org" <ardb+tianocore@kernel.org>,
"sami.mujawar@arm.com" <sami.mujawar@arm.com>,
Jeff Brasen <jbrasen@nvidia.com>
Cc: Michael Kinney <michael.d.kinney@intel.com>,
"Liming Gao (Byosoft address)" <gaoliming@byosoft.com.cn>
Subject: Re: [edk2-devel] [PATCH] DynamicTablesPkg: Fix ETE _UID Creation
Date: Fri, 17 Nov 2023 22:14:43 +0000 [thread overview]
Message-ID: <BY5PR12MB5544BE2530849151A1FAF446BAB7A@BY5PR12MB5544.namprd12.prod.outlook.com> (raw)
In-Reply-To: <783347b8-2ea4-7dc4-7793-1d6d871fb47b@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 5325 bytes --]
It seems like my BZ account has been disabled and I am not able to create an issue there myself. Can one of you create it so that the bug can be fixed? I am meanwhile working to restore my account.
________________________________
From: Laszlo Ersek <lersek@redhat.com>
Sent: Friday, November 17, 2023 1:30 PM
To: Ashish Singhal <ashishsingha@nvidia.com>; devel@edk2.groups.io <devel@edk2.groups.io>; quic_llindhol@quicinc.com <quic_llindhol@quicinc.com>; ardb+tianocore@kernel.org <ardb+tianocore@kernel.org>; sami.mujawar@arm.com <sami.mujawar@arm.com>; Jeff Brasen <jbrasen@nvidia.com>
Cc: Michael Kinney <michael.d.kinney@intel.com>; Liming Gao (Byosoft address) <gaoliming@byosoft.com.cn>
Subject: Re: [edk2-devel] [PATCH] DynamicTablesPkg: Fix ETE _UID Creation
External email: Use caution opening links or attachments
On 11/17/23 17:37, Ashish Singhal wrote:
>
>
> ------------------------------------------------------------------------
> *From:* Laszlo Ersek <lersek@redhat.com>
> *Sent:* Friday, November 17, 2023 2:20 AM
> *To:* devel@edk2.groups.io <devel@edk2.groups.io>; Ashish Singhal
> <ashishsingha@nvidia.com>; quic_llindhol@quicinc.com
> <quic_llindhol@quicinc.com>; ardb+tianocore@kernel.org
> <ardb+tianocore@kernel.org>; sami.mujawar@arm.com
> <sami.mujawar@arm.com>; Jeff Brasen <jbrasen@nvidia.com>
> *Cc:* Michael Kinney <michael.d.kinney@intel.com>; Liming Gao (Byosoft
> address) <gaoliming@byosoft.com.cn>
> *Subject:* Re: [edk2-devel] [PATCH] DynamicTablesPkg: Fix ETE _UID Creation
>
> External email: Use caution opening links or attachments
>
>
> On 11/15/23 04:19, Ashish Singhal via groups.io wrote:
>> Just like CPU _UID, ETE UID also needs to be unique so
>> use AcpiProcessorUid instead of CpuName
>>
>> Signed-off-by: Ashish Singhal <ashishsingha@nvidia.com>
>> ---
>> .../Arm/AcpiSsdtCpuTopologyLibArm/SsdtCpuTopologyGenerator.c | 5 ++++-
>> 1 file changed, 4 insertions(+), 1 deletion(-)
>
> Is this a fixup for the recent feature
>
> [PATCH v3 00/11] Update MADT for ACPI 6.5, and add TRBE & ETE support
> https://edk2.groups.io/g/devel/message/108996
> <https://edk2.groups.io/g/devel/message/108996>
>
> ?
>
> If so, then I *think* this qualifies to be merged during the hard
> feature freeze (+Liming +Mike), but:
>
> - I think we should have a "Fixes:" tag in the commit message (for
> pointing out the commit that should have contained the code being
> added/updated now)
>
> - I think we should have a BZ too (also linked into the commit message).
>
> Laszlo
>
> Hello Laszlo,
>
> The issue was indeed introduced in the patch series you pointed to and
> precisely in the commit
> https://github.com/tianocore/edk2/commit/3ee23713e1ce09faa6fa66ee6799e3e336deb58b <https://github.com/tianocore/edk2/commit/3ee23713e1ce09faa6fa66ee6799e3e336deb58b>. This is indeed a bug and should ideally be fixed as soon as possible. Do you need me to file BZ bug and link that in commit message?
A BZ ticket would be great, yes. It helps with the release notes
(determining the contents of a release).
If/when you file the new BZ, please add the old BZ's URL to the See Also
field. ... Oh, wait, the original series didn't have a BZ. That's a pity.
Thanks
Laszlo
>
> Thanks
> Ashish
>
>>
>> diff --git a/DynamicTablesPkg/Library/Acpi/Arm/AcpiSsdtCpuTopologyLibArm/SsdtCpuTopologyGenerator.c b/DynamicTablesPkg/Library/Acpi/Arm/AcpiSsdtCpuTopologyLibArm/SsdtCpuTopologyGenerator.c
>> index 8228c7845a..724f33c660 100644
>> --- a/DynamicTablesPkg/Library/Acpi/Arm/AcpiSsdtCpuTopologyLibArm/SsdtCpuTopologyGenerator.c
>> +++ b/DynamicTablesPkg/Library/Acpi/Arm/AcpiSsdtCpuTopologyLibArm/SsdtCpuTopologyGenerator.c
>> @@ -359,6 +359,7 @@ CreateAmlCpcNode (
>>
>> @param [in] Generator The SSDT Cpu Topology generator.
>> @param [in] ParentNode Parent node to attach the Cpu node to.
>> + @param [in] GicCInfo CM_ARM_GICC_INFO object used to create the node.
>> @param [in] CpuName Value used to generate the node name.
>> @param [out] EtNodePtr If not NULL, return the created Cpu node.
>>
>> @@ -372,6 +373,7 @@ EFIAPI
>> CreateAmlEtd (
>> IN ACPI_CPU_TOPOLOGY_GENERATOR *Generator,
>> IN AML_NODE_HANDLE ParentNode,
>> + IN CM_ARM_GICC_INFO *GicCInfo,
>> IN UINT32 CpuName,
>> OUT AML_OBJECT_NODE_HANDLE *EtNodePtr OPTIONAL
>> )
>> @@ -397,7 +399,7 @@ CreateAmlEtd (
>>
>> Status = AmlCodeGenNameInteger (
>> "_UID",
>> - CpuName,
>> + GicCInfo->AcpiProcessorUid,
>> EtNode,
>> NULL
>> );
>> @@ -474,6 +476,7 @@ CreateAmlEtNode (
>> Status = CreateAmlEtd (
>> Generator,
>> Node,
>> + GicCInfo,
>> CpuName,
>> NULL
>> );
>
-=-=-=-=-=-=-=-=-=-=-=-
Groups.io Links: You receive all messages sent to this group.
View/Reply Online (#111419): https://edk2.groups.io/g/devel/message/111419
Mute This Topic: https://groups.io/mt/102598848/7686176
Group Owner: devel+owner@edk2.groups.io
Unsubscribe: https://edk2.groups.io/g/devel/unsub [rebecca@openfw.io]
-=-=-=-=-=-=-=-=-=-=-=-
[-- Attachment #2: Type: text/html, Size: 9238 bytes --]
next prev parent reply other threads:[~2023-11-17 22:14 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-15 3:19 [edk2-devel] [PATCH] DynamicTablesPkg: Fix ETE _UID Creation Ashish Singhal via groups.io
2023-11-15 16:21 ` Leif Lindholm
2023-11-15 16:24 ` Ashish Singhal via groups.io
2023-11-15 17:20 ` Leif Lindholm
2023-11-15 17:27 ` Ashish Singhal via groups.io
2023-11-17 9:20 ` Laszlo Ersek
2023-11-17 16:37 ` Ashish Singhal via groups.io
2023-11-17 20:30 ` Laszlo Ersek
2023-11-17 22:14 ` Ashish Singhal via groups.io [this message]
2023-11-20 16:07 ` edk2-stable202311: " Sami Mujawar
2023-11-21 1:04 ` 回复: " gaoliming via groups.io
2023-11-20 12:22 ` Sami Mujawar
2023-11-20 12:41 ` Sami Mujawar
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=BY5PR12MB5544BE2530849151A1FAF446BAB7A@BY5PR12MB5544.namprd12.prod.outlook.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