Re: [PATCH V7 11/17] perf, core: expose LBR call stack to user perf tool

2014-11-05 Thread Peter Zijlstra
On Tue, Nov 04, 2014 at 09:56:07PM -0500, Kan Liang wrote: > From: Yan, Zheng Now for this patch I'm fairly sure Zheng didn't actually write it; his last posting did something different IIRC. > With LBR call stack feature enable, there are two call chain data _three_, LBR is the 3rd. >

Re: [PATCH V7 11/17] perf, core: expose LBR call stack to user perf tool

2014-11-05 Thread Peter Zijlstra
On Tue, Nov 04, 2014 at 09:56:07PM -0500, Kan Liang wrote: From: Yan, Zheng zheng.z@intel.com Now for this patch I'm fairly sure Zheng didn't actually write it; his last posting did something different IIRC. With LBR call stack feature enable, there are two call chain data _three_, LBR is

[PATCH V7 11/17] perf, core: expose LBR call stack to user perf tool

2014-11-04 Thread Kan Liang
From: Yan, Zheng With LBR call stack feature enable, there are two call chain data sources, traditional frame pointer and LBR call stack. This patch extends the perf_callchain_entry struct to mark the available call chain source. The frame pointer is still output as PERF_SAMPLE_CALLCHAIN data

[PATCH V7 11/17] perf, core: expose LBR call stack to user perf tool

2014-11-04 Thread Kan Liang
From: Yan, Zheng zheng.z@intel.com With LBR call stack feature enable, there are two call chain data sources, traditional frame pointer and LBR call stack. This patch extends the perf_callchain_entry struct to mark the available call chain source. The frame pointer is still output as