KVM: nSVM: Fixes for SVM_EXIT_CR0_SEL_WRITE injection
cover KVM: nSVM: Fixes for SVM_EXIT_CR0_SEL_WRITE injection
A couple of fixes for injecting SVM_EXIT_CR0_SEL_WRITE to L1 when emulating MOV-to-CR0 or LMSW. LMSW is handled by the emulator even in some cases where decode assists are enabled, so it's a more important fix. An example would be if L0 intercepts SVM_EXIT_WRITE_CR0 while L1 intercepts SVM_EXIT_CR0_SEL_WRITE.
Patch is an unrelated cleanup that can be dropped/merged separately.
Yosry Ahmed (3):
KVM: nSVM: Remove redundant cases in nested_svm_intercept()
KVM: nSVM: Propagate SVM_EXIT_CR0_SEL_WRITE correctly for LMSW
emulation
KVM: nSVM: Avoid incorrect injection of SVM_EXIT_CR0_SEL_WRITE
arch/x86/kvm/svm/nested.c | 10 ---------- arch/x86/kvm/svm/svm.c | 34 ++++++++++++++++++++++------------ 2 files changed, 22 insertions(+), 22 deletions(-)
Signature · 1 line
2.51.1.821.gb6fe4d2222-goog
PATCH 1/3 KVM: nSVM: Remove redundant cases in nested_svm_intercept()
Both the CRx and DRx cases are doing exactly what the default case is doing, remove them.
No functional change intended.
--- arch/x86/kvm/svm/nested.c | 10 ---------- 1 file changed, 10 deletions(-)
arch/x86/kvm/svm/nested.c +0 -10
@@ -1436,16 +1436,6 @@ static int nested_svm_intercept(struct vcpu_svm *svm)case SVM_EXIT_IOIO : vmexit =nested_svm_intercept_ioio (svm);break ; - case SVM_EXIT_READ_CR0 ... SVM_EXIT_WRITE_CR8: { -if (vmcb12_is_intercept (&svm->nested.ctl, exit_code)) - vmexit =NESTED_EXIT_DONE ; -break ; - } - case SVM_EXIT_READ_DR0 ... SVM_EXIT_WRITE_DR7: { -if (vmcb12_is_intercept (&svm->nested.ctl, exit_code)) - vmexit =NESTED_EXIT_DONE ; -break ; - } case SVM_EXIT_EXCP_BASE ... SVM_EXIT_EXCP_BASE + 0x1f: {/* * Host-intercepted exceptions have been checked already in
Signature · 1 line
2.51.1.821.gb6fe4d2222-goog
PATCH 2/3 KVM: nSVM: Propagate SVM_EXIT_CR0_SEL_WRITE correctly for LMSW emulation
In reply to Yosry AhmedWhen emulating L2 instructions, svm_check_intercept() checks whether a write to CR0 should trigger a synthesized #VMEXIT with SVM_EXIT_CR0_SEL_WRITE. For MOV-to-CR0, SVM_EXIT_CR0_SEL_WRITE is only triggered if any bit other than CR0.MP and CR0.TS is updated. However, according to the APM (24593—Rev. 3.42—March 2024, Table 15-7):
The LMSW instruction treats the selective CR0-write intercept as a non-selective intercept (i.e., it intercepts regardless of the value being written).
Skip checking the changed bits for x86_intercept_lmsw and always inject SVM_EXIT_CR0_SEL_WRITE.
--- arch/x86/kvm/svm/svm.c | 18 +++++++++--------- 1 file changed, 9 insertions(+), 9 deletions(-)
arch/x86/kvm/svm/svm.c +9 -9
@@ -4541,20 +4541,20 @@ static int svm_check_intercept(struct kvm_vcpu *vcpu, INTERCEPT_SELECTIVE_CR0)))break ; - cr0 = vcpu->arch.cr0 & ~SVM_CR0_SELECTIVE_MASK ; - val = info->src_val & ~SVM_CR0_SELECTIVE_MASK ; - +/* LMSW always triggers INTERCEPT_SELECTIVE_CR0 */ if (info->intercept == x86_intercept_lmsw) { - cr0 &=0xfUL ; - val &=0xfUL ; -/* lmsw can't clear PE - catch this here */ -if (cr0 &X86_CR0_PE ) - val |=X86_CR0_PE ; + icpt_info.exit_code =SVM_EXIT_CR0_SEL_WRITE ; +break ; } +/* +* MOV-to-CR0 only triggers INTERCEPT_SELECTIVE_CR0 if any bit +* other than SVM_CR0_SELECTIVE_MASK is changed. +*/ + cr0 = vcpu->arch.cr0 & ~SVM_CR0_SELECTIVE_MASK ; + val = info->src_val & ~SVM_CR0_SELECTIVE_MASK ;if (cr0 ^ val) icpt_info.exit_code =SVM_EXIT_CR0_SEL_WRITE ; -break ; }case SVM_EXIT_READ_DR0 :
Signature · 1 line
2.51.1.821.gb6fe4d2222-goog
Sean Christopherson
maintainerRe: [PATCH 2/3] KVM: nSVM: Propagate SVM_EXIT_CR0_SEL_WRITE correctly for LMSW emulation
Quoted 10 lines · Yosry Ahmed
When emulating L2 instructions,
svm_check_intercept()checks whether a write to CR0 should trigger a synthesized #VMEXIT withSVM_EXIT_CR0_SEL_WRITE. For MOV-to-CR0,SVM_EXIT_CR0_SEL_WRITEis only triggered if any bit other than CR0.MP and CR0.TS is updated. However, according to the APM (24593—Rev. 3.42—March 2024, Table 15-7):The LMSW instruction treats the selective CR0-write intercept as a non-selective intercept (i.e., it intercepts regardless of the value being written).
Quoted 5 lines
Skip checking the changed bits for
x86_intercept_lmswand always injectSVM_EXIT_CR0_SEL_WRITE.Fixes cfec82cb7d31 ("KVM: SVM: Add intercept check for emulated cr accesses")
Bad email (mostly in case you're using a macro for this; the next patch has the same typo).
Re: [PATCH 2/3] KVM: nSVM: Propagate SVM_EXIT_CR0_SEL_WRITE correctly for LMSW emulation
Quoted 11 lines · Sean Christopherson
Quoted 10 lines · Yosry Ahmed
When emulating L2 instructions,
svm_check_intercept()checks whether a write to CR0 should trigger a synthesized #VMEXIT withSVM_EXIT_CR0_SEL_WRITE. For MOV-to-CR0,SVM_EXIT_CR0_SEL_WRITEis only triggered if any bit other than CR0.MP and CR0.TS is updated. However, according to the APM (24593—Rev. 3.42—March 2024, Table 15-7):The LMSW instruction treats the selective CR0-write intercept as a non-selective intercept (i.e., it intercepts regardless of the value being written).
Quoted 8 lines
Quoted 5 lines
Skip checking the changed bits for
x86_intercept_lmswand always injectSVM_EXIT_CR0_SEL_WRITE.Fixes cfec82cb7d31 ("KVM: SVM: Add intercept check for emulated cr accesses")Bad email (mostly in case you're using a macro for this; the next patch has the same typo).
Yeah I realized after sending it. Will fixup if there's a new version.
PATCH 3/3 KVM: nSVM: Avoid incorrect injection of SVM_EXIT_CR0_SEL_WRITE
In reply to Yosry AhmedWhen emulating L2 instructions, svm_check_intercept() checks whether a write to CR0 should trigger a synthesized #VMEXIT with SVM_EXIT_CR0_SEL_WRITE. However, it does not check whether L1 enabled the intercept for SVM_EXIT_WRITE_CR0, which has higher priority according to the APM (24593—Rev. 3.42—March 2024, Table 15-7):
When both selective and non-selective CR0-write intercepts are active at the same time, the non-selective intercept takes priority. With respect to exceptions, the priority of this inter
Make sure L1 does NOT intercept SVM_EXIT_WRITE_CR0 before checking if SVM_EXIT_CR0_SEL_WRITE needs to be injected.
--- arch/x86/kvm/svm/svm.c | 16 +++++++++++++--- 1 file changed, 13 insertions(+), 3 deletions(-)
arch/x86/kvm/svm/svm.c +13 -3
@@ -4533,12 +4533,22 @@ static int svm_check_intercept(struct kvm_vcpu *vcpu,if (info->intercept == x86_intercept_cr_write) icpt_info.exit_code += info->modrm_reg; +/* +* If the write is indeed to CR0, check whether the exit_code +* needs to be converted to SVM_EXIT_CR0_SEL_WRITE. Intercepting +* SVM_EXIT_WRITE_CR0 has higher priority than +* SVM_EXIT_CR0_SEL_WRITE, so this is only relevant if L1 sets +* INTERCEPT_SELECTIVE_CR0 but not INTERCEPT_CR0_WRITE. +*/ if (icpt_info.exit_code !=SVM_EXIT_WRITE_CR0 || - info->intercept == x86_intercept_clts) +vmcb12_is_intercept (&svm->nested.ctl, +INTERCEPT_CR0_WRITE ) || + !(vmcb12_is_intercept (&svm->nested.ctl, +INTERCEPT_SELECTIVE_CR0 )))break ; -if (!(vmcb12_is_intercept (&svm->nested.ctl, -INTERCEPT_SELECTIVE_CR0 ))) +/* CLTS never triggers INTERCEPT_SELECTIVE_CR0 */ +if (info->intercept == x86_intercept_clts)break ;/* LMSW always triggers INTERCEPT_SELECTIVE_CR0 */
Signature · 1 line
2.51.1.821.gb6fe4d2222-goog
Sean Christopherson
maintainerRe: [PATCH 3/3] KVM: nSVM: Avoid incorrect injection of SVM_EXIT_CR0_SEL_WRITE
Quoted 27 lines · Yosry Ahmed
When emulating L2 instructions,
svm_check_intercept()checks whether a write to CR0 should trigger a synthesized #VMEXIT withSVM_EXIT_CR0_SEL_WRITE. However, it does not check whether L1 enabled the intercept forSVM_EXIT_WRITE_CR0, which has higher priority according to the APM (24593—Rev. 3.42—March 2024, Table 15-7):When both selective and non-selective CR0-write intercepts are active at the same time, the non-selective intercept takes priority. With respect to exceptions, the priority of this inter
Make sure L1 does NOT intercept
SVM_EXIT_WRITE_CR0before checking ifSVM_EXIT_CR0_SEL_WRITEneeds to be injected.Fixes cfec82cb7d31 ("KVM: SVM: Add intercept check for emulated cr accesses")Signed-off-by Yosry Ahmed <[email protected]>--- arch/x86/kvm/svm/svm.c | 16 +++++++++++++--- 1 file changed, 13 insertions(+), 3 deletions(-)arch/x86/kvm/svm/svm.c +0
-0@@ -4533,12 +4533,22 @@ static int svm_check_intercept(struct kvm_vcpu *vcpu,if (info->intercept == x86_intercept_cr_write)
arch/x86/kvm/svm/svm.c static int svm_check_intercept(struct kvm_vcpu *vcpu, · line 4543
Quoted 10 lines
arch/x86/kvm/svm/svm.c +7
-0icpt_info.exit_code += info->modrm_reg; +/* +* If the write is indeed to CR0, check whether the exit_code +* needs to be converted to SVM_EXIT_CR0_SEL_WRITE. Intercepting +* SVM_EXIT_WRITE_CR0 has higher priority than +* SVM_EXIT_CR0_SEL_WRITE, so this is only relevant if L1 sets +* INTERCEPT_SELECTIVE_CR0 but not INTERCEPT_CR0_WRITE. +*/ if (icpt_info.exit_code != SVM_EXIT_WRITE_CR0 ||
Oof, the existing is all kinds of confusing. Even with your comment, it took me a few seconds to understand how/where the exit_code is being modified. Eww.
Any objection to opportunistically fixing this up to the (completely untested) below when applying?
/*
* Adjust the exit code accordingly if a CR other than CR0 is
* being written, and skip straight to the common handling as
* only CR0 has an additional selective intercept.
*/
if (info->intercept == x86_intercept_cr_write && info->modrm_reg) {
icpt_info.exit_code += info->modrm_reg;
break;
}
/*
* Convert the exit_code to SVM_EXIT_CR0_SEL_WRITE if L1 set
* INTERCEPT_SELECTIVE_CR0 but not INTERCEPT_CR0_WRITE, as the
* unconditional intercept has higher priority.
*/
if (vmcb12_is_intercept(&svm->nested.ctl, INTERCEPT_CR0_WRITE) ||
!(vmcb12_is_intercept(&svm->nested.ctl, INTERCEPT_SELECTIVE_CR0)))
break;arch/x86/kvm/svm/svm.c static int svm_check_intercept(struct kvm_vcpu *vcpu, · line 4547
Quoted 5 lines
arch/x86/kvm/svm/svm.c +4
-1- info->intercept == x86_intercept_clts) +vmcb12_is_intercept (&svm->nested.ctl, +INTERCEPT_CR0_WRITE ) || + !(vmcb12_is_intercept (&svm->nested.ctl, + INTERCEPT_SELECTIVE_CR0)))
Let these poke out.
Quoted 12 lines
arch/x86/kvm/svm/svm.c +2
-2break ; -if (!(vmcb12_is_intercept (&svm->nested.ctl, -INTERCEPT_SELECTIVE_CR0 ))) +/* CLTS never triggers INTERCEPT_SELECTIVE_CR0 */ +if (info->intercept == x86_intercept_clts)break ;/* LMSW always triggers INTERCEPT_SELECTIVE_CR0 */ Signature · 1 line
2.51.1.821.gb6fe4d2222-goog
Re: [PATCH 3/3] KVM: nSVM: Avoid incorrect injection of SVM_EXIT_CR0_SEL_WRITE
Quoted 42 lines · Sean Christopherson
Quoted 27 lines · Yosry Ahmed
When emulating L2 instructions,
svm_check_intercept()checks whether a write to CR0 should trigger a synthesized #VMEXIT withSVM_EXIT_CR0_SEL_WRITE. However, it does not check whether L1 enabled the intercept forSVM_EXIT_WRITE_CR0, which has higher priority according to the APM (24593—Rev. 3.42—March 2024, Table 15-7):When both selective and non-selective CR0-write intercepts are active at the same time, the non-selective intercept takes priority. With respect to exceptions, the priority of this inter
Make sure L1 does NOT intercept
SVM_EXIT_WRITE_CR0before checking ifSVM_EXIT_CR0_SEL_WRITEneeds to be injected.Fixes cfec82cb7d31 ("KVM: SVM: Add intercept check for emulated cr accesses")Signed-off-by Yosry Ahmed <[email protected]>--- arch/x86/kvm/svm/svm.c | 16 +++++++++++++--- 1 file changed, 13 insertions(+), 3 deletions(-)arch/x86/kvm/svm/svm.c +0
-0@@ -4533,12 +4533,22 @@ static int svm_check_intercept(struct kvm_vcpu *vcpu,if (info->intercept == x86_intercept_cr_write)arch/x86/kvm/svm/svm.c static int svm_check_intercept(struct kvm_vcpu *vcpu, · line 4543
Quoted 10 lines
arch/x86/kvm/svm/svm.c +7
-0icpt_info.exit_code += info->modrm_reg; +/* +* If the write is indeed to CR0, check whether the exit_code +* needs to be converted to SVM_EXIT_CR0_SEL_WRITE. Intercepting +* SVM_EXIT_WRITE_CR0 has higher priority than +* SVM_EXIT_CR0_SEL_WRITE, so this is only relevant if L1 sets +* INTERCEPT_SELECTIVE_CR0 but not INTERCEPT_CR0_WRITE. +*/ if (icpt_info.exit_code != SVM_EXIT_WRITE_CR0 ||Oof, the existing is all kinds of confusing. Even with your comment, it took me a few seconds to understand how/where the
exit_codeis being modified. Eww.
Quoted 2 lines
Any objection to opportunistically fixing this up to the (completely untested) below when applying?
Looks good with a minor nit:
Quoted 16 lines
/*
* Adjust the exit code accordingly if a CR other than CR0 is
* being written, and skip straight to the common handling as
* only CR0 has an additional selective intercept.
*/
if (info->intercept == x86_intercept_cr_write && info->modrm_reg) {
icpt_info.exit_code += info->modrm_reg;
break;
}
/*
* Convert the exit_code to SVM_EXIT_CR0_SEL_WRITE if L1 set
* INTERCEPT_SELECTIVE_CR0 but not INTERCEPT_CR0_WRITE, as the
* unconditional intercept has higher priority.
*/We only convert the exict_code to SVM_EXIT_CR0_SEL_WRITE if other conditions are true below. So maybe "Check if the exit_code needs to be converted to.."?
Quoted 5 lines
if (vmcb12_is_intercept(&svm->nested.ctl, INTERCEPT_CR0_WRITE) || !(vmcb12_is_intercept(&svm->nested.ctl, INTERCEPT_SELECTIVE_CR0))) break;
Quoted 7 lines
arch/x86/kvm/svm/svm.c static int svm_check_intercept(struct kvm_vcpu *vcpu, · line 4547
Quoted 5 lines
arch/x86/kvm/svm/svm.c +4
-1- info->intercept == x86_intercept_clts) +vmcb12_is_intercept (&svm->nested.ctl, +INTERCEPT_CR0_WRITE ) || + !(vmcb12_is_intercept (&svm->nested.ctl, + INTERCEPT_SELECTIVE_CR0)))Let these poke out.
Sure. Do you prefer a new version with this + your fixup above, or will you fix them up while applying?
Quoted 13 lines
Quoted 13 lines
arch/x86/kvm/svm/svm.c +2
-2break ; -if (!(vmcb12_is_intercept (&svm->nested.ctl, -INTERCEPT_SELECTIVE_CR0 ))) +/* CLTS never triggers INTERCEPT_SELECTIVE_CR0 */ +if (info->intercept == x86_intercept_clts)break ;/* LMSW always triggers INTERCEPT_SELECTIVE_CR0 */ Signature · 1 line
2.51.1.821.gb6fe4d2222-goog
Sean Christopherson
maintainerRe: [PATCH 3/3] KVM: nSVM: Avoid incorrect injection of SVM_EXIT_CR0_SEL_WRITE
Quoted 21 lines · Yosry Ahmed
Quoted 1 line · Sean Christopherson
On Fri, Oct 24, 2025, Yosry Ahmed wrote:
Looks good with a minor nit:
Quoted 16 lines
/* * Adjust the exit code accordingly if a CR other than CR0 is * being written, and skip straight to the common handling as * only CR0 has an additional selective intercept. */ if (info->intercept == x86_intercept_cr_write && info->modrm_reg) { icpt_info.exit_code += info->modrm_reg; break; } /* * Convert the exit_code to SVM_EXIT_CR0_SEL_WRITE if L1 set * INTERCEPT_SELECTIVE_CR0 but not INTERCEPT_CR0_WRITE, as the * unconditional intercept has higher priority. */
Quoted 3 lines
We only convert the
exict_codetoSVM_EXIT_CR0_SEL_WRITEif other conditions are true below. So maybe "Check if theexit_codeneeds to be converted to.."?
Ouch, good point. I keep forgetting that the common code below this needs to check the exit_code against the intercept enables. How about this?
/*
* Convert the exit_code to SVM_EXIT_CR0_SEL_WRITE if a
* selective CR0 intercept is triggered (the common logic will
* treat the selective intercept as being enabled). Note, the
* unconditional intercept has higher priority, i.e. this is
* only relevant if *only* the selective intercept is enabled. */
Quoted 14 lines
Quoted 6 lines
if (vmcb12_is_intercept(&svm->nested.ctl, INTERCEPT_CR0_WRITE) || !(vmcb12_is_intercept(&svm->nested.ctl, INTERCEPT_SELECTIVE_CR0))) break;Quoted 7 lines
arch/x86/kvm/svm/svm.c static int svm_check_intercept(struct kvm_vcpu *vcpu, · line 4547
Quoted 5 lines
arch/x86/kvm/svm/svm.c +4
-1- info->intercept == x86_intercept_clts) +vmcb12_is_intercept (&svm->nested.ctl, +INTERCEPT_CR0_WRITE ) || + !(vmcb12_is_intercept (&svm->nested.ctl, + INTERCEPT_SELECTIVE_CR0)))Let these poke out.
Quoted 2 lines
Sure. Do you prefer a new version with this + your fixup above, or will you fix them up while applying?
If you're happy with it, I'll just fixup when applying.
Re: [PATCH 3/3] KVM: nSVM: Avoid incorrect injection of SVM_EXIT_CR0_SEL_WRITE
Quoted 22 lines · Sean Christopherson
Quoted 21 lines · Yosry Ahmed
Quoted 1 line · Sean Christopherson
On Fri, Oct 24, 2025, Yosry Ahmed wrote:
Looks good with a minor nit:
Quoted 16 lines
/* * Adjust the exit code accordingly if a CR other than CR0 is * being written, and skip straight to the common handling as * only CR0 has an additional selective intercept. */ if (info->intercept == x86_intercept_cr_write && info->modrm_reg) { icpt_info.exit_code += info->modrm_reg; break; } /* * Convert the exit_code to SVM_EXIT_CR0_SEL_WRITE if L1 set * INTERCEPT_SELECTIVE_CR0 but not INTERCEPT_CR0_WRITE, as the * unconditional intercept has higher priority. */
Quoted 6 lines
Quoted 3 lines
We only convert the
exict_codetoSVM_EXIT_CR0_SEL_WRITEif other conditions are true below. So maybe "Check if theexit_codeneeds to be converted to.."?Ouch, good point. I keep forgetting that the common code below this needs to check the
exit_codeagainst the intercept enables. How about this?
Looks good.
Quoted 23 lines
/*
* Convert theexit_codetoSVM_EXIT_CR0_SEL_WRITEif a
* selective CR0 intercept is triggered (the common logic will
* treat the selective intercept as being enabled). Note, the
* unconditional intercept has higher priority, i.e. this is
* only relevant if *only* the selective intercept is enabled. */Quoted 14 lines
Quoted 13 lines
if (vmcb12_is_intercept(&svm->nested.ctl, INTERCEPT_CR0_WRITE) || !(vmcb12_is_intercept(&svm->nested.ctl, INTERCEPT_SELECTIVE_CR0))) break;arch/x86/kvm/svm/svm.c static int svm_check_intercept(struct kvm_vcpu *vcpu, · line 4547
Quoted 5 lines
arch/x86/kvm/svm/svm.c +4
-1- info->intercept == x86_intercept_clts) +vmcb12_is_intercept (&svm->nested.ctl, +INTERCEPT_CR0_WRITE ) || + !(vmcb12_is_intercept (&svm->nested.ctl, + INTERCEPT_SELECTIVE_CR0)))Let these poke out.
Quoted 4 lines
Quoted 2 lines
Sure. Do you prefer a new version with this + your fixup above, or will you fix them up while applying?
If you're happy with it, I'll just fixup when applying.
More than happy :)
Quoted 7 lines · Yosry Ahmed
A couple of fixes for injecting
SVM_EXIT_CR0_SEL_WRITEto L1 when emulating MOV-to-CR0 or LMSW. LMSW is handled by the emulator even in some cases where decode assists are enabled, so it's a more important fix. An example would be if L0 interceptsSVM_EXIT_WRITE_CR0while L1 interceptsSVM_EXIT_CR0_SEL_WRITE.Patch is an unrelated cleanup that can be dropped/merged separately.
Patch 1*
Also, related tests:
https://lore.kernel.org/kvm/[email protected]/
Quoted 14 lines
Yosry Ahmed (3):
KVM: nSVM: Remove redundant cases innested_svm_intercept()
KVM: nSVM: PropagateSVM_EXIT_CR0_SEL_WRITEcorrectly for LMSW
emulation
KVM: nSVM: Avoid incorrect injection ofSVM_EXIT_CR0_SEL_WRITEarch/x86/kvm/svm/nested.c | 10 ---------- arch/x86/kvm/svm/svm.c | 34 ++++++++++++++++++++++------------ 2 files changed, 22 insertions(+), 22 deletions(-)Signature · 1 line
2.51.1.821.gb6fe4d2222-goog
Quoted 9 lines · Yosry Ahmed
A couple of fixes for injecting
SVM_EXIT_CR0_SEL_WRITEto L1 when emulating MOV-to-CR0 or LMSW. LMSW is handled by the emulator even in some cases where decode assists are enabled, so it's a more important fix. An example would be if L0 interceptsSVM_EXIT_WRITE_CR0while L1 interceptsSVM_EXIT_CR0_SEL_WRITE.Patch is an unrelated cleanup that can be dropped/merged separately.
[...]
Applied to kvm-x86 svm, with the proper stable@ email and the tweaks to svm_check_intercept(). Thanks!
[1/3] KVM: nSVM: Remove redundant cases in nested_svm_intercept()
https://github.com/kvm-x86/linux/commit/3d31bdf9cc79 [2/3] KVM: nSVM: Propagate SVM_EXIT_CR0_SEL_WRITE correctly for LMSW emulation https://github.com/kvm-x86/linux/commit/5674a76db021 [3/3] KVM: nSVM: Avoid incorrect injection of SVM_EXIT_CR0_SEL_WRITE https://github.com/kvm-x86/linux/commit/3d80f4c93d3d