From: Fabio Fantoni <fabio.fantoni@m2r.biz>
To: Jan Beulich <JBeulich@suse.com>
Cc: George Dunlap <george.dunlap@eu.citrix.com>,
Andrew Cooper <andrew.cooper3@citrix.com>,
"xen-devel@lists.xen.org" <xen-devel@lists.xen.org>,
Anthony PERARD <anthony.perard@citrix.com>
Subject: Re: Xen 4.3 development update RC2 imminent
Date: Thu, 23 May 2013 12:36:35 +0200 [thread overview]
Message-ID: <519DF133.1020808@m2r.biz> (raw)
In-Reply-To: <519DE3D702000078000D85B4@nat28.tlf.novell.com>
Il 23/05/2013 09:39, Jan Beulich ha scritto:
>>>> On 22.05.13 at 18:54, George Dunlap <george.dunlap@eu.citrix.com> wrote:
>> On 22/05/13 17:30, Pasi Kärkkäinen wrote:
>>> On Wed, May 22, 2013 at 04:05:27PM +0100, George Dunlap wrote:
>>> Hmm, for testing, can we use cpuid to mask out SSE,
>>> and then try qxl ?
>> That had occurred to me -- Andrew / Jan, do you know which flag might
>> disable this particular instruction?
>>
>> I guess we could try just disabling all the SSE instructions.
> movdqu is an SSE2 instruction, so disabling bit 26 of CPUID EDX
> output to EAX=1 input.
Can you explain better please?
Should I add this to test it?
cpuid="host,sse=0,sse2=0,ssse3=0,sse4_1=0,sse4_2=0,eax=1"
>
> However, just like the hypervisor itself does, 64-bit code may
> imply SSE2 to be available unconditionally (i.e. without looking at
> any feature flags). In particular, both single and double precision
> math are done via SSE/SSE2 instructions rather than FPU ones by
> default on x86-64.
>
> Jan
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
next prev parent reply other threads:[~2013-05-23 10:36 UTC|newest]
Thread overview: 52+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-20 10:33 Xen 4.3 development update RC2 imminent George Dunlap
2013-05-20 10:36 ` George Dunlap
2013-05-20 17:12 ` Keir Fraser
2013-05-21 8:13 ` Tim Deegan
2013-05-21 10:22 ` Jan Beulich
2013-05-21 8:19 ` Jan Beulich
2013-05-21 8:22 ` George Dunlap
2013-05-21 8:25 ` Jan Beulich
2013-05-20 10:51 ` Wei Liu
2013-05-20 11:09 ` George Dunlap
2013-05-20 11:16 ` Ian Campbell
2013-05-20 11:32 ` George Dunlap
2013-05-20 11:46 ` Ian Campbell
2013-05-20 13:42 ` George Dunlap
2013-05-20 11:15 ` Ian Campbell
2013-05-20 11:22 ` George Dunlap
2013-05-20 11:26 ` Ian Campbell
2013-05-20 11:28 ` George Dunlap
2013-05-20 11:48 ` Ian Campbell
2013-05-21 14:06 ` Anthony PERARD
2013-05-21 14:31 ` Andrew Cooper
2013-05-21 14:49 ` George Dunlap
2013-05-21 14:55 ` Jan Beulich
2013-05-21 14:58 ` Andrew Cooper
2013-05-21 15:07 ` Jan Beulich
2013-05-21 16:13 ` George Dunlap
2013-05-21 16:16 ` George Dunlap
2013-05-22 12:49 ` Fabio Fantoni
2013-05-22 12:58 ` Andrew Cooper
2013-05-22 15:05 ` George Dunlap
2013-05-22 16:30 ` Pasi Kärkkäinen
2013-05-22 16:54 ` George Dunlap
2013-05-23 7:39 ` Jan Beulich
2013-05-23 10:36 ` Fabio Fantoni [this message]
2013-05-23 10:39 ` Andrew Cooper
2013-05-23 10:54 ` George Dunlap
2013-05-23 14:17 ` Fabio Fantoni
2013-05-23 14:26 ` George Dunlap
2013-05-23 14:35 ` George Dunlap
2013-05-23 14:58 ` Fabio Fantoni
2013-05-23 15:10 ` Pasi Kärkkäinen
2013-05-23 16:10 ` George Dunlap
2013-05-23 16:07 ` George Dunlap
2013-05-24 13:56 ` Fabio Fantoni
2013-05-24 13:59 ` George Dunlap
2013-05-24 14:53 ` Fabio Fantoni
2013-05-24 15:52 ` George Dunlap
2013-05-23 14:32 ` George Dunlap
2013-05-23 10:48 ` Jan Beulich
2013-05-23 10:31 ` Fabio Fantoni
2013-05-23 14:01 ` Pasi Kärkkäinen
2013-05-22 12:48 ` Fabio Fantoni
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=519DF133.1020808@m2r.biz \
--to=fabio.fantoni@m2r.biz \
--cc=JBeulich@suse.com \
--cc=andrew.cooper3@citrix.com \
--cc=anthony.perard@citrix.com \
--cc=george.dunlap@eu.citrix.com \
--cc=xen-devel@lists.xen.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).