From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43)
	id 1NLjBO-0003cL-Kl
	for qemu-devel@nongnu.org; Fri, 18 Dec 2009 15:12:14 -0500
Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43)
	id 1NLjBI-0003Ui-74
	for qemu-devel@nongnu.org; Fri, 18 Dec 2009 15:12:12 -0500
Received: from [199.232.76.173] (port=42941 helo=monty-python.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.43) id 1NLjBH-0003TT-3g
	for qemu-devel@nongnu.org; Fri, 18 Dec 2009 15:12:07 -0500
Received: from mx20.gnu.org ([199.232.41.8]:21978)
	by monty-python.gnu.org with esmtps (TLS-1.0:RSA_AES_256_CBC_SHA1:32)
	(Exim 4.60) (envelope-from <agraf@suse.de>) id 1NLjBG-0000gv-IX
	for qemu-devel@nongnu.org; Fri, 18 Dec 2009 15:12:06 -0500
Received: from cantor2.suse.de ([195.135.220.15] helo=mx2.suse.de)
	by mx20.gnu.org with esmtp (Exim 4.60)
	(envelope-from <agraf@suse.de>) id 1NLjBF-0005Xq-IW
	for qemu-devel@nongnu.org; Fri, 18 Dec 2009 15:12:05 -0500
Message-ID: <4B2BE098.3060704@suse.de>
Date: Fri, 18 Dec 2009 21:05:44 +0100
From: Alexander Graf <agraf@suse.de>
MIME-Version: 1.0
Subject: Re: [Qemu-devel] Re: SVM support in 0.12?
References: <fdaac4d50912171837k2eb2f3a2l81de933dab5b521c@mail.gmail.com>
	<fdaac4d50912171839v5dd7b108u1f04cc58f8102cdf@mail.gmail.com>
	<F780F0C5-3C21-4D85-820D-80BB4C4B7C62@suse.de>
	<20091218200358.GD1205@shareable.org>
In-Reply-To: <20091218200358.GD1205@shareable.org>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
List-Id: qemu-devel.nongnu.org
List-Unsubscribe: <http://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/pipermail/qemu-devel>
List-Post: <mailto:qemu-devel@nongnu.org>
List-Help: <mailto:qemu-devel-request@nongnu.org?subject=help>
List-Subscribe: <http://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=subscribe>
To: Jamie Lokier <jamie@shareable.org>
Cc: "qemu-devel@nongnu.org" <qemu-devel@nongnu.org>, Jun Koi <junkoi2004@gmail.com>

Jamie Lokier wrote:
> Alexander Graf wrote:
>   
>> Am 18.12.2009 um 03:39 schrieb Jun Koi <junkoi2004@gmail.com>
>>
>>     
>>> On Fri, Dec 18, 2009 at 11:37 AM, Jun Koi <junkoi2004@gmail.com>  
>>> wrote:
>>>       
>>>> Hi,
>>>>
>>>> I am running latest Qemu 0.12-rc. My guest VM runs Linux kernel  
>>>> 2.6.31.
>>>>
>>>> Because Qemu now supports SVM, I expect to see the SVM flag in
>>>> /proc/cpuinfo, but that is not the case.
>>>>
>>>> So it seems SVM support is not enabled by default configuration??
>>>>
>>>>         
>>> My host and guest are both 32 bit Linux, if that matters.
>>>
>>> (And this is pure Qemu, without using KVM or KQemu)
>>>       
>> Kqemu actually works with svm emulation.
>>
>> Have you tried -cpu qemu32,+svm? I think I only enabled svm on qemu64,  
>> because I'm not aware of 32-bit AMD CPUs that can do svm.
>>     
>
> 32-bit VT (Intel) definitely exists.
>
> If there aren't any 32-bit AMDs with SVM, does SVM even have defined
> 32-bit semantics?
>   

Yes, it does.

> But I see the kvm kernel code can build 32-bit SVM support.  I wonder
> if it has ever been tested :-)
>   

Well, just because all SVM capable CPUs are long mode capable doesn't
mean you have to run an x86_64 kernel on them.

>> Also, back when I developed it, 32-bit kvm didn't really work  
>> properly. So please let me know what you find out!
>>     
>
> Do you mean 32-bit kvm on a 32-bit host, or 32-bit kvm inside your SVM
> emulation?  kvm works very well on 32-bit Intel hosts.
>   

32-bit kvm inside my SVM emulation.


Alex