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

elfloader/riscv: always pass hart/core information #194

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

axel-h
Copy link
Member

@axel-h axel-h commented Mar 14, 2024

Align the SMP and non-SMP ABI for kernel entry and pass on the hard ID obtained from the previous bootloader unconditionally. This allows the kernel to use the ID, e.g. when setting up the PLIC, so there is no need to require defining a platform specific hard-codes value. Furthermore, this change allows running a single core kernel in SMP configuration also.

The long term goal if this change is removing the need to have the explicit CONFIG_FIRST_HART_ID in the seL4 kernel. It will just use the ID that is passed (unless platforms configure something else due to special needs). That aligns the behavior a bit to ARM, where we can read the current core ID from a register in case it is needed somewhere, so there is no need to configure this explicitly. Unfortunately, RISC-V does not have such a register here.

@axel-h
Copy link
Member Author

axel-h commented May 13, 2024

Is there a chance to get this merged?

Align the SMP and non-SMP ABI for kernel entry and pass on the hard ID
obtained from the previous bootloader unconditionally. This allows the
kernel to use the ID, e.g. when setting up the PLIC, so there is no
need to require defining a platform specific hard-coded value.
Furthermore, this change allows running a single core kernel in SMP
configuration also.

Signed-off-by: Axel Heider <axel.heider@codasip.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.

None yet

1 participant