From mboxrd@z Thu Jan 1 00:00:00 1970 From: Gleb Natapov Subject: Re: [PATCH] kvm_para_available() should check hypervisor bit before accessing hypervisor cpuid leaf. Date: Tue, 1 May 2012 15:55:46 +0300 Message-ID: <20120501125546.GI22191@redhat.com> References: <20120430114549.GA22191@redhat.com> <4F9FDC24.5090509@redhat.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: kvm@vger.kernel.org, mtosatti@redhat.com, mst@redhat.com To: Avi Kivity Return-path: Received: from mx1.redhat.com ([209.132.183.28]:44409 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753910Ab2EAMzs (ORCPT ); Tue, 1 May 2012 08:55:48 -0400 Received: from int-mx12.intmail.prod.int.phx2.redhat.com (int-mx12.intmail.prod.int.phx2.redhat.com [10.5.11.25]) by mx1.redhat.com (8.14.4/8.14.4) with ESMTP id q41CtmSD023908 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK) for ; Tue, 1 May 2012 08:55:48 -0400 Content-Disposition: inline In-Reply-To: <4F9FDC24.5090509@redhat.com> Sender: kvm-owner@vger.kernel.org List-ID: On Tue, May 01, 2012 at 03:50:44PM +0300, Avi Kivity wrote: > On 04/30/2012 02:45 PM, Gleb Natapov wrote: > > This couid range does not exist on real HW and Intel spec says that > > "Information returned for highest basic information leaf" will be > > returned. Not very well defined. > > > > Correct in principle. But IIRC some old qemus supported the kvm cpuid > range without setting the hypervisor bit. > How old? -- Gleb.