-
Notifications
You must be signed in to change notification settings - Fork 19
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
Initial monitor state management overhaul #196
Conversation
16ffd0f
to
f0f898d
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good, just a minor clarification.
@@ -0,0 +1,3 @@ | |||
use twizzler_runtime_api::ObjID; | |||
|
|||
pub const MONITOR_INSTANCE_ID: ObjID = ObjID::new(0); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is this a placeholder? Please document.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Will document!
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Do it!
This PR implements the scaffolding for the rest of the implementation of the security monitor, organizing the state management, initial support for mapping and unmapping objects in the space, and managing threads. Most of this is stubbed and not hooked up yet. Next PR will implement more functionality.