Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67;
Date:   Tue, 10 Dec 2019 07:37:03 -0800
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
Message-ID: <20191210153702.GA15758@linux.intel.com>
References: <1575474037-7903-1-git-send-email-pbonzini@redhat.com>
 <20191204154806.GC6323@linux.intel.com>
 <9951afb8-8f91-2fe1-3893-04307fafa570@redhat.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <9951afb8-8f91-2fe1-3893-04307fafa570@redhat.com>
User-Agent: Mutt/1.5.24 (2015-08-30)
Sender: linux-kernel-owner@vger.kernel.org
Precedence: bulk

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.