[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20150903163706.GF11521@kernel.org>
Date: Thu, 3 Sep 2015 13:37:06 -0300
From: Arnaldo Carvalho de Melo <acme@...nel.org>
To: Jan Stancek <jstancek@...hat.com>
Cc: Adrian Hunter <adrian.hunter@...el.com>,
linux-kernel@...r.kernel.org, jolsa@...nel.org, dsahern@...il.com,
cjashfor@...ux.vnet.ibm.com, fweisbec@...il.com, mingo@...nel.org,
namhyung@...nel.org, paulus@...ba.org, a.p.zijlstra@...llo.nl
Subject: Re: [PATCH v3 2/4] perf tests: make objdump disassemble zero blocks
Em Thu, Sep 03, 2015 at 06:19:04PM +0200, Jan Stancek escreveu:
> On 09/03/2015 05:14 PM, Arnaldo Carvalho de Melo wrote:
> > Em Thu, Sep 03, 2015 at 02:35:55PM +0300, Adrian Hunter escreveu:
> >> On 03/09/15 14:23, Jan Stancek wrote:
> >>> Add -z parameter to avoid skipping zero blocks:
> >>>
> >>> ffffffff816704fe <sysret_check+0x4b>:
> >>> ffffffff816704fe: 7b 34 jnp ffffffff81670534 <sysret_signal+0x1c>
> >>> ...
> >>> ffffffff81670501 <sysret_careful>:
> >>> ffffffff81670501: 0f ba e2 03 bt $0x3,%edx
> >>> ffffffff81670505: 73 11 jae ffffffff81670518 <sysret_signal>
> >>
> >> Acked-by: Adrian Hunter <adrian.hunter@...el.com>
> >
> > Ok, I am applying this, but it would be nice to know in which systems,
> > with which objdump/binutils versions which 'perf test' entry fails, with
> > the output of such failure.
> >
> > Jan, can you please provide this info?
>
> Since my original report last year [1], I've seen it fail many times on
Ok, so it is a longstanding bug and now I have some tool output where it
fails to complement what was in these two patches, thanks, I'll update
it and put it on my next perf/urgent pull request to upstream.
- Arnaldo
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists