All of lore.kernel.org
 help / color / mirror / Atom feed
From: Michael Ellerman <mpe@ellerman.id.au>
To: Anshuman Khandual <khandual@linux.vnet.ibm.com>
Cc: linuxppc-dev@ozlabs.org, linuxram@us.ibm.com,
	Jeremy Kerr <jk@ozlabs.org>
Subject: Re: [PATCH v3 2/2] selftests/powerpc: Add a test of the switch_endian() syscall
Date: Wed, 18 Mar 2015 16:04:19 +1100	[thread overview]
Message-ID: <1426655059.6504.4.camel@ellerman.id.au> (raw)
In-Reply-To: <5507C437.3020203@linux.vnet.ibm.com>

On Tue, 2015-03-17 at 11:35 +0530, Anshuman Khandual wrote:
> On 03/17/2015 04:34 AM, Michael Ellerman wrote:
> > What are you seeing exactly?
> 
> I am running on a BE PKVM guest but compiling the test case on
> a different BE machine which has newer version of the compiler.
> 
> cc (GCC) 4.8.3 20140624
> 
> cc -O2 -Wall -g -nostdlib -m64   -c -o check.o check.S
> objcopy -j .text --reverse-bytes=4 -O binary check.o check-reversed.o
> hexdump -v -e '/1 ".byte 0x%02X\n"' check-reversed.o > check-reversed.S
> cc -O2 -Wall -g -nostdlib -m64    switch_endian_test.S check-reversed.S   -o switch_endian_test
> 
> which looks very similar to the details you have provided above.
> Running on guest or host should not make any difference.

No it shouldn't.

Can you try strace, that should give you the full result code.

Also can you try gdb. You can't breakpoint in the wrong-endian region, but it
looks like you're getting through that anyway.

So try setting a breakpoint at line ~77, and you should be back in BE. Then you
can single step and see where it errors out.

> BTW, we need to add one .gitignore file to this new test directory.

Oh yeah, thanks for the reminder.

cheers

  reply	other threads:[~2015-03-18  5:04 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-16  6:57 [PATCH v3 1/2] powerpc: Add a proper syscall for switching endianness Michael Ellerman
2015-03-16  6:57 ` [PATCH v3 2/2] selftests/powerpc: Add a test of the switch_endian() syscall Michael Ellerman
2015-03-16 11:00   ` Anshuman Khandual
2015-03-16 23:04     ` Michael Ellerman
2015-03-17  6:05       ` Anshuman Khandual
2015-03-18  5:04         ` Michael Ellerman [this message]
2015-03-25  5:28           ` Michael Ellerman
2015-03-25 11:32             ` Anshuman Khandual
2015-03-26  0:36               ` Michael Ellerman
2015-03-26  6:24                 ` Anshuman Khandual
2015-03-28  2:34                   ` Michael Ellerman

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=1426655059.6504.4.camel@ellerman.id.au \
    --to=mpe@ellerman.id.au \
    --cc=jk@ozlabs.org \
    --cc=khandual@linux.vnet.ibm.com \
    --cc=linuxppc-dev@ozlabs.org \
    --cc=linuxram@us.ibm.com \
    /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.