Skip to content
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

[libc/libos] code seperation #296

Open
3 of 5 tasks
Meulengracht opened this issue Oct 7, 2022 · 0 comments
Open
3 of 5 tasks

[libc/libos] code seperation #296

Meulengracht opened this issue Oct 7, 2022 · 0 comments

Comments

@Meulengracht
Copy link
Owner

Meulengracht commented Oct 7, 2022

We are currently in the progress of splitting up most of the service/syscall-api code into libos, and then keep libc clean in the sense that it should only interact with code from libos, instead of acting directly with system calls and system services.

This means we would like to end the most of the interactions that libc has with gracht+system calls.

Things that remain:

  • All file related functions currently invoke the system service protocol directly.
  • All socket related functions currently invoke the system service protocol directly.
  • events.h needs a corresponding implementation in libos with type header and normal header
  • signal.c uses both system call and process service directly
  • exit.c uses the thread system call directly
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant