Em Wed, Mar 02, 2016 at 07:36:59AM +0100, Jiri Olsa escreveu:
> On Tue, Mar 01, 2016 at 03:32:37PM -0800, Andi Kleen wrote:
> > From: Andi Kleen
> >
> > Bug fix:
> >
> > The earlier metrics changes broke --per-thread causing a segfault.
> > Handle this case correctly. We
Em Wed, Mar 02, 2016 at 07:36:59AM +0100, Jiri Olsa escreveu:
> On Tue, Mar 01, 2016 at 03:32:37PM -0800, Andi Kleen wrote:
> > From: Andi Kleen
> >
> > Bug fix:
> >
> > The earlier metrics changes broke --per-thread causing a segfault.
> > Handle this case correctly. We actually don't print
On Tue, Mar 01, 2016 at 03:32:37PM -0800, Andi Kleen wrote:
> From: Andi Kleen
>
> Bug fix:
>
> The earlier metrics changes broke --per-thread causing a segfault.
> Handle this case correctly. We actually don't print metrics
> in per thread mode, so using a 0 shadow CPU is
On Tue, Mar 01, 2016 at 03:32:37PM -0800, Andi Kleen wrote:
> From: Andi Kleen
>
> Bug fix:
>
> The earlier metrics changes broke --per-thread causing a segfault.
> Handle this case correctly. We actually don't print metrics
> in per thread mode, so using a 0 shadow CPU is fine.
right, so
From: Andi Kleen
Bug fix:
The earlier metrics changes broke --per-thread causing a segfault.
Handle this case correctly. We actually don't print metrics
in per thread mode, so using a 0 shadow CPU is fine.
Could be folded into
"perf, tools, stat: Support metrics in
From: Andi Kleen
Bug fix:
The earlier metrics changes broke --per-thread causing a segfault.
Handle this case correctly. We actually don't print metrics
in per thread mode, so using a 0 shadow CPU is fine.
Could be folded into
"perf, tools, stat: Support metrics in --per-core/socket mode"
6 matches
Mail list logo