-
Notifications
You must be signed in to change notification settings - Fork 136
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
Descriptor::tss_segment
too restrictive?
#423
Comments
The way I see it, there are two ways to solve this:
Option 2 will likely require breaking changes, so I tend towards option 1 for now (though we were planning on releasing a new breaking version anyways, so option 2 should also be good). |
I think it makes sense to implement both option 1 and option 2. There will always be cases where our safe abstractions are not a good fit, so we should allow users to plug in their own abstractions if desired. So starting with option 1 sounds good to me! @SamZhang3 If you have time, it would be great if you could create a PR to add an unsafe |
I'm trying to implement multitasking in user mode with the following setup:
But with this crate, there is a problem. To add the TSS, the
Descriptor::tss_segment
function should be called with theTaskStateSegment
structure, to create aDescriptor
that can be added to the GDT. But the function expects a&'static
reference to theTaskStateSegment
, which means that, once called, no further modifications are possible to the TSS (the&'static
reference cannot coexist with any mutable references), so it is not possible to update the TSS on context switching.Would it be a good idea to loosen the requirements for calling this function?
The text was updated successfully, but these errors were encountered: