public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: "Laszlo Ersek" <lersek@redhat.com>
To: devel@edk2.groups.io, tigerliu@zhaoxin.com
Subject: Re: [edk2-devel] MP Services Protocol : Support Hyper threading or not
Date: Mon, 22 Feb 2021 11:39:47 +0100	[thread overview]
Message-ID: <581d5952-32b2-56e3-30d5-7f7f24039fa0@redhat.com> (raw)
In-Reply-To: <03f9e675800143189bc59fab08865256@zhaoxin.com>

On 02/22/21 08:08, Tiger Liu(BJ-RD) wrote:
> Dear All:
> I have a question about MP Services Protocol.
> Does it support Hyper-threading technology?
> 
> For example:
> A Quad-cores CPU(with HT feature support), actually it is equal to 8 logical cores.
> Take assumption 8 logical cores are all healthy and being enabled.
> 
> So:
> 
> 1.      Will EFI_MP_SERVICES_PROTOCOL.GetNumberOfProcessors()return total 8 logical processor cores?
> 
> 2.      Will EFI_MP_SERVICES_PROTOCOL.StartupAllAPs() make all 8 logical cores do some tasks simultaneously?

My understanding is "yes", to both questions. Most of the MP stuff deals
with "logical processors".


BTW, if you check the EFI_MP_SERVICES_GET_PROCESSOR_INFO prototype, it
outputs EFI_PROCESSOR_INFORMATION. The latter has the following fields:

  EFI_CPU_PHYSICAL_LOCATION      Location;
  EXTENDED_PROCESSOR_INFORMATION ExtendedInformation;

The former gives you a package/core/thread identification for a
particular processor number. The latter (optionally) provides a 6-level
description (package / module / tile / die / core / thread). In each
information structure, "logical thread" is the finest granularity
information.

hth
Laszlo


  reply	other threads:[~2021-02-22 10:39 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-22  7:08 [edk2-devel] MP Services Protocol : Support Hyper threading or not Tiger Liu(BJ-RD)
2021-02-22 10:39 ` Laszlo Ersek [this message]
2021-02-23  1:17   ` fanjianfeng
2021-02-23 17:29     ` Laszlo Ersek
  -- strict thread matches above, loose matches on Subject: below --
2021-02-23  4:49 Tiger Liu(BJ-RD)

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=581d5952-32b2-56e3-30d5-7f7f24039fa0@redhat.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