> On Mon, Mar 30, 2015 at 10:11:00AM +0200, David Hildenbrand wrote:
> > Commit 2e77784bb7d8 ("perf callchain: Move cpumode resolve code to
> > add_callchain_ip") promised "No change in behavior.".
> >
> > As this commit breaks callchains on s390x (symbols not getting resolved,
>
> I think it's
On Mon, Mar 30, 2015 at 10:11:00AM +0200, David Hildenbrand wrote:
> Commit 2e77784bb7d8 ("perf callchain: Move cpumode resolve code to
> add_callchain_ip") promised "No change in behavior.".
>
> As this commit breaks callchains on s390x (symbols not getting resolved,
I think it's a generic
Commit 2e77784bb7d8 ("perf callchain: Move cpumode resolve code to
add_callchain_ip") promised "No change in behavior.".
As this commit breaks callchains on s390x (symbols not getting resolved,
observed when profiling the kernel), this statement is wrong. The cpumode
must be kept when iterating
Commit 2e77784bb7d8 (perf callchain: Move cpumode resolve code to
add_callchain_ip) promised No change in behavior..
As this commit breaks callchains on s390x (symbols not getting resolved,
observed when profiling the kernel), this statement is wrong. The cpumode
must be kept when iterating over
On Mon, Mar 30, 2015 at 10:11:00AM +0200, David Hildenbrand wrote:
Commit 2e77784bb7d8 (perf callchain: Move cpumode resolve code to
add_callchain_ip) promised No change in behavior..
As this commit breaks callchains on s390x (symbols not getting resolved,
I think it's a generic problem not
On Mon, Mar 30, 2015 at 10:11:00AM +0200, David Hildenbrand wrote:
Commit 2e77784bb7d8 (perf callchain: Move cpumode resolve code to
add_callchain_ip) promised No change in behavior..
As this commit breaks callchains on s390x (symbols not getting resolved,
I think it's a generic
6 matches
Mail list logo