manual: don't list out all MSRs and VMCS fields#515
Conversation
dreamliner787-9
changed the title
midnightveil
left a comment
midnightveil
left a comment
There was a problem hiding this comment.
IDK why we need a long list of everything supported tbh.
|
Actually, yeah. I think I changed my mind. I'm guessing there's an x86 reference for these registers? I don't think we should list all of them here, it's unwieldy. |
|
You could consult the Intel SDM, but the kernel doesn't allow you to read/write to all of the fields. So I thought it would be best if we list out which fields the user can touch. |
|
I think we should do something along the lines of "seL4 only allows certain MSRs to be written by userspace; for a full list of supported ones, see ". |
dreamliner787-9
force-pushed
the
manual_update
branch
from
ce9ccfe to
4b696e6
Compare
dreamliner787-9
changed the title
midnightveil
left a comment
midnightveil
left a comment
There was a problem hiding this comment.
It might be worth making it so that seL4 documents this somewhere outside of the source, so that we don't have to link there, but this is good enough for now.
The previous approach is too unwieldy and required constant updates. We should just link the user to the kernel instead and have one source of truth. Signed-off-by: Bill Nguyen <bill.nguyen@unsw.edu.au>
dreamliner787-9
force-pushed
the
manual_update
branch
from
4b696e6 to
2ae4366
Compare
2 participants
The kernel now permits userspace to readIA32_VMX_MISC_MSRMSR to operate the VMX preemption timer in commit 7441046. This commit updates the manual to reflect that. Since the seL4 version in Microkit had been recently bumped which included that commit.The previous approach is too unwieldy and required constant updates.
We should just link the user to the kernel instead and have one
source of truth.