From: "Pedro Falcato" <pedro.falcato@gmail.com>
To: devel@edk2.groups.io, JackX.Lin@intel.com
Cc: Chasel Chiu <chasel.chiu@intel.com>,
Nate DeSimone <nathaniel.l.desimone@intel.com>,
Isaac Oram <isaac.w.oram@intel.com>,
Liming Gao <gaoliming@byosoft.com.cn>,
Eric Dong <eric.dong@intel.com>,
Donald Kuo <Donald.Kuo@intel.com>,
Chandana C Kumar <chandana.c.kumar@intel.com>
Subject: Re: [edk2-devel] [edk2-platforms: PATCH] BIOS needs to present cores in order of relative performance in MADT
Date: Thu, 17 Nov 2022 14:09:27 +0000 [thread overview]
Message-ID: <CAKbZUD2Qebad9TAfxZm9EhJh+y5kDGeovwnjLaRV6hKs0z2yRQ@mail.gmail.com> (raw)
In-Reply-To: <20221117060123.209-1-jackx.lin@intel.com>
[-- Attachment #1: Type: text/plain, Size: 443 bytes --]
On Thu, Nov 17, 2022 at 6:01 AM JackX Lin <JackX.Lin@intel.com> wrote:
> BIOS should keep MADT ordering by big core first then small core
>
Hi Jack,
Can you please elaborate why this is required? AFAIK nowhere in the ACPI
spec does it say you need to order by big-little cores.
Is this some sort of regression for a specific OS? A useful commit message
and/or some comments would be really useful here for posterity.
Thanks,
Pedro Falcato
[-- Attachment #2: Type: text/html, Size: 866 bytes --]
next prev parent reply other threads:[~2022-11-17 14:09 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-17 6:01 [edk2-platforms: PATCH] BIOS needs to present cores in order of relative performance in MADT JackX Lin
2022-11-17 6:06 ` [edk2-devel] " Michael D Kinney
2022-11-17 14:09 ` Pedro Falcato [this message]
2022-11-18 8:34 ` JackX Lin
2022-11-18 19:11 ` Pedro Falcato
2022-11-22 3:35 ` Ni, Ray
-- strict thread matches above, loose matches on Subject: below --
2022-11-16 6:29 JackX Lin
2022-11-17 3:45 ` [edk2-devel] " Michael D Kinney
2022-11-17 3:54 ` JackX Lin
2022-11-16 2:52 JackX Lin
2022-11-16 3:50 ` [edk2-devel] " Michael D Kinney
2022-11-16 3:59 ` JackX Lin
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=CAKbZUD2Qebad9TAfxZm9EhJh+y5kDGeovwnjLaRV6hKs0z2yRQ@mail.gmail.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