On 01/02/20 19:52, Sean Christopherson wrote: > Although it's _extremely_ tempting to yank KVM's stateful code, leave it > in for now but annotate all its code paths as "unlikely". The code is > relatively contained, and if by some miracle there is someone running KVM > on a CPU with a stateful CPUID 0x2, more power to 'em. I suppose the only way that could happen is with nested virtualization. I would just drop it. Paolo
