From: Sean Christopherson <sean.j.christopherson@intel.com>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: linux-kernel@vger.kernel.org, kvm@vger.kernel.org,
thomas.lendacky@amd.com, stable@vger.kernel.org
Subject: Re: [PATCH v2] KVM: x86: use CPUID to locate host page table reserved bits
Date: Tue, 10 Dec 2019 07:37:03 -0800 [thread overview]
Message-ID: <20191210153702.GA15758@linux.intel.com> (raw)
In-Reply-To: <9951afb8-8f91-2fe1-3893-04307fafa570@redhat.com>
On Tue, Dec 10, 2019 at 10:19:57AM +0100, Paolo Bonzini wrote:
> On 04/12/19 16:48, Sean Christopherson wrote:
> >> + /*
> >> + * Quite weird to have VMX or SVM but not MAXPHYADDR; probably a VM with
> >> + * custom CPUID. Proceed with whatever the kernel found since these features
> >> + * aren't virtualizable (SME/SEV also require CPUIDs higher than 0x80000008).
> > No love for MKTME? :-D
>
> I admit I didn't check, but does MKTME really require CPUID leaves in
> the "AMD range"? (My machines have 0x80000008 as the highest supported
> leaf in that range).
Ah, no, I just misunderstood what the blurb in the parentheses was saying.
next prev parent reply other threads:[~2019-12-10 15:37 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-04 15:40 [PATCH v2] KVM: x86: use CPUID to locate host page table reserved bits Paolo Bonzini
2019-12-04 15:48 ` Sean Christopherson
2019-12-10 9:19 ` Paolo Bonzini
2019-12-10 15:37 ` Sean Christopherson [this message]
2019-12-04 15:57 ` Tom Lendacky
2019-12-10 3:53 ` Huang, Kai
2019-12-10 9:18 ` Paolo Bonzini
2019-12-10 9:17 ` Paolo Bonzini
2019-12-11 0:11 ` Huang, Kai
2019-12-11 9:07 ` Paolo Bonzini
2019-12-11 20:48 ` Tom Lendacky
2019-12-11 23:16 ` Huang, Kai
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=20191210153702.GA15758@linux.intel.com \
--to=sean.j.christopherson@intel.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pbonzini@redhat.com \
--cc=stable@vger.kernel.org \
--cc=thomas.lendacky@amd.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