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

[Cherry-Pick][Rebase & FF] UefiCpuPkg: Consume PcdCpuSmmApSyncTimeout2. #1097

Conversation

apop5
Copy link
Contributor

@apop5 apop5 commented Aug 7, 2024

Description

In addition to what was said in the Cherry-Pick in #1096.

It looks like Edk2 picked up these changes, reverted them, and then added them back because Ovmf packages had already started consuming them.

The changes should not impact existing platforms, because the changes only modify PiSmmCpuDxeSmm.

  • Impacts functionality?
    • Functionality - Does the change ultimately impact how firmware functions?
    • Examples: Add a new library, publish a new PPI, update an algorithm, ...
  • Impacts security?
    • Security - Does the change have a direct security impact on an application,
      flow, or firmware?
    • Examples: Crypto algorithm change, buffer overflow fix, parameter
      validation improvement, ...
  • Breaking change?
    • Breaking change - Will anyone consuming this change experience a break
      in build or boot behavior?
    • Examples: Add a new library class, move a module to a different repo, call
      a function in a new library class in a pre-existing module, ...
  • Includes tests?
    • Tests - Does the change include any explicit test code?
    • Examples: Unit tests, integration tests, robot tests, ...
  • Includes documentation?
    • Documentation - Does the change contain explicit documentation additions
      outside direct code modifications (and comments)?
    • Examples: Update readme file, add feature readme file, link to documentation
      on an a separate Web page, ...

How This Was Tested

Local CI.

Integration Instructions

N/A

@apop5 apop5 changed the title [Cherry-Pick] [Cherry-Pick] UefiCpuPkg: Consume PcdCpuSmmApSyncTimeout2. Aug 7, 2024
@apop5 apop5 requested review from os-d and kuqin12 August 7, 2024 23:49
@makubacki makubacki changed the title [Cherry-Pick] UefiCpuPkg: Consume PcdCpuSmmApSyncTimeout2. [Cherry-Pick]{Rebase & FF] UefiCpuPkg: Consume PcdCpuSmmApSyncTimeout2. Aug 8, 2024
@makubacki makubacki changed the title [Cherry-Pick]{Rebase & FF] UefiCpuPkg: Consume PcdCpuSmmApSyncTimeout2. [Cherry-Pick][Rebase & FF] UefiCpuPkg: Consume PcdCpuSmmApSyncTimeout2. Aug 8, 2024
jiaxinwu and others added 2 commits August 8, 2024 19:27
PcdCpuSmmApSyncTimeout is not only used by BSP to wait AP,
but also for AP to wait BSP (APHandler).

This patch is only to refine the PCD comment. No function
impact.

Signed-off-by: Jiaxin Wu <[email protected]>
Cc: Ray Ni <[email protected]>
Cc: Rahul Kumar <[email protected]>
Cc: Gerd Hoffmann <[email protected]>
This patch is to consume the PcdCpuSmmApSyncTimeout2 to
enhance the flexibility of timeout configuration.
In some cases, certain processors may not be able to enter
SMI, and prolonged waiting could lead to kernel soft/hard
lockup. We have now defined two timeouts. The first timeout
can be set to a smaller value to reduce the waiting period.
Processors that are unable to enter SMI will be woken up
through SMIIPL to enter SMI, followed by a second waiting
period. The second timeout can be set to a larger value to
prevent delays in processors entering SMI case due to the
long instruction execution.

This patch adjust the location of PcdCpuSmmApSyncTimeout2
to avoid conflict.

Signed-off-by: Yanbo Huang <[email protected]>
Cc: Ray Ni <[email protected]>
Cc: Rahul Kumar <[email protected]>
Cc: Gerd Hoffmann <[email protected]>
@apop5 apop5 force-pushed the personal/apop5/cherrypickapsynctimeoutpcd branch from a2516a0 to 6e45201 Compare August 9, 2024 02:28
@apop5 apop5 merged commit cf2acf1 into microsoft:release/202311 Aug 9, 2024
31 checks passed
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.

5 participants