Re: [PATCH v3 2/9] KVM: x86: Add CR4.LAM_SUP in guest owned bits

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Subject: Re: [PATCH v3 2/9] KVM: x86: Add CR4.LAM_SUP in guest owned bits
From: Sean Christopherson <seanjc@xxxxxxxxxx>
Date: Sat, 7 Jan 2023 00:38:23 +0000
Cc: pbonzini@xxxxxxxxxx, kirill.shutemov@xxxxxxxxxxxxxxx, kvm@xxxxxxxxxxxxxxx, Jingqi Liu <jingqi.liu@xxxxxxxxx>
In-reply-to: <20221209044557.1496580-3-robert.hu@linux.intel.com>
References: <20221209044557.1496580-1-robert.hu@linux.intel.com> <20221209044557.1496580-3-robert.hu@linux.intel.com>

On Fri, Dec 09, 2022, Robert Hoo wrote:
> If LAM enabled, CR4.LAM_SUP is owned by guest; otherwise, reserved.

Why is it passed through to the guest?

Follow-Ups:
- Re: [PATCH v3 2/9] KVM: x86: Add CR4.LAM_SUP in guest owned bits
  - From: Robert Hoo

References:
- [PATCH v3 0/9] Linear Address Masking (LAM) KVM Enabling
  - From: Robert Hoo
- [PATCH v3 2/9] KVM: x86: Add CR4.LAM_SUP in guest owned bits
  - From: Robert Hoo

Prev by Date: Re: [PATCH v8 15/16] x86/virt/tdx: Flush cache in kexec() when TDX is enabled
Next by Date: Re: [PATCH v3 3/9] KVM: x86: MMU: Rename get_cr3() --> get_pgd() and clear high bits for pgd
Previous by thread: [PATCH v3 2/9] KVM: x86: Add CR4.LAM_SUP in guest owned bits
Next by thread: Re: [PATCH v3 2/9] KVM: x86: Add CR4.LAM_SUP in guest owned bits
Index(es):
- Date
- Thread

[Index of Archives] [KVM ARM] [KVM ia64] [KVM ppc] [Virtualization Tools] [Spice Development] [Libvirt] [Libvirt Users] [Linux USB Devel] [Linux Audio Users] [Yosemite Questions] [Linux Kernel] [Linux SCSI] [XFree86]

Powered by Linux