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

[2405] Revert "ArmPkg: ArmPsciMpServicesDxe: Fix CPU resource leakage" #256

Merged
merged 1 commit into from
Jul 23, 2024

Conversation

kuqin12
Copy link
Contributor

@kuqin12 kuqin12 commented Jul 22, 2024

Description

This reverts commit 05caf20. As the change was integrated into EDK2 in a different way which will cover the expected CPU state to fix the state machine.

  • 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

This change was tested on QEMU SBSA and verified MP test works as expected.

Integration Instructions

N/A

@kuqin12 kuqin12 requested review from cfernald, os-d and apop5 July 22, 2024 19:00
@kuqin12 kuqin12 enabled auto-merge (rebase) July 23, 2024 19:21
@kuqin12 kuqin12 disabled auto-merge July 23, 2024 19:21
@kuqin12 kuqin12 enabled auto-merge (squash) July 23, 2024 19:21
@kuqin12 kuqin12 disabled auto-merge July 23, 2024 19:21
@kuqin12 kuqin12 changed the title Revert "ArmPkg: ArmPsciMpServicesDxe: Fix CPU resource leakage" [2405] Revert "ArmPkg: ArmPsciMpServicesDxe: Fix CPU resource leakage" Jul 23, 2024
@kuqin12 kuqin12 enabled auto-merge (squash) July 23, 2024 19:21
@kuqin12 kuqin12 merged commit bb6ba6f into microsoft:release/202405 Jul 23, 2024
15 checks passed
@kuqin12 kuqin12 deleted the revert_cpu branch July 23, 2024 21:20
apop5 pushed a commit to apop5/mu_silicon_arm_tiano that referenced this pull request Jan 17, 2025
microsoft#256)

# Preface

Please ensure you have read the [contribution
docs](https://github.com/microsoft/mu/blob/master/CONTRIBUTING.md) prior
to submitting the pull request. In particular,
[pull request
guidelines](https://github.com/microsoft/mu/blob/master/CONTRIBUTING.md#pull-request-best-practices).

## Description

This reverts commit 05caf20. As the
change was integrated into EDK2 in a different way which will cover the
expected CPU state to fix the state machine.

For each item, place an "x" in between `[` and `]` if true. Example:
`[x]`.
_(you can also check items in the GitHub UI)_

- [x] 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

This change was tested on QEMU SBSA and verified MP test works as
expected.

## Integration Instructions

N/A
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.

3 participants