-
Notifications
You must be signed in to change notification settings - Fork 133
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
Allow mutation of the GDT #322
Comments
First of all thank you for raising that issue, we were previously not aware of the side effects caused by loading a TSS and the processor changing the GDT entries. The old implementation didn't allow any mutation, not by the processor nor by a user, so given that the processor was mutating it, it was technically unsound. Following the discussion in #323 (comment), we decided that we will no longer support sharing a GDT in the next breaking release. |
Hopefully, this help address confusion like that seen in: #322 Signed-off-by: Joe Richey <[email protected]>
Hopefully, this help address confusion like that seen in: #322 Signed-off-by: Joe Richey <[email protected]>
I've been experiencing with SMP and was trying to reuse the same GDT for all cores since my segments are always the same, but I found a problem, the processor was setting the
ACCESS
bit in the TSS lower half segment and causing general protection faults when trying to load the TSS segment selector in another processor.It would be great if there was a way to mutate the GDT in a way that allowed to unset this bit.
The text was updated successfully, but these errors were encountered: