-
Notifications
You must be signed in to change notification settings - Fork 118
snp guest vsm: register intercepts #1142
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
base: main
Are you sure you want to change the base?
Conversation
85ab7fa
to
af56d64
Compare
0eead15
to
2c05abc
Compare
9c2582d
to
fa71c45
Compare
// The APIC is software-enabled after reset for | ||
// secure VTLs, to maintain compatibility with released versions of secure | ||
// kernel | ||
let mut lapic = apic_set.add_apic(vp_info, vtl == Vtl::Vtl1); |
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.
@jstarks any concerns with this part of the change? Our other components also do this; without it, if I remember correctly, I couldn't get the intercept delivered to VTL 1.
hvdef::HV_SYNIC_INTERCEPTION_SINT_INDEX, | ||
&crate::processor::InterceptMessageType::Register { reg, value } | ||
.generate_hv_message(self.vp_index(), vtl, message_state), | ||
); |
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.
@jstarks also wanted to confirm with you that this post_message approach is correct for sending intercepts to VTL 1.
Support for VTL 1 to register for write intercepts on certain registers.
Tested: