From: Laszlo Ersek <lersek@redhat.com>
To: Eduardo Habkost <ehabkost@redhat.com>,
"Michael S. Tsirkin" <mst@redhat.com>
Cc: qemu-devel@nongnu.org, "Gerd Hoffmann" <kraxel@redhat.com>,
"Paolo Bonzini" <pbonzini@redhat.com>,
"Igor Mammedov" <imammedo@redhat.com>,
"Philippe Mathieu-Daudé" <philmd@redhat.com>,
"Richard Henderson" <rth@twiddle.net>
Subject: Re: [RFC 3/3] acpi: cpuhp: add CPHP_GET_CPU_ID_CMD command
Date: Fri, 11 Oct 2019 10:07:03 +0200 [thread overview]
Message-ID: <91fa8359-d3f7-a28e-f8ce-e08637dea429@redhat.com> (raw)
In-Reply-To: <20191010192649.GF4084@habkost.net>
On 10/10/19 21:26, Eduardo Habkost wrote:
> Topology info is already available on CPUID.
Independently of everything else, thanks for pointing this out.
The edk2 library called "LocalApicLib" has two relevant functions:
> /**
> Get Package ID/Core ID/Thread ID of a processor.
>
> The algorithm assumes the target system has symmetry across physical
> package boundaries with respect to the number of logical processors
> per package, number of cores per package.
>
> @param[in] InitialApicId Initial APIC ID of the target logical processor.
> @param[out] Package Returns the processor package ID.
> @param[out] Core Returns the processor core ID.
> @param[out] Thread Returns the processor thread ID.
> **/
> VOID
> EFIAPI
> GetProcessorLocationByApicId (
> IN UINT32 InitialApicId,
> OUT UINT32 *Package OPTIONAL,
> OUT UINT32 *Core OPTIONAL,
> OUT UINT32 *Thread OPTIONAL
> );
>
> /**
> Get Package ID/Module ID/Tile ID/Die ID/Core ID/Thread ID of a processor.
>
> The algorithm assumes the target system has symmetry across physical
> package boundaries with respect to the number of threads per core, number of
> cores per module, number of modules per tile, number of tiles per die, number
> of dies per package.
>
> @param[in] InitialApicId Initial APIC ID of the target logical processor.
> @param[out] Package Returns the processor package ID.
> @param[out] Die Returns the processor die ID.
> @param[out] Tile Returns the processor tile ID.
> @param[out] Module Returns the processor module ID.
> @param[out] Core Returns the processor core ID.
> @param[out] Thread Returns the processor thread ID.
> **/
> VOID
> EFIAPI
> GetProcessorLocation2ByApicId (
> IN UINT32 InitialApicId,
> OUT UINT32 *Package OPTIONAL,
> OUT UINT32 *Die OPTIONAL,
> OUT UINT32 *Tile OPTIONAL,
> OUT UINT32 *Module OPTIONAL,
> OUT UINT32 *Core OPTIONAL,
> OUT UINT32 *Thread OPTIONAL
> );
They are implemented with heavy CPUID usage.
So... just give me the APIC-ID. That's the primary key in edk2 for identifying
x86 processors.
Thanks
Laszlo
next prev parent reply other threads:[~2019-10-11 8:08 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-09 13:22 [RFC 0/3] acpi: cphp: add CPHP_GET_CPU_ID_CMD command to cpu hotplug MMIO interface Igor Mammedov
2019-10-09 13:22 ` [RFC 1/3] acpi: cpuhp: fix 'Command data' description is spec Igor Mammedov
2019-10-10 12:33 ` Laszlo Ersek
2019-10-17 15:41 ` Igor Mammedov
2019-10-18 13:24 ` Laszlo Ersek
2019-10-10 13:31 ` Laszlo Ersek
2019-10-10 13:36 ` Laszlo Ersek
2019-10-22 17:17 ` Christophe de Dinechin
2019-10-22 17:37 ` Laszlo Ersek
2019-10-09 13:22 ` [RFC 2/3] acpi: cpuhp: add typical usecases into spec Igor Mammedov
2019-10-10 13:04 ` Laszlo Ersek
2019-10-10 13:15 ` Laszlo Ersek
2019-10-10 14:13 ` Laszlo Ersek
2019-10-18 14:45 ` Igor Mammedov
2019-10-09 13:22 ` [RFC 3/3] acpi: cpuhp: add CPHP_GET_CPU_ID_CMD command Igor Mammedov
2019-10-10 14:56 ` Laszlo Ersek
2019-10-10 15:06 ` Michael S. Tsirkin
2019-10-10 17:23 ` Igor Mammedov
2019-10-10 17:53 ` Laszlo Ersek
2019-10-10 19:26 ` Eduardo Habkost
2019-10-11 8:07 ` Laszlo Ersek [this message]
2019-10-18 16:18 ` Igor Mammedov
2019-10-21 13:06 ` Laszlo Ersek
2019-10-22 12:39 ` Laszlo Ersek
2019-10-22 14:42 ` Igor Mammedov
2019-10-22 15:49 ` Laszlo Ersek
2019-10-23 14:59 ` Igor Mammedov
2019-10-24 15:07 ` Philippe Mathieu-Daudé
2019-10-10 9:56 ` [RFC 0/3] acpi: cphp: add CPHP_GET_CPU_ID_CMD command to cpu hotplug MMIO interface Michael S. Tsirkin
2019-10-10 13:39 ` Igor Mammedov
2019-10-10 13:59 ` Michael S. Tsirkin
2019-10-10 15:57 ` Igor Mammedov
2019-10-10 18:15 ` Michael S. Tsirkin
2019-10-11 7:41 ` Laszlo Ersek
2019-10-10 19:20 ` Eduardo Habkost
2019-10-11 8:01 ` Laszlo Ersek
2019-10-11 13:00 ` Michael S. Tsirkin
2019-10-11 16:13 ` Laszlo Ersek
2019-10-11 10:47 ` Igor Mammedov
2019-10-11 6:54 ` Laszlo Ersek
2019-10-10 14:16 ` Eduardo Habkost
2019-10-10 14:49 ` Michael S. Tsirkin
2019-10-10 17:09 ` Igor Mammedov
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=91fa8359-d3f7-a28e-f8ce-e08637dea429@redhat.com \
--to=lersek@redhat.com \
--cc=ehabkost@redhat.com \
--cc=imammedo@redhat.com \
--cc=kraxel@redhat.com \
--cc=mst@redhat.com \
--cc=pbonzini@redhat.com \
--cc=philmd@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=rth@twiddle.net \
/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;
as well as URLs for NNTP newsgroup(s).