All of lore.kernel.org
 help / color / mirror / Atom feed
From: xiakaixu <xiakaixu@huawei.com>
To: Jan Stancek <jstancek@redhat.com>
Cc: Jiri Olsa <jolsa@redhat.com>,
	adrian hunter <adrian.hunter@intel.com>,
	Arnaldo Carvalho de Melo <acme@kernel.org>,
	Ingo Molnar <mingo@kernel.org>,
	masami hiramatsu pt <masami.hiramatsu.pt@hitachi.com>,
	<linux-kernel@vger.kernel.org>,
	"Wangnan (F)" <wangnan0@huawei.com>
Subject: Re: [BUG] perf test 21("Test object code reading") failure on ARM64
Date: Mon, 21 Dec 2015 10:18:20 +0800	[thread overview]
Message-ID: <5677616C.2060404@huawei.com> (raw)
In-Reply-To: <20151220002526.GA27082@dustball.brq.redhat.com>

于 2015/12/20 8:25, Jan Stancek 写道:
> On Sat, Dec 19, 2015 at 11:04:21AM +0800, xiakaixu wrote:
>>
>>>>>    ...
>>>
>>> Hi,
>>>
>>> What is your objdump version?
>>
>> Hi,
>>
>> Sorry for the late reply.
>>
>> # objdump --version
>> GNU objdump (GNU Binutils) 2.25.
>>
>> I am sure that the system is Little endian.
>>>
> 
> I have attached a patch if you care to try it with your setup.
> If it still fails, output from -v and last objdump command output
> would be helpful.

Hi,

After applying this patch, the perf test case passed.

# perf test 21
21: Test object code reading                                 : (no vmlinux) Ok

Thanks!
> 
> Regards,
> Jan
> 


-- 
Regards
Kaixu Xia


  reply	other threads:[~2015-12-21  2:20 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-12-17 11:41 [BUG] perf test 21("Test object code reading") failure on ARM64 xiakaixu
2015-12-17 12:09 ` Jiri Olsa
2015-12-17 12:24   ` Jan Stancek
2015-12-19  3:04     ` xiakaixu
2015-12-20  0:25       ` Jan Stancek
2015-12-21  2:18         ` xiakaixu [this message]
2016-01-07 16:27           ` Arnaldo Carvalho de Melo
2016-01-08  8:03             ` Jan Stancek
2016-01-08 12:52               ` Arnaldo Carvalho de Melo

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=5677616C.2060404@huawei.com \
    --to=xiakaixu@huawei.com \
    --cc=acme@kernel.org \
    --cc=adrian.hunter@intel.com \
    --cc=jolsa@redhat.com \
    --cc=jstancek@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=masami.hiramatsu.pt@hitachi.com \
    --cc=mingo@kernel.org \
    --cc=wangnan0@huawei.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.