-
Notifications
You must be signed in to change notification settings - Fork 25
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
System Calls #8
Comments
I'd like to work on this one. |
@dwdenton - are you still planning on taking this on? |
Yeah. Only have read a bit into it, so nothing started if you're also interested. |
I'm interested too. |
Apparently this issue is part of a milestone that's due soon, so I'm just looking into what I can help out on. |
Ah. I don't normally check Github often, so I didn't notice that. Just created system_calls branch to work on. |
Could we maybe meet at the GDC sometime this weekend to work on this? |
Definitely. I have Saturday free before noon and from around 3 to 6. Sunday I get off work at 1 and am free until 6:30. |
I'm free anytime. Jeffrey? |
So do you want to just meet in the GDC lab tomorrow at like 1:30 then? |
Works for me. |
Hey guys, sorry; I was at a wedding this weekend and wasn't checking github. I'm free to meet today at 1:30 in the lab. |
I got system calls running and added a branch statement to hw_handlers.c |
Nice! That will come in handy for those who were wondering how to work with interrupts. |
We need the two "endpoints" for system call support: An entry.s like kernel-side system call handler and the corresponding syscall function in user space.
The text was updated successfully, but these errors were encountered: