> Ok, I can add the read-back check before setting the feature flag(s). > > But... what about the case where the guest is a different family than > hypervisor? If we're on, say, a Fam15h hypervisor but the guest is started > as a Fam0fh guest where the MSR doesn't exist and LFENCE is supposed to be > serialized? I'll have to do a rdmsr_safe() and only set the flag(s) if I > can successfully read the MSR back and validate the bit.
At some point, if the hypervisor is lying to you about what the CPU is, and you can't check empirically, you have to admit defeat :) -- dwmw2
