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

SBSA multi-processor not fully functional #153

Open
kuqin12 opened this issue Nov 18, 2022 · 3 comments
Open

SBSA multi-processor not fully functional #153

kuqin12 opened this issue Nov 18, 2022 · 3 comments
Assignees
Labels
platform:SBSA Specific to the SBSA platform state:backlog In the backlog type:bug Something isn't working

Comments

@kuqin12
Copy link
Contributor

kuqin12 commented Nov 18, 2022

QEMU will release all cores at launching. These cores will go through the BL1 boot process and then APs will enter a plat_secondary_cold_boot_setup function.

In the implementation of QEMU TFA, the APs will be left in the flash region where the BL1 code reside, waiting for events. In this case, MMIO write operations to the secure flash region from the BSP will wake up the APs. However, as the P30_CMD_READ_DEVICE_ID command is issued to the flash device, the flash will change mode to return device status registers. When APs wake up during these events, the code will no longer be accessible and results in AP panicking.

The idea is to bring these APs out of XIP state and host them in a memory-based code region. But there is a catch when the system reset. Resolution is still pending.

@kuqin12 kuqin12 added type:bug Something isn't working platform:SBSA Specific to the SBSA platform labels Nov 18, 2022
@github-actions
Copy link

This issue has been automatically marked as stale because it has not had activity in 45 days. It will be closed if no further activity occurs within 7 days. Thank you for your contributions.

@github-actions github-actions bot added state:stale Has not been updated in a long time and removed state:stale Has not been updated in a long time labels Jan 14, 2023
@github-actions
Copy link

github-actions bot commented Mar 5, 2023

This issue has been automatically marked as stale because it has not had activity in 45 days. It will be closed if no further activity occurs within 7 days. Thank you for your contributions.

@github-actions github-actions bot added the state:stale Has not been updated in a long time label Mar 5, 2023
@apop5 apop5 added state:backlog In the backlog and removed state:stale Has not been updated in a long time labels Mar 7, 2023
@makubacki
Copy link
Member

@kuqin12 - Check this

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
platform:SBSA Specific to the SBSA platform state:backlog In the backlog type:bug Something isn't working
Projects
None yet
Development

No branches or pull requests

3 participants