[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Xen-devel] fsincos emulation on AMD CPUs


  • To: Jan Beulich <JBeulich@xxxxxxxx>
  • From: Keir Fraser <keir@xxxxxxx>
  • Date: Thu, 15 Dec 2011 16:52:50 +0000
  • Cc: Paolo Bonzini <pbonzini@xxxxxxxxxx>, xen-devel@xxxxxxxxxxxxxxxxxxx
  • Delivery-date: Thu, 15 Dec 2011 16:53:21 +0000
  • List-id: Xen developer discussion <xen-devel.lists.xensource.com>
  • Thread-index: Acy7SfqzW+wVJ4SAYEisTdde2oqROQ==
  • Thread-topic: [Xen-devel] fsincos emulation on AMD CPUs

On 15/12/2011 13:19, "Jan Beulich" <JBeulich@xxxxxxxx> wrote:

>>>> On 15.12.11 at 14:13, Keir Fraser <keir@xxxxxxx> wrote:
>> On 15/12/2011 13:08, "Jan Beulich" <JBeulich@xxxxxxxx> wrote:
>> 
>>>>>> On 15.12.11 at 13:33, Keir Fraser <keir@xxxxxxx> wrote:
>>>> More detail: the full patch is ugly and hard to test all cases. And there's
>>>> no practical scenario where we want to emulate FSINCOS on AMD -- we don't
>>>> emulate realmode on AMD, FSINCOS on a shadowed page certainly indicates
>>>> that
>>>> we should unshadow the page, FSINCOS on MMIO is mad or malicious.
>>> 
>>> Those latter two cases can't really happen, as fsincos has no memory
>>> operand.
>> 
>> Possibly if the instruction itself was in a recycled page-table page? Or in
>> an MMIO page, or the malicious race that Paolo described --- definitely
>> malicious either way.
>> 
>> Anyhow the short answer is we never want to emulate it on AMD. :-)
> 
> I just sent out the patch as quoted in the reply to Paolo, but you're
> suggesting to be even more drastic and ignore the CPU family. If
> you really want it done that way, I wonder whether we should bail on
> AMD for *all* x87 operations not having memory operands.

Your patch is fine.

 -- Keir

> Jan
> 



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


 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.