On 04.02.2021 15:10, Andrew Cooper wrote:
> On 29/01/2021 11:45, Jan Beulich wrote:
>> + {
>> + u32 general1_intercepts = vmcb_get_general1_intercepts(vmcb);
>> +
>> + if ( v->arch.hvm.guest_cr[4] & X86_CR4_UMIP )
>> + {
>> + value &= ~X86_CR4_UMIP;
>> + ASSERT(vmcb_get_cr_intercepts(vmcb) &
>> CR_INTERCEPT_CR0_READ);
>
> It occurs to me that adding CR0 read exiting adds a lot of complexity
> for very little gain.
Actually, upon second look - why do you say "adding CR0 read
exiting"? This is only an assertion. No other changes are
being made to CR0 interception (apart from the few lines in
the handling of the respective #VMEXIT).
Jan
