From: "Huang, Kai" <kai.huang@intel.com>
To: "binbin.wu@linux.intel.com" <binbin.wu@linux.intel.com>
Cc: "kvm@vger.kernel.org" <kvm@vger.kernel.org>,
"robert.hu@linux.intel.com" <robert.hu@linux.intel.com>,
"pbonzini@redhat.com" <pbonzini@redhat.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"Christopherson,, Sean" <seanjc@google.com>,
"Gao, Chao" <chao.gao@intel.com>
Subject: Re: [PATCH v8 2/6] KVM: x86: Virtualize CR4.LAM_SUP
Date: Fri, 12 May 2023 10:49:36 +0000 [thread overview]
Message-ID: <982ce5177647331b7b9f6526dfe064b76a921d06.camel@intel.com> (raw)
In-Reply-To: <abbb7938-0615-8578-0072-a96d21df3b4d@linux.intel.com>
> > >
> > LAM only applies to 64-bit linear address, which means LAM can only be enabled
> > when CPU is in 64-bit mode with either 4-level or 5-level paging enabled.
> >
> > What's the hardware behaviour if we set CR4.LAM_SUP when CPU isn't in 64-bit
> > mode? And how does VMENTRY check GUEST_CR4.LAM_SUP and 64-bit mode?
> >
> > Looks they are not clear in the spec you pasted in the cover letter:
> >
> > https://cdrdv2.intel.com/v1/dl/getContent/671368
> >
> > Or I am missing something?
> Yes, it is not clearly described in LAM spec.
> Had some internal discussions and also did some tests in host,
> if the processor supports LAM, CR4.LAM_SUP is allowed to be set even
> when cpu isn't in 64bit mode.
>
> There was a statement in commit message of the last version, but I
> missed it in this version. I'll add it back.
> "CR4.LAM_SUP is allowed to be set even not in 64-bit mode, but it will not
> take effect since LAM only applies to 64-bit linear address."
Yeah this does help. Please add it back to the changelog.
>
> Also, I will try to ask Intel guys if it's possible to update the document.
>
Thanks.
next prev parent reply other threads:[~2023-05-12 10:50 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-10 6:06 [PATCH v8 0/6] Linear Address Masking (LAM) KVM Enabling Binbin Wu
2023-05-10 6:06 ` [PATCH v8 1/6] KVM: x86: Consolidate flags for __linearize() Binbin Wu
2023-05-10 7:42 ` Chao Gao
2023-05-11 1:25 ` Binbin Wu
2023-05-11 9:58 ` David Laight
2023-05-12 1:35 ` Binbin Wu
2023-05-10 12:41 ` Huang, Kai
2023-05-11 1:30 ` Binbin Wu
2023-05-10 6:06 ` [PATCH v8 2/6] KVM: x86: Virtualize CR4.LAM_SUP Binbin Wu
2023-05-11 12:50 ` Huang, Kai
2023-05-12 1:33 ` Binbin Wu
2023-05-12 10:49 ` Huang, Kai [this message]
2023-05-18 4:01 ` Binbin Wu
2023-05-10 6:06 ` [PATCH v8 3/6] KVM: x86: Virtualize CR3.LAM_{U48,U57} Binbin Wu
2023-05-10 8:58 ` Chao Gao
2023-05-11 1:27 ` Binbin Wu
2023-05-10 11:59 ` Huang, Kai
2023-05-10 6:06 ` [PATCH v8 4/6] KVM: x86: Introduce untag_addr() in kvm_x86_ops Binbin Wu
2023-05-11 6:03 ` Chao Gao
2023-05-11 9:18 ` Binbin Wu
2023-05-11 10:37 ` Chao Gao
2023-05-10 6:06 ` [PATCH v8 5/6] KVM: x86: Untag address when LAM applicable Binbin Wu
2023-05-11 6:28 ` Chao Gao
2023-05-10 6:06 ` [PATCH v8 6/6] KVM: x86: Expose LAM feature to userspace VMM Binbin Wu
2023-05-12 12:49 ` Huang, Kai
2023-05-16 3:30 ` Binbin Wu
2023-05-25 2:08 ` [PATCH v8 0/6] Linear Address Masking (LAM) KVM Enabling Binbin Wu
2023-05-25 15:59 ` Sean Christopherson
2023-06-06 9:26 ` Binbin Wu
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=982ce5177647331b7b9f6526dfe064b76a921d06.camel@intel.com \
--to=kai.huang@intel.com \
--cc=binbin.wu@linux.intel.com \
--cc=chao.gao@intel.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pbonzini@redhat.com \
--cc=robert.hu@linux.intel.com \
--cc=seanjc@google.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®