lkml.org 
[lkml]   [2021]   [Sep]   [21]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
SubjectRe: [PATCH v2] KVM: nVMX: Fix nested bus lock VM exit
From
Date
On 9/14/2021 5:50 PM, Chenyi Qiang wrote:
> Nested bus lock VM exits are not supported yet. If L2 triggers bus lock
> VM exit, it will be directed to L1 VMM, which would cause unexpected
> behavior. Therefore, handle L2's bus lock VM exits in L0 directly.
>
> Fixes: fe6b6bc802b4 ("KVM: VMX: Enable bus lock VM exit")
> Signed-off-by: Chenyi Qiang <chenyi.qiang@intel.com>

Reviewed-by: Xiaoyao Li <xiaoyao.li@intel.com>

> ---
> Change log
> v1->v2
> - Because nested bus lock VM exit is not supported and how nested
> support would operate is uncertain. Add a brief comment to state that this
> feature is never exposed to L1 at present. (Sean)
> - v1: https://lore.kernel.org/lkml/20210827085110.6763-1-chenyi.qiang@intel.com/
> ---
> arch/x86/kvm/vmx/nested.c | 6 ++++++
> 1 file changed, 6 insertions(+)
>
> diff --git a/arch/x86/kvm/vmx/nested.c b/arch/x86/kvm/vmx/nested.c
> index bc6327950657..5646cc1e8d4c 100644
> --- a/arch/x86/kvm/vmx/nested.c
> +++ b/arch/x86/kvm/vmx/nested.c
> @@ -5873,6 +5873,12 @@ static bool nested_vmx_l0_wants_exit(struct kvm_vcpu *vcpu,
> case EXIT_REASON_VMFUNC:
> /* VM functions are emulated through L2->L0 vmexits. */
> return true;
> + case EXIT_REASON_BUS_LOCK:
> + /*
> + * At present, bus lock VM exit is never exposed to L1.
> + * Handle L2's bus locks in L0 directly.
> + */
> + return true;
> default:
> break;
> }
>

\
 
 \ /
  Last update: 2021-09-22 04:00    [W:0.064 / U:0.168 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site