-
Notifications
You must be signed in to change notification settings - Fork 36
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
Syscall support: miscellaneous #6
Comments
How to decide to which groups each syscall belongs? |
The manpages ( |
I was going to add these as well:
With them, I cannot build:
Have you ever seen anything similar? |
Not exactly, but some things that it could be:
|
You're right. If you know of a way to build for x86, I'd go with it; otherwise I will go for a new VM and use that instead |
Hmm, it's possible that KRF doesn't build at all with x86_32 -- it definitely makes assumptions about running on x86 in general, and I've only ever tested and used it on x86_64. I'd say it's okay to table x86_32-specific syscalls for now and focus on other ones; I'll create an issue to track general 32-bit support. |
To be more explicit here: we should prioritize syscalls of interest like those in gVisor: |
We should support faulting these syscalls.
vhangup
sysctl
prctl
arch_prctl
adjtime
adjtimex
pivot_root
iopl
nfsservctl
readahead
That list is not exhaustive; there are definitely others.
Each of the above probably belongs to one or more groups.
The text was updated successfully, but these errors were encountered: