-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
V7a mon #14371
base: master
Are you sure you want to change the base?
V7a mon #14371
Conversation
VELAPLATFO-7449 1. add the secure monitor runtime 2. implement ap switch to tee and back with smc/fiq Signed-off-by: guoshichao <[email protected]> Change-Id: Iaaf25f4670ce2b87adb1a23390554565e94920fa
VELAPLATFO-7449 the qemu_idle implement up_idle() method, inside the up_idle() method will invoke sm_switch_nsec() function to implement boot the ap core from tee core Signed-off-by: guoshichao <[email protected]> Change-Id: I43d4be20265b1d89dca7e2613ad523979b7371c6
This PR exceeds the recommended size of 1000 lines. Please make sure you are NOT addressing multiple issues with one PR. Note this PR might be rejected due to its size. |
@@ -220,3 +220,9 @@ config ARMV7A_ICACHE_DISABLE | |||
config ARMV7A_AFE_ENABLE | |||
bool "Enable Access Flag at __start" | |||
default n | |||
|
|||
config ARMV7A_MONITOR_STACK_SIZE | |||
int "monitor stack size" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
int "Monitor stack size"
VELAPLATFO-7449 Change-Id: Id38ebd39f6c31ba15ba53e1f1964b9eac5eac00d Signed-off-by: genglong <[email protected]>
This PR exceeds the recommended size of 1000 lines. Please make sure you are NOT addressing multiple issues with one PR. Note this PR might be rejected due to its size. |
Note: Please adhere to Contributing Guidelines.
Summary
Update this section with information on why change is necessary,
what it exactly does and how, if new feature shows up, provide
references (dependencies, similar problems and solutions), etc.
Impact
Update this section, where applicable, on how change affects users,
build process, hardware, documentation, security, compatibility, etc.
Testing
Update this section with details on how did you verify the change,
what Host was used for build (OS, CPU, compiler, ..), what Target was
used for verification (arch, board:config, ..), etc. Providing build
and runtime logs from before and after change is highly appreciated.