Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

CorebootPayloadPkg: disable StatusCodeSerial for release build #3

Merged
merged 1 commit into from
Jul 2, 2019

Conversation

piotr-kleins
Copy link

Signed-off-by: Piotr Kleinschmidt piotr.kleins@gmail.com

Signed-off-by: Piotr Kleinschmidt <piotr.kleins@gmail.com>
@miczyg1 miczyg1 self-assigned this Jul 2, 2019
@miczyg1 miczyg1 self-requested a review July 2, 2019 10:11
@miczyg1 miczyg1 merged commit 573e677 into coreboot-4.7.x-uefi Jul 2, 2019
@miczyg1 miczyg1 deleted the dis_progress_output branch July 2, 2019 10:12
pietrushnic pushed a commit that referenced this pull request Apr 13, 2020
REF: https://bugzilla.tianocore.org/show_bug.cgi?id=1584

The flow of CPU feature initialization logic is:
1. BSP calls GetConfigDataFunc() for each thread/AP;
2. Each thread/AP calls SupportFunc() to detect its own capability;
3. BSP calls InitializeFunc() for each thread/AP.

There is a design gap in step #3. For a package scope feature that only
requires one thread of each package does the initialization operation,
what InitializeFunc() currently does is to do the initialization
operation only CPU physical location Core# is 0.
But in certain platform, Core#0 might be disabled in hardware level
which results the certain package scope feature isn't initialized at
all.

The patch adds a new field First to indicate the CPU's location in
its parent scope.
First.Package is set for all APs/threads under first package;
First.Core is set for all APs/threads under first core of each
package;
First.Thread is set for the AP/thread of each core.

Signed-off-by: Ray Ni <ray.ni@intel.com>
Reviewed-by: Eric Dong <eric.dong@intel.com>
Reviewed-by: Star Zeng <star.zeng@intel.com>
Cc: Michael D Kinney <michael.d.kinney@intel.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants