All of lore.kernel.org
 help / color / mirror / Atom feed
From: Don Slutz <dslutz@verizon.com>
To: Jan Beulich <JBeulich@suse.com>, Don Slutz <dslutz@verizon.com>
Cc: Keir Fraser <keir@xen.org>, xen-devel@lists.xen.org
Subject: Re: test_x86_emulator
Date: Tue, 15 Apr 2014 10:24:08 -0400	[thread overview]
Message-ID: <534D4108.2020100@terremark.com> (raw)
In-Reply-To: <534CF2950200007800008C62@nat28.tlf.novell.com>

[-- Attachment #1: Type: text/plain, Size: 1757 bytes --]

On 04/15/14 02:49, Jan Beulich wrote:
>>>> On 14.04.14 at 19:29, <dslutz@verizon.com> wrote:
>> It is more complex then it appears at 1st look.
>>
>> -O1:
>> ...
>> Testing movdqu (%edx),%xmm4...          okay
>> Testing vmovdqu %ymm2,(%ecx)...         skipped
>> Testing vmovdqu (%edx),%ymm4...         skipped
>> Testing movsd %xmm5,(%ecx)...           okay
>> Testing movaps (%edx),%xmm7...          okay
>> ...
>>
>> -O2:
>> ...
>> Testing movdqu (%edx),%xmm4...          okay
>> Testing vmovdqu %ymm2,(%ecx)...         failed!
>> make: *** [run] Error 1
> Now that's of course very interesting - looks more like a problem
> with test_x86_emulator.c's use of CPUID then (because you said
> you do this on an AVX-capable system, the -O1 test shouldn't skip
> these).
>
>> get_fpu (exception_callback=0x402a60 <fpu_handle_exception>,
>> exception_callback_arg=0x7fffffffd7d0,
>>       type=X86EMUL_FPU_ymm, ctxt=0x7fffffffdb80) at test_x86_emulator.c:138
>> 138         switch ( type )
>> (gdb) n
>> 137     {
>> (gdb)
>> 138         switch ( type )
>> (gdb)
>> 154         return X86EMUL_OKAY;
>> (gdb)
>> 138         switch ( type )
>> (gdb)
>> 152             return X86EMUL_UNHANDLEABLE;
>> (gdb)
>> 138         switch ( type )
>> (gdb)
>> 132     int get_fpu(
>> (gdb)
>> 155     }
> Or a code generation problem: An input of X86EMUL_FPU_ymm should
> obviously result in execution making to the respective case statement,
> yet the steps above lead directly to the default one.
>
> What gcc version are you using? And could you perhaps make both
> binaries (-O1 and -O2) available for inspection?

dcs-xen-54:~/xen/tools/tests/x86_emulator>gcc --version
gcc (GCC) 4.7.2 20120921 (Red Hat 4.7.2-2)

Attached are the binaries.

    -Don Slutz
> Jan
>


[-- Attachment #2: x86_emulate.o.O2 --]
[-- Type: application/octet-stream, Size: 548584 bytes --]

[-- Attachment #3: x86_emulate.o.O1 --]
[-- Type: application/octet-stream, Size: 295952 bytes --]

[-- Attachment #4: test_x86_emulator.o.O1 --]
[-- Type: application/octet-stream, Size: 71008 bytes --]

[-- Attachment #5: test_x86_emulator.o.O2 --]
[-- Type: application/octet-stream, Size: 92944 bytes --]

[-- Attachment #6: blowfish.o.O2 --]
[-- Type: application/octet-stream, Size: 14344 bytes --]

[-- Attachment #7: blowfish.o.O1 --]
[-- Type: application/octet-stream, Size: 14344 bytes --]

[-- Attachment #8: Type: text/plain, Size: 126 bytes --]

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel

  reply	other threads:[~2014-04-15 14:24 UTC|newest]

Thread overview: 47+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-08 14:24 [PATCH v2 00/10] Prevent one cause of "MP-BIOS bug: 8254 timer"... message from linux Don Slutz
2014-04-08 14:24 ` [PATCH v2 01/10] hvm/hpet: Add manual unit test code Don Slutz
2014-04-09 16:08   ` Jan Beulich
2014-04-09 18:35     ` Don Slutz
2014-04-10  6:11       ` Jan Beulich
2014-04-11  2:53         ` Don Slutz
2014-04-11  7:45           ` Jan Beulich
2014-04-11 11:57             ` [PATCH optional " Don Slutz
2014-04-11 12:09               ` Jan Beulich
2014-04-11 12:48                 ` Don Slutz
2014-04-11 15:14                   ` Jan Beulich
2014-04-11 17:40                     ` Don Slutz
2014-04-14  7:40                       ` Jan Beulich
2014-04-14 17:29                         ` test_x86_emulator (was Re: [PATCH optional v2 01/10] hvm/hpet: Add manual unit test code.) Don Slutz
2014-04-15  6:49                           ` test_x86_emulator Jan Beulich
2014-04-15 14:24                             ` Don Slutz [this message]
2014-04-16  8:26                               ` test_x86_emulator Jan Beulich
2014-04-16  9:32                                 ` test_x86_emulator Keir Fraser
2014-04-16 15:21                                   ` test_x86_emulator Don Slutz
2014-04-08 14:24 ` [PATCH v2 02/10] hvm/hpet: Only call guest_time_hpet(h) one time per action Don Slutz
2014-04-14 14:31   ` Jan Beulich
2014-04-14 17:38     ` Don Slutz
2014-04-08 14:24 ` [PATCH v2 03/10] hvm/hpet: Only set comparator or period not both Don Slutz
2014-04-14 14:58   ` Jan Beulich
2014-04-14 22:53     ` Don Slutz
2014-04-15  6:59       ` Jan Beulich
2014-04-16  4:06         ` Don Slutz
2014-04-08 14:24 ` [PATCH v2 04/10] hvm/hpet: In hpet_save, correctly compute mc64 Don Slutz
2014-04-08 14:24 ` [PATCH v2 05/10] hvm/hpet: Init comparator64 like comparator Don Slutz
2014-04-08 14:24 ` [PATCH v2 06/10] hvm/hpet: comparator can only change when master clock is enabled Don Slutz
2014-04-14 15:07   ` Jan Beulich
2014-04-14 19:50     ` Don Slutz
2014-04-15  7:05       ` Jan Beulich
2014-04-15 15:53         ` Don Slutz
2014-04-15 16:14           ` Jan Beulich
2014-04-15 18:11             ` Don Slutz
2014-04-16  8:42               ` Jan Beulich
2014-04-08 14:24 ` [PATCH v2 07/10] hvm/hpet: Call hpet_get_comparator during hpet_save Don Slutz
2014-04-14 15:13   ` Jan Beulich
2014-04-15  0:21     ` Don Slutz
2014-04-15  7:06       ` Jan Beulich
2014-04-15 14:18         ` Don Slutz
2014-04-08 14:24 ` [PATCH v2 08/10] hvm/hpet: Prevent master clock equal to comparator while enabled Don Slutz
2014-04-08 14:24 ` [PATCH v2 09/10] hvm/hpet: Correctly limit period to a maximum Don Slutz
2014-04-08 14:24 ` [PATCH v2 10/10] hvm/hpet: handle 1st period special Don Slutz
2014-04-14 15:27   ` Jan Beulich
2014-04-15  0:21     ` Don Slutz

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=534D4108.2020100@terremark.com \
    --to=dslutz@verizon.com \
    --cc=JBeulich@suse.com \
    --cc=keir@xen.org \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.