Skip to content

Fix caller-saved register explanation in p18-sched.md #270

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.

Sign up for GitHub

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

Closed
Rachit-Bhalani wants to merge 1 commit into from
Closed

Fix caller-saved register explanation in p18-sched.md #270

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions p18-sched.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -30,7 +30,7 @@ the compiler. If we search `swtch` in `kernel.asm`, we see the following code:

`eax` and `edx` registers are pushed on the stack. `eip` will be saved as the
return address by the `call` instruction itself. Interestingly, `ecx` is also a
caller-saved register, but since the callee of `swtch`, i.e, `scheduler`, did
caller-saved register, but since the caller of `swtch`, i.e, `scheduler`, did
not modify `ecx`, the compiler chose to not save it. Caller of `scheduler` would
have already saved it.

Expand Down Expand Up @@ -81,4 +81,4 @@ sometimes process 2 is running:
2 runble initcode
1 runble initcode
2 run initcode
```
```
Loading