linux-kernel - Re: [PATCH v2] KVM: x86: use CPUID to locate host page table reserved bits

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20191210153702.GA15758@linux.intel.com>
Date:   Tue, 10 Dec 2019 07:37:03 -0800
From:   Sean Christopherson <sean.j.christopherson@...el.com>
To:     Paolo Bonzini <pbonzini@...hat.com>
Cc:     linux-kernel@...r.kernel.org, kvm@...r.kernel.org,
        thomas.lendacky@....com, stable@...r.kernel.org
Subject: Re: [PATCH v2] KVM: x86: use CPUID to locate host page table
 reserved bits

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.