Just out of curiousity, how does the SVM nested implementation deal
with the potential time-of-check to time-of-use bugs that were fixed
on the VMX side with commit 4f2777bc9797 ("kvm: x86: nVMX: maintain
internal copy of current VMCS")?
Just out of curiousity, how does the SVM nested implementation deal
with the potential time-of-check to time-of-use bugs that were fixed
on the VMX side with commit 4f2777bc9797 ("kvm: x86: nVMX: maintain
internal copy of current VMCS")?
|