From: Arnaldo Carvalho de Melo <acme@kernel.org>
To: xiakaixu <xiakaixu@huawei.com>
Cc: Jan Stancek <jstancek@redhat.com>, Jiri Olsa <jolsa@redhat.com>,
adrian hunter <adrian.hunter@intel.com>,
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: Thu, 7 Jan 2016 13:27:21 -0300 [thread overview]
Message-ID: <20160107162721.GD18457@kernel.org> (raw)
In-Reply-To: <5677616C.2060404@huawei.com>
Em Mon, Dec 21, 2015 at 10:18:20AM +0800, xiakaixu escreveu:
> 于 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
So, assuming this doesn't break other running the test in other arches,
can Jan please resend this with a changelog and a Tested-by: Xia?
Was that done already? /me still digging thru my queue after last month
vacations...
- Arnaldo
> Thanks!
> >
> > Regards,
> > Jan
> >
>
>
> --
> Regards
> Kaixu Xia
next prev parent reply other threads:[~2016-01-07 16:27 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
2016-01-07 16:27 ` Arnaldo Carvalho de Melo [this message]
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=20160107162721.GD18457@kernel.org \
--to=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 \
--cc=xiakaixu@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 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).