WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

Re: [Xen-devel] mmx sse emulation

To: "Keir Fraser" <keir.fraser@xxxxxxxxxxxxx>
Subject: Re: [Xen-devel] mmx sse emulation
From: "Ashish Bijlani" <ashish.bijlani@xxxxxxxxx>
Date: Wed, 5 Nov 2008 02:52:07 -0500
Cc: xen-devel@xxxxxxxxxxxxxxxxxxx
Delivery-date: Tue, 04 Nov 2008 23:52:31 -0800
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to :subject:cc:in-reply-to:mime-version:content-type :content-transfer-encoding:content-disposition:references; bh=+337xW2GL/c0WheYeQCEiaBNO9X9xgXq3r/L5FRZ6SU=; b=Ka2VY3OOTKITVgQUeqUCgQRwJ8VXEgeviH40Z6vUwo3UezH3OQchD+S0XKjoy/MuaF Tzphbe8sP6rV7uRack0sOSfyw2BOj1CP3tiqsnYyXinsuejZDfn6HLXCBJYwQUeCcNoY hyIWzKX6aMde1xNBE1eKjMk6BymHhkjk404Nw=
Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:cc:in-reply-to:mime-version :content-type:content-transfer-encoding:content-disposition :references; b=iJkBSrn8BCpDjFDRpdy6NhA9CPjzhVeKwEv2vF48wyOAyzJ/tsHT8RC/cL6PdxFXn/ Uw5uuMNdMVTcUHWAvvTnm5oP+VW4dvpe3ONKx6e8SYUJP/PuW7Cbu7TfAC1rFCO13OJ2 wtGmCehleVks/TomOguoBF5gpSMEXxvo8bnCE=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <C536FCFA.1EE2A%keir.fraser@xxxxxxxxxxxxx>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References: <ec55b17e0811041634n30c3fc19s5c425d8f41246776@xxxxxxxxxxxxxx> <C536FCFA.1EE2A%keir.fraser@xxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Hi Keir,

Thanks for the help. I've one more doubt though.

Calling x86_emulate from do_device_not_available after validating the
EM flag would work? Of course provided MMX/SS emulation code reside in
x86_emulate. Please lemme know.

Thanks,
Ashish

On Wed, Nov 5, 2008 at 2:34 AM, Keir Fraser <keir.fraser@xxxxxxxxxxxxx> wrote:
> On 5/11/08 00:34, "Ashish Bijlani" <ashish.bijlani@xxxxxxxxx> wrote:
>
>>
>> I want to emulate mmx/sse for hvm guests when applications inside hvm
>> guests are compiled for mmx/sse but the underlying hardware doesn't
>> support mmx/sse. What is the best place to do this? i'm looking at
>> x86_emulate but i dunno if that is the best place to put the emulation
>> layer. any suggestions?? also, currently movq emulation is present in
>> x86_emulate for handling mmio. however, i realized that get_fpu fails
>> if the hardware doesn't have mmx capability. is it true or am i
>> missing something here?
>
> x86_emulate() does its work by using the actual underlying processor
> instructions (really it is a system emulator rather than an instruction
> emulator). This wouldn't necessarily stop you adding full emulation for
> certain instructions like SSE/MMX though, and it's probably the right place
> to put that sort of thing.
>
>  -- Keir
>
>
>

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel

<Prev in Thread] Current Thread [Next in Thread>