From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from [140.186.70.92] (port=35728 helo=eggs.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.43) id 1OHze5-00014b-Ca
	for qemu-devel@nongnu.org; Fri, 28 May 2010 09:30:42 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.69)
	(envelope-from <vdkouwe@cs.vu.nl>) id 1OHze3-0008Dm-Pb
	for qemu-devel@nongnu.org; Fri, 28 May 2010 09:30:41 -0400
Received: from hera.amn.nl ([213.189.22.5]:2529 helo=AMN.nl)
	by eggs.gnu.org with esmtp (Exim 4.69)
	(envelope-from <vdkouwe@cs.vu.nl>) id 1OHze3-0008DC-KD
	for qemu-devel@nongnu.org; Fri, 28 May 2010 09:30:39 -0400
Message-ID: <4BFFC56B.5010408@cs.vu.nl>
Date: Fri, 28 May 2010 15:30:19 +0200
From: Erik van der Kouwe <vdkouwe@cs.vu.nl>
MIME-Version: 1.0
Subject: Re: [Qemu-devel] Re: SVM emulation: EVENTINJ marked valid when a
	pagefault happens while issuing a software interrupt
References: <4BFE8F13.2000009@cs.vu.nl>
	<4BFEBF9E.90600@web.de>	<4BFECCC3.2000806@cs.vu.nl>
	<4BFEF010.50300@web.de>	<4BFF510B.9050508@cs.vu.nl>
	<4BFF5E73.70508@web.de>	<20100528073531.GD3266@amd.com>
	<20100528132031.GG31920@shareable.org>
In-Reply-To: <20100528132031.GG31920@shareable.org>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
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.nongnu.org/archive/html/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: "Roedel, Joerg" <Joerg.Roedel@amd.com>, Jan Kiszka <jan.kiszka@web.de>, "qemu-devel@nongnu.org" <qemu-devel@nongnu.org>, Gleb Natapov <gleb@redhat.com>

Hi,

>> And the svm-emulation is only available on AMD hardware.
> 
> I assume you mean nested SVM emulation in a KVM guest is only
> available on real AMD hardware?
> 
> Is this due to something inherent, or just a limitation of the KVM
> code not handling all the necessary traps in kvm-intel?

I don't think you could hardware-emulate a CPU from a different brand. 
AMD instructions would probably trap on Intel, but might also just do 
something completely different without a #VMEXIT. Same problem would 
exist vice versa.

Would be nice to have nested VMX support though, given that Intel CPUs 
are so much more common than AMDs. I've been searching on the Dell 
website (in the Netherlands) for a laptop recently and I couldn't find a 
single AMD model.

With kind regards,
Erik