Fix kernel stack pointer save on LoongArch64 (again) #14
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
The fix proposed previously at 7152ea5 is wrong.
next_ctx.sp
, which is saved in the previouscontext_switch
, is never the top of kernel stack.This PR fixs this by porting oscomp/arceos#18.
Comparison
As said in arceos-org/arceos#229, the previous fix tried to take a similar approach to x86_64. But x86_64's
TaskContext
has a fixedkstack_top
field, so this is correct.I believe there is no need to reduce the times to save kernel sp on LoongArch64 since on x86_64 each save and load involves a memory operation but here we just read and write registers, which is the same way
sscratch
is used on RISC-V.