Hello Kan and Andi,
On 14.09.2018 17:57, linux-kernel-ow...@vger.kernel.org wrote:
>
>
> On 9/14/2018 10:27 AM, Andi Kleen wrote:
>> On Fri, Sep 14, 2018 at 08:39:36AM -0400, Liang, Kan wrote:
>>>
>>>
>>> On 9/14/2018 5:22 AM, Alexey Budankov wrote:
Hi Andi,
On 14.09.2018 11:
On 9/14/2018 10:27 AM, Andi Kleen wrote:
On Fri, Sep 14, 2018 at 08:39:36AM -0400, Liang, Kan wrote:
On 9/14/2018 5:22 AM, Alexey Budankov wrote:
Hi Andi,
On 14.09.2018 11:54, Andi Kleen wrote:
In principle the LBRs need to be flushed between threads. So does
current code.
IMHO, ideal
On Fri, Sep 14, 2018 at 08:39:36AM -0400, Liang, Kan wrote:
>
>
> On 9/14/2018 5:22 AM, Alexey Budankov wrote:
> >
> > Hi Andi,
> >
> > On 14.09.2018 11:54, Andi Kleen wrote:
> > > > > In principle the LBRs need to be flushed between threads. So does
> > > > > current code.
> > > >
> > > > IMH
On 9/14/2018 5:22 AM, Alexey Budankov wrote:
Hi Andi,
On 14.09.2018 11:54, Andi Kleen wrote:
In principle the LBRs need to be flushed between threads. So does
current code.
IMHO, ideally, LBRs stack would be preserved and restored when
switching between execution stacks. That would allow
Hi Andi,
On 14.09.2018 11:54, Andi Kleen wrote:
>>> In principle the LBRs need to be flushed between threads. So does
>>> current code.
>>
>> IMHO, ideally, LBRs stack would be preserved and restored when
>> switching between execution stacks. That would allow implementing
>> per-thread statis
> > In principle the LBRs need to be flushed between threads. So does
> > current code.
>
> IMHO, ideally, LBRs stack would be preserved and restored when
> switching between execution stacks. That would allow implementing
> per-thread statistical call graph view in Perf tools, fully based
> on
Hi,
On 13.09.2018 23:08, linux-kernel-ow...@vger.kernel.org wrote:
> From: Kan Liang
>
> LBR can bring big overhead when the benchmark has high context switches.
> For example, a sub benchmark of Dacapo, avrora.
>
> Baseline: java -jar dacapo-9.12-MR1-bach.jar avrora -n 20
> With LBR: perf reco
From: Kan Liang
LBR can bring big overhead when the benchmark has high context switches.
For example, a sub benchmark of Dacapo, avrora.
Baseline: java -jar dacapo-9.12-MR1-bach.jar avrora -n 20
With LBR: perf record --branch-filter any,u -- java -jar
dacapo-9.12-MR1-bach.jar avrora -n 20
Basel
8 matches
Mail list logo