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

Signals #11

Open
edwardwawrzynek opened this issue Oct 21, 2019 · 1 comment
Open

Signals #11

edwardwawrzynek opened this issue Oct 21, 2019 · 1 comment
Labels
enhancement New feature or request

Comments

@edwardwawrzynek
Copy link
Owner

We need some kind of signal mechanism, or at least some way to do Ctrl+c and kill.

@edwardwawrzynek edwardwawrzynek added the enhancement New feature or request label Oct 21, 2019
@edwardwawrzynek
Copy link
Owner Author

Probably a second context + stack page is needed, and we need processes handling signals to be able to do syscalls.

Additionally, a signal queue should be implemented so that signals can be buffered. If a signal handler triggers a hardware exception, we can probably just immediately call the handler for that exception, otherwise queue it.

Signal handling should probably just be a part of regularly schedule process execution, and just set up the special signal stack frame so that returning from a signal handler calls a special syscall that ends signal handling.

Signal handlers should not be able to cause the whole system to hang or get screwed up.

Stack page allocation needs to be moved from memory context into execution context records, or at least kept somewhere in execution context records in the process table.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant