public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: "Jeshua Smith via groups.io" <jeshuas=nvidia.com@groups.io>
To: Pierre Gondois <pierre.gondois@arm.com>,
	"devel@edk2.groups.io" <devel@edk2.groups.io>
Cc: "ardb+tianocore@kernel.org" <ardb+tianocore@kernel.org>,
	"quic_llindhol@quicinc.com" <quic_llindhol@quicinc.com>,
	"Sami.Mujawar@arm.com" <Sami.Mujawar@arm.com>,
	Shanker Donthineni <sdonthineni@nvidia.com>,
	Vikram Sethi <vsethi@nvidia.com>,
	Ashish Singhal <ashishsingha@nvidia.com>
Subject: Re: [edk2-devel] [PATCH] DynamicTablesPkg/SSDT: Remove incorrect root node check
Date: Tue, 9 Jan 2024 16:55:23 +0000	[thread overview]
Message-ID: <DM6PR12MB3371B05774C6FA9F02E673FDDB6A2@DM6PR12MB3371.namprd12.prod.outlook.com> (raw)
In-Reply-To: <a7ee4ee6-375c-4f34-bfcb-a65b83b71da5@arm.com>

> > Two physical packages are on a multi-chip module and share resources on
> the module. The module then plugs into the baseboard/motherboard.
> 
> Is it possible to elaborate on the resource being shared ?

In our specific case the problem is related to the PPTT's "Identical Implementation" flag. We need a top level node above the physical package nodes to be able to set the "Identical Implementation" flag to indicate that all of the procs in all of the child packages are the same identical implementation. Without this (ie. forcing each physical package to be its own root node) Linux will fail to load the SPE driver when there are multiple identical packages because it detects that some of the procs have a different root node than other procs, implying that the packages don't have identical implementations.

> Does it fall into the subject of this thread ? Some resources might be aswell
> described in other ACPI tables.

The thread you linked looks like it is about non-processor resources, and therefore wasn't in scope for PPTT. I don't think this is related.

> > Note: While investigating this we noticed that another vendor also has a
> similar PPTT topology to what is being flagged as invalid, so either that vendor
> isn't using EDK2 or they have done something to avoid this check without
> submitting a patch to EDK2.
> 
> This check is only present in the DynamicTablesPkg, so it shouldn't be too
> restrictive.

Ah, correct. If they're not using DynamicTablesPkg to generate the PPTT/SSDT, then they wouldn't hit this.

> If the platform is known to use it, is it possible to share which platform it is ?

We see the topology in question (ie. a root node is a parent node to physical package nodes) in Ampere's two-socket Altra PPTT.


-=-=-=-=-=-=-=-=-=-=-=-
Groups.io Links: You receive all messages sent to this group.
View/Reply Online (#113485): https://edk2.groups.io/g/devel/message/113485
Mute This Topic: https://groups.io/mt/103603398/7686176
Group Owner: devel+owner@edk2.groups.io
Unsubscribe: https://edk2.groups.io/g/devel/unsub [rebecca@openfw.io]
-=-=-=-=-=-=-=-=-=-=-=-



  reply	other threads:[~2024-01-09 16:55 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-08 18:12 [edk2-devel] [PATCH] DynamicTablesPkg/SSDT: Remove incorrect root node check Jeshua Smith via groups.io
2024-01-09  8:22 ` PierreGondois
2024-01-09 15:47   ` Jeshua Smith via groups.io
2024-01-09 16:15     ` PierreGondois
2024-01-09 16:55       ` Jeshua Smith via groups.io [this message]
2024-01-15 11:41         ` PierreGondois

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=DM6PR12MB3371B05774C6FA9F02E673FDDB6A2@DM6PR12MB3371.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