perf, x86: Haswell LBR call stack support
Subsystems (2)
v7 cover perf, x86: Haswell LBR call stack support
For many profiling tasks we need the callgraph. For example we often need to see the caller of a lock or the caller of a memcpy or other library function to actually tune the program. Frame pointer unwinding is efficient and works well. But frame pointers are off by default on 64bit code (and on modern 32bit gccs), so there are many binaries around that do not use frame pointers. Profiling unchanged production code is very useful in practice. On some CPUs frame pointer also has a high cost. Dwarf2 unwinding also does not always work and is extremely slow (upto 20% overhead).
Haswell has a new feature that utilizes the existing Last Branch Record facility to record call chains. When the feature is enabled, function call will be collected as normal, but as return instructions are executed the last captured branch record is popped from the on-chip LBR registers. The LBR call stack facility provides an alternative to get callgraph. It has some limitations too, but should work in most cases and is significantly faster than dwarf. Frame pointer unwinding is still the best default, but LBR call stack is a good alternative when nothing else works.
In the implementation, both Frame pointer and LBR call stack data are collected by kernel, and expose to user space. The frame pointer is still output as PERF_SAMPLE_CALLCHAIN data format. The LBR call stack data will be output as PERF_SAMPLE_BRANCH_STACK data format. a callahain source extension of perf report call-graph option is introduced. So user can choose call chain from either FP or LBR call stack.
When profiling bc(1) on Fedora 19:
echo 'scale=2000; 4*a(1)' > cmd; perf record --call-graph fp bc -l < cmd If this feature is enabled, perf report with lbr output looks like:
50.36% bc bc [.] bc_divide
|
--- bc_divide
execute
run_code
yyparse
main
__libc_start_main
_start
33.66% bc bc [.] _one_mult
|
--- _one_mult
bc_divide
execute
run_code
yyparse
main
__libc_start_main
_start
7.62% bc bc [.] _bc_do_add
|
--- _bc_do_add
|
|--99.89%-- 0x2000186a8
--0.11%-- [...]
6.83% bc bc [.] _bc_do_sub
|
--- _bc_do_sub
|
|--99.94%-- bc_add
| execute
| run_code
| yyparse
| main
| __libc_start_main
| _start
--0.06%-- [...]
0.46% bc libc-2.17.so [.] __memset_sse2
|
--- __memset_sse2
|
|--54.13%-- bc_new_num
| |
| |--51.00%-- bc_divide
| | execute
| | run_code
| | yyparse
| | main
| | __libc_start_main
| | _start
| |
| |--30.46%-- _bc_do_sub
| | bc_add
| | execute
| | run_code
| | yyparse
| | main
| | __libc_start_main
| | _start
| |
| --18.55%-- _bc_do_add
| bc_add
| execute
| run_code
| yyparse
| main
| __libc_start_main
| _start
|
--45.87%-- bc_divide
execute
run_code
yyparse
main
__libc_start_main
_start
If this feature is disabled, perf report output looks like:
50.49% bc bc [.] bc_divide
|
--- bc_divide
33.57% bc bc [.] _one_mult
|
--- _one_mult
7.61% bc bc [.] _bc_do_add
|
--- _bc_do_add
0x2000186a8
6.88% bc bc [.] _bc_do_sub
|
--- _bc_do_sub
0.42% bc libc-2.17.so [.] __memcpy_ssse3_back
|
--- __memcpy_ssse3_backAnother example is to demo the extension of perf report.
If both fp and lbr are available, we can dump either them by fp or lbr option as below.
$ perf record --call-graph fp ./a.out [ perf record: Woken up 18 times to write data ] [ perf record: Captured and wrote 4.322 MB perf.data (~188824 samples) ]
$ perf report --call-graph fractal,0.5,callee,function,fp -D | wc -l 605688 $ perf report --call-graph fractal,0.5,callee,function,lbr -D | wc -l 605730
The LBR call stack has following known limitations
- Zero length calls are not filtered out by hardware
- Exception handing such as setjmp/longjmp will have calls/returns not match
- Pushing different return address onto the stack will have calls/returns not match
- If callstack is deeper than the LBR, only the last entries are captured
Changes since v1
- split change into more patches
- introduce context switch callback and use it to flush LBR
- use the context switch callback to save/restore LBR
- dynamic allocate memory area for storing LBR stack, always switch the memory area during context switch
- disable this feature by default
- more description in change logs
Changes since v2
- don't use xchg to switch PMU specific data
- remove nr_branch_stack from struct perf_event_context
- simplify the save/restore LBR stack logical
- remove unnecessary 'has_branch_stack -> needs_branch_stack' conversion
- more description in change logs
Changes since v3
- remove sysfs attribute file that disable this feature
Changes since v4
- re-organize code that save/resotre LBR stack
- allocate pmu specific data when it's needed
- update code comments
Changes since v5
- Expose LBR call stack data to user perf tool
- Add option for perf report to support LBR call stack
- Some minor changes according to comments
Changes since v6
- rebase on tip.git 05066a2a04
- Modify perf test accordingly
Yan, Zheng (15):
perf, x86: Reduce lbr_sel_map size
perf, core: introduce pmu context switch callback
perf, x86: use context switch callback to flush LBR stack perf, x86: Basic Haswell LBR call stack support
perf, core: pmu specific data for perf task context
perf, core: always switch pmu specific data during context switch perf, x86: allocate space for storing LBR stack
perf, x86: track number of events that use LBR callstack perf, x86: Save/resotre LBR stack during context switch perf, core: simplify need branch stack check
perf, core: expose LBR call stack to user perf tool
perf, x86: re-organize code that implicitly enables LBR/PEBS perf, x86: enable LBR callstack when recording callchain perf, x86: disable FREEZE_LBRS_ON_PMI when LBR operates in callstack
mode
perf, x86: Discard zero length call entries in LBR call stack
Kan Liang (2):
perf tools: handle LBR call stack data
perf tools: choose to dump callchain from LBR and FP
arch/x86/kernel/cpu/perf_event.c | 90 ++++++--- arch/x86/kernel/cpu/perf_event.h | 28 ++- arch/x86/kernel/cpu/perf_event_intel.c | 38 +--- arch/x86/kernel/cpu/perf_event_intel_ds.c | 2 +- arch/x86/kernel/cpu/perf_event_intel_lbr.c | 309 ++++++++++++++++++++++------- include/linux/perf_event.h | 35 +++- include/uapi/linux/perf_event.h | 49 +++-- kernel/events/callchain.c | 1 + kernel/events/core.c | 200 +++++++++++-------- tools/perf/builtin-report.c | 8 +- tools/perf/tests/hists_cumulate.c | 20 +- tools/perf/tests/sample-parsing.c | 2 +- tools/perf/util/callchain.c | 18 +- tools/perf/util/callchain.h | 6 + tools/perf/util/event.h | 8 + tools/perf/util/evsel.c | 21 +- tools/perf/util/machine.c | 198 ++++++++++++------ tools/perf/util/session.c | 34 +++- 18 files changed, 742 insertions(+), 325 deletions(-)
Signature · 1 line
1.8.3.2
PATCH v7 1/17 perf, x86: Reduce lbr_sel_map size
From: Yan, Zheng <[email protected]>
The index of lbr_sel_map is bit value of perf branch_sample_type. PERF_SAMPLE_BRANCH_MAX is 1024 at present, so each lbr_sel_map uses 4096 bytes. By using bit shift as index, we can reduce lbr_sel_map size to 40 bytes. This patch defines 'bit shift' for branch types, and use 'bit shift' to define lbr_sel_maps.
--- arch/x86/kernel/cpu/perf_event.h | 4 +++ arch/x86/kernel/cpu/perf_event_intel_lbr.c | 54 ++++++++++++++---------------- include/uapi/linux/perf_event.h | 49 +++++++++++++++++++-------- 3 files changed, 64 insertions(+), 43 deletions(-)
arch/x86/kernel/cpu/perf_event.h +4 -0
@@ -509,6 +509,10 @@ struct x86_pmu {struct perf_guest_switch_msr *(*guest_get_msrs)(int *nr); }; +enum { +PERF_SAMPLE_BRANCH_SELECT_MAP_SIZE =PERF_SAMPLE_BRANCH_MAX_SHIFT , +}; +#define x86_add_quirk (func_) \ do { \ static struct x86_pmu_quirk __quirk __initdata = { \
arch/x86/kernel/cpu/perf_event_intel_lbr.c +25 -29
84 lines not on this page · raw message
include/uapi/linux/perf_event.h +35 -14
56 lines not on this page · raw message
Signature · 1 line
1.8.3.2
tip-bot for Yan, Zheng
merge bot[tip:perf/core] perf/x86/intel: Reduce lbr_sel_map[] size
perf/x86/intel: Reduce lbr_sel_map[] size
Commit-ID: 27ac905b8f88d28779b0661809286b5ba2817d37 Gitweb: http://git.kernel.org/tip/27ac905b8f88d28779b0661809286b5ba2817d37 Author: Yan, Zheng <[email protected]> AuthorDate: Tue, 4 Nov 2014 21:55:57 -0500 Committer: Ingo Molnar <[email protected]> CommitDate: Wed, 18 Feb 2015 17:16:01 +0100
perf/x86/intel: Reduce lbr_sel_map[] size
The index of lbr_sel_map is bit value of perf branch_sample_type. PERF_SAMPLE_BRANCH_MAX is 1024 at present, so each lbr_sel_map uses 4096 bytes. By using bit shift as index, we can reduce lbr_sel_map size to 40 bytes. This patch defines 'bit shift' for branch types, and use 'bit shift' to define lbr_sel_maps.
--- arch/x86/kernel/cpu/perf_event.h | 4 +++ arch/x86/kernel/cpu/perf_event_intel_lbr.c | 54 ++++++++++++++---------------- include/uapi/linux/perf_event.h | 49 +++++++++++++++++++-------- 3 files changed, 64 insertions(+), 43 deletions(-)
arch/x86/kernel/cpu/perf_event.h +4 -0
@@ -515,6 +515,10 @@ struct x86_pmu {struct perf_guest_switch_msr *(*guest_get_msrs)(int *nr); }; +enum { +PERF_SAMPLE_BRANCH_SELECT_MAP_SIZE =PERF_SAMPLE_BRANCH_MAX_SHIFT , +}; +#define x86_add_quirk (func_) \ do { \ static struct x86_pmu_quirk __quirk __initdata = { \
arch/x86/kernel/cpu/perf_event_intel_lbr.c +25 -29
84 lines not on this page · raw message
include/uapi/linux/perf_event.h +35 -14
56 lines not on this page · raw message
PATCH v7 2/17 perf, core: introduce pmu context switch callback
In reply to Kan LiangFrom: Yan, Zheng <[email protected]>
The callback is invoked when process is scheduled in or out. It provides mechanism for later patches to save/store the LBR stack. For the schedule in case, the callback is invoked at the same place that flush branch stack callback is invoked. So it also can replace the flush branch stack callback. To avoid unnecessary overhead, the callback is enabled only when there are events use the LBR stack.
--- arch/x86/kernel/cpu/perf_event.c | 7 +++++ arch/x86/kernel/cpu/perf_event.h | 2 ++ include/linux/perf_event.h | 9 +++++++ kernel/events/core.c | 57 ++++++++++++++++++++++++++++++++++++++++ 4 files changed, 75 insertions(+)
arch/x86/kernel/cpu/perf_event.c +7 -0
@@ -1879,6 +1879,12 @@ static const struct attribute_group *x86_pmu_attr_groups[] = { NULL, }; +static void x86_pmu_sched_task (struct perf_event_context *ctx,bool sched_in) +{ +if (x86_pmu.sched_task) + x86_pmu.sched_task (ctx, sched_in); +} +static void x86_pmu_flush_branch_stack (void ) {if (x86_pmu.flush_branch_stack)
@@ -1912,6 +1918,7 @@ static struct pmu pmu = { .event_idx = x86_pmu_event_idx, .flush_branch_stack = x86_pmu_flush_branch_stack, + .sched_task = x86_pmu_sched_task, };void arch_perf_update_userpage (struct perf_event_mmap_page *userpg,u64 now)
arch/x86/kernel/cpu/perf_event.h +2 -0
@@ -467,6 +467,8 @@ struct x86_pmu {void (*check_microcode)(void );void (*flush_branch_stack)(void ); +void (*sched_task)(struct perf_event_context *ctx, +bool sched_in);/* * Intel Arch Perfmon v2+
include/linux/perf_event.h +9 -0
@@ -263,6 +263,13 @@ struct pmu {* flush branch stack on context-switches (needed in cpu-wide mode) */ void (*flush_branch_stack) (void ); + +/* +* context-switches callback +*/ +void (*sched_task) (struct perf_event_context *ctx, +bool sched_in); + };/**
@@ -562,6 +569,8 @@ extern void perf_event_delayed_put(struct task_struct *task);extern void perf_event_print_debug (void );extern void perf_pmu_disable (struct pmu *pmu);extern void perf_pmu_enable (struct pmu *pmu); +extern void perf_sched_cb_dec (struct pmu *pmu); +extern void perf_sched_cb_inc (struct pmu *pmu);extern int perf_event_task_disable (void );extern int perf_event_task_enable (void );extern int perf_event_refresh (struct perf_event *event,int refresh);
kernel/events/core.c +57 -0
81 lines not on this page · raw message
Signature · 1 line
1.8.3.2
tip-bot for Yan, Zheng
merge bot[tip:perf/core] perf: Introduce pmu context switch callback
perf: Introduce pmu context switch callback
Commit-ID: ba532500c5651a4be4108acc64ed99a95cb005b3 Gitweb: http://git.kernel.org/tip/ba532500c5651a4be4108acc64ed99a95cb005b3 Author: Yan, Zheng <[email protected]> AuthorDate: Tue, 4 Nov 2014 21:55:58 -0500 Committer: Ingo Molnar <[email protected]> CommitDate: Wed, 18 Feb 2015 17:16:02 +0100
perf: Introduce pmu context switch callback
The callback is invoked when process is scheduled in or out. It provides mechanism for later patches to save/store the LBR stack. For the schedule in case, the callback is invoked at the same place that flush branch stack callback is invoked. So it also can replace the flush branch stack callback. To avoid unnecessary overhead, the callback is enabled only when there are events use the LBR stack.
--- arch/x86/kernel/cpu/perf_event.c | 7 +++++ arch/x86/kernel/cpu/perf_event.h | 2 ++ include/linux/perf_event.h | 9 +++++++ kernel/events/core.c | 57 ++++++++++++++++++++++++++++++++++++++++ 4 files changed, 75 insertions(+)
arch/x86/kernel/cpu/perf_event.c +7 -0
@@ -1914,6 +1914,12 @@ static const struct attribute_group *x86_pmu_attr_groups[] = { NULL, }; +static void x86_pmu_sched_task (struct perf_event_context *ctx,bool sched_in) +{ +if (x86_pmu.sched_task) + x86_pmu.sched_task (ctx, sched_in); +} +static void x86_pmu_flush_branch_stack (void ) {if (x86_pmu.flush_branch_stack)
@@ -1950,6 +1956,7 @@ static struct pmu pmu = { .event_idx = x86_pmu_event_idx, .flush_branch_stack = x86_pmu_flush_branch_stack, + .sched_task = x86_pmu_sched_task, }; void arch_perf_update_userpage(struct perf_event *event,
arch/x86/kernel/cpu/perf_event.h +2 -0
@@ -473,6 +473,8 @@ struct x86_pmu {void (*check_microcode)(void );void (*flush_branch_stack)(void ); +void (*sched_task)(struct perf_event_context *ctx, +bool sched_in);/* * Intel Arch Perfmon v2+
include/linux/perf_event.h +9 -0
@@ -265,6 +265,13 @@ struct pmu {* flush branch stack on context-switches (needed in cpu-wide mode) */ void (*flush_branch_stack) (void ); + +/* +* context-switches callback +*/ +void (*sched_task) (struct perf_event_context *ctx, +bool sched_in); + };/**
@@ -558,6 +565,8 @@ extern void perf_event_delayed_put(struct task_struct *task);extern void perf_event_print_debug (void );extern void perf_pmu_disable (struct pmu *pmu);extern void perf_pmu_enable (struct pmu *pmu); +extern void perf_sched_cb_dec (struct pmu *pmu); +extern void perf_sched_cb_inc (struct pmu *pmu);extern int perf_event_task_disable (void );extern int perf_event_task_enable (void );extern int perf_event_refresh (struct perf_event *event,int refresh);
kernel/events/core.c +57 -0
81 lines not on this page · raw message
PATCH v7 3/17 perf, x86: use context switch callback to flush LBR stack
In reply to Kan LiangFrom: Yan, Zheng <[email protected]>
Previous commit introduces context switch callback, its function overlaps with the flush branch stack callback. So we can use the context switch callback to flush LBR stack.
This patch adds code that uses the flush branch callback to flush the LBR stack when task is being scheduled in. The callback is enabled only when there are events use the LBR hardware. This patch also removes all old flush branch stack code.
--- arch/x86/kernel/cpu/perf_event.c | 7 --- arch/x86/kernel/cpu/perf_event.h | 3 +- arch/x86/kernel/cpu/perf_event_intel.c | 14 +----- arch/x86/kernel/cpu/perf_event_intel_lbr.c | 27 +++++++++++ include/linux/perf_event.h | 1 - kernel/events/core.c | 77 ------------------------------ 6 files changed, 30 insertions(+), 99 deletions(-)
arch/x86/kernel/cpu/perf_event.c +0 -7
@@ -1885,12 +1885,6 @@ static void x86_pmu_sched_task(struct perf_event_context *ctx, bool sched_in) x86_pmu.sched_task (ctx, sched_in); } -static void x86_pmu_flush_branch_stack (void ) -{ -if (x86_pmu.flush_branch_stack) - x86_pmu.flush_branch_stack (); -} -void perf_check_microcode (void ) {if (x86_pmu.check_microcode)
@@ -1917,7 +1911,6 @@ static struct pmu pmu = { .commit_txn = x86_pmu_commit_txn, .event_idx = x86_pmu_event_idx, - .flush_branch_stack = x86_pmu_flush_branch_stack, .sched_task = x86_pmu_sched_task, };
arch/x86/kernel/cpu/perf_event.h +2 -1
@@ -466,7 +466,6 @@ struct x86_pmu {void (*cpu_dead)(int cpu);void (*check_microcode)(void ); -void (*flush_branch_stack)(void );void (*sched_task)(struct perf_event_context *ctx,bool sched_in);
@@ -727,6 +726,8 @@ void intel_pmu_pebs_disable_all(void);void intel_ds_init (void ); +void intel_pmu_lbr_sched_task (struct perf_event_context *ctx,bool sched_in); +void intel_pmu_lbr_reset (void );void intel_pmu_lbr_enable (struct perf_event *event);
arch/x86/kernel/cpu/perf_event_intel.c +1 -13
@@ -2044,18 +2044,6 @@ static void intel_pmu_cpu_dying(int cpu)fini_debug_store_on_cpu (cpu); } -static void intel_pmu_flush_branch_stack (void ) -{ -/* -* Intel LBR does not tag entries with the -* PID of the current task, then we need to -* flush it on ctxsw -* For now, we simply reset it -*/ -if (x86_pmu.lbr_nr) -intel_pmu_lbr_reset (); -} -PMU_FORMAT_ATTR (offcore_rsp,"config1:0-63" );PMU_FORMAT_ATTR (ldlat,"config1:0-15" );
@@ -2107,7 +2095,7 @@ static __initconst const struct x86_pmu intel_pmu = { .cpu_starting = intel_pmu_cpu_starting, .cpu_dying = intel_pmu_cpu_dying, .guest_get_msrs = intel_guest_get_msrs, - .flush_branch_stack = intel_pmu_flush_branch_stack, + .sched_task = intel_pmu_lbr_sched_task, };static __init void intel_clovertown_quirk (void )
arch/x86/kernel/cpu/perf_event_intel_lbr.c +27 -0
@@ -177,6 +177,31 @@ void intel_pmu_lbr_reset(void)intel_pmu_lbr_reset_64 (); } +void intel_pmu_lbr_sched_task (struct perf_event_context *ctx,bool sched_in) +{ +struct cpu_hw_events *cpuc =this_cpu_ptr (&cpu_hw_events); + +if (!x86_pmu.lbr_nr) +return ; + +/* +* When sampling the branck stack in system-wide, it may be +* necessary to flush the stack on context switch. This happens +* when the branch stack does not tag its entries with the pid +* of the current task. Otherwise it becomes impossible to +* associate a branch entry with a task. This ambiguity is more +* likely to appear when the branch stack supports priv level +* filtering and the user sets it to monitor only at the user +* level (which could be a useful measurement in system-wide +* mode). In that case, the risk is high of having a branch +* stack with branch from multiple tasks. +*/ +if (sched_in) { +intel_pmu_lbr_reset (); + cpuc->lbr_context = ctx; + } +} +void intel_pmu_lbr_enable (struct perf_event *event) {struct cpu_hw_events *cpuc =this_cpu_ptr (&cpu_hw_events);
@@ -195,6 +220,7 @@ void intel_pmu_lbr_enable(struct perf_event *event) cpuc->br_sel = event->hw.branch_reg.reg; cpuc->lbr_users++; +perf_sched_cb_inc (event->ctx->pmu); }void intel_pmu_lbr_disable (struct perf_event *event)
@@ -206,6 +232,7 @@ void intel_pmu_lbr_disable(struct perf_event *event) cpuc->lbr_users--;WARN_ON_ONCE (cpuc->lbr_users <0 ); +perf_sched_cb_dec (event->ctx->pmu);if (cpuc->enabled && !cpuc->lbr_users) {__intel_pmu_lbr_disable ();
include/linux/perf_event.h +0 -1
@@ -514,7 +514,6 @@ struct perf_event_context {u64 generation;int pin_count;int nr_cgroups;/* cgroup evts */ -int nr_branch_stack;/* branch_stack evt */ struct rcu_head rcu_head;struct delayed_work orphans_remove;
kernel/events/core.c +0 -77
119 lines not on this page · raw message
Signature · 1 line
1.8.3.2
tip-bot for Yan, Zheng
merge bot[tip:perf/core] perf/x86/intel: Use context switch callback to flush LBR stack
perf/x86/intel: Use context switch callback to flush LBR stack
Commit-ID: 2a0ad3b326a9024ba86dca4028499d31fa0c6c4d Gitweb: http://git.kernel.org/tip/2a0ad3b326a9024ba86dca4028499d31fa0c6c4d Author: Yan, Zheng <[email protected]> AuthorDate: Tue, 4 Nov 2014 21:55:59 -0500 Committer: Ingo Molnar <[email protected]> CommitDate: Wed, 18 Feb 2015 17:16:03 +0100
perf/x86/intel: Use context switch callback to flush LBR stack
Previous commit introduces context switch callback, its function overlaps with the flush branch stack callback. So we can use the context switch callback to flush LBR stack.
This patch adds code that uses the flush branch callback to flush the LBR stack when task is being scheduled in. The callback is enabled only when there are events use the LBR hardware. This patch also removes all old flush branch stack code.
--- arch/x86/kernel/cpu/perf_event.c | 7 --- arch/x86/kernel/cpu/perf_event.h | 3 +- arch/x86/kernel/cpu/perf_event_intel.c | 14 +----- arch/x86/kernel/cpu/perf_event_intel_lbr.c | 27 +++++++++++ include/linux/perf_event.h | 1 - kernel/events/core.c | 77 ------------------------------ 6 files changed, 30 insertions(+), 99 deletions(-)
arch/x86/kernel/cpu/perf_event.c +0 -7
@@ -1920,12 +1920,6 @@ static void x86_pmu_sched_task(struct perf_event_context *ctx, bool sched_in) x86_pmu.sched_task (ctx, sched_in); } -static void x86_pmu_flush_branch_stack (void ) -{ -if (x86_pmu.flush_branch_stack) - x86_pmu.flush_branch_stack (); -} -void perf_check_microcode (void ) {if (x86_pmu.check_microcode)
@@ -1955,7 +1949,6 @@ static struct pmu pmu = { .commit_txn = x86_pmu_commit_txn, .event_idx = x86_pmu_event_idx, - .flush_branch_stack = x86_pmu_flush_branch_stack, .sched_task = x86_pmu_sched_task, };
arch/x86/kernel/cpu/perf_event.h +2 -1
@@ -472,7 +472,6 @@ struct x86_pmu {void (*cpu_dead)(int cpu);void (*check_microcode)(void ); -void (*flush_branch_stack)(void );void (*sched_task)(struct perf_event_context *ctx,bool sched_in);
@@ -733,6 +732,8 @@ void intel_pmu_pebs_disable_all(void);void intel_ds_init (void ); +void intel_pmu_lbr_sched_task (struct perf_event_context *ctx,bool sched_in); +void intel_pmu_lbr_reset (void );void intel_pmu_lbr_enable (struct perf_event *event);
arch/x86/kernel/cpu/perf_event_intel.c +1 -13
@@ -2044,18 +2044,6 @@ static void intel_pmu_cpu_dying(int cpu)fini_debug_store_on_cpu (cpu); } -static void intel_pmu_flush_branch_stack (void ) -{ -/* -* Intel LBR does not tag entries with the -* PID of the current task, then we need to -* flush it on ctxsw -* For now, we simply reset it -*/ -if (x86_pmu.lbr_nr) -intel_pmu_lbr_reset (); -} -PMU_FORMAT_ATTR (offcore_rsp,"config1:0-63" );PMU_FORMAT_ATTR (ldlat,"config1:0-15" );
@@ -2107,7 +2095,7 @@ static __initconst const struct x86_pmu intel_pmu = { .cpu_starting = intel_pmu_cpu_starting, .cpu_dying = intel_pmu_cpu_dying, .guest_get_msrs = intel_guest_get_msrs, - .flush_branch_stack = intel_pmu_flush_branch_stack, + .sched_task = intel_pmu_lbr_sched_task, };static __init void intel_clovertown_quirk (void )
arch/x86/kernel/cpu/perf_event_intel_lbr.c +27 -0
@@ -177,6 +177,31 @@ void intel_pmu_lbr_reset(void)intel_pmu_lbr_reset_64 (); } +void intel_pmu_lbr_sched_task (struct perf_event_context *ctx,bool sched_in) +{ +struct cpu_hw_events *cpuc =this_cpu_ptr (&cpu_hw_events); + +if (!x86_pmu.lbr_nr) +return ; + +/* +* When sampling the branck stack in system-wide, it may be +* necessary to flush the stack on context switch. This happens +* when the branch stack does not tag its entries with the pid +* of the current task. Otherwise it becomes impossible to +* associate a branch entry with a task. This ambiguity is more +* likely to appear when the branch stack supports priv level +* filtering and the user sets it to monitor only at the user +* level (which could be a useful measurement in system-wide +* mode). In that case, the risk is high of having a branch +* stack with branch from multiple tasks. +*/ +if (sched_in) { +intel_pmu_lbr_reset (); + cpuc->lbr_context = ctx; + } +} +void intel_pmu_lbr_enable (struct perf_event *event) {struct cpu_hw_events *cpuc =this_cpu_ptr (&cpu_hw_events);
@@ -195,6 +220,7 @@ void intel_pmu_lbr_enable(struct perf_event *event) cpuc->br_sel = event->hw.branch_reg.reg; cpuc->lbr_users++; +perf_sched_cb_inc (event->ctx->pmu); }void intel_pmu_lbr_disable (struct perf_event *event)
@@ -206,6 +232,7 @@ void intel_pmu_lbr_disable(struct perf_event *event) cpuc->lbr_users--;WARN_ON_ONCE (cpuc->lbr_users <0 ); +perf_sched_cb_dec (event->ctx->pmu);if (cpuc->enabled && !cpuc->lbr_users) {__intel_pmu_lbr_disable ();
include/linux/perf_event.h +0 -1
@@ -511,7 +511,6 @@ struct perf_event_context {u64 generation;int pin_count;int nr_cgroups;/* cgroup evts */ -int nr_branch_stack;/* branch_stack evt */ struct rcu_head rcu_head;struct delayed_work orphans_remove;
kernel/events/core.c +0 -77
119 lines not on this page · raw message
PATCH v7 4/17 perf, x86: Basic Haswell LBR call stack support
In reply to Kan LiangFrom: Yan, Zheng <[email protected]>
Haswell has a new feature that utilizes the existing LBR facility to record call chains. To enable this feature, bits (JCC, NEAR_IND_JMP, NEAR_REL_JMP, FAR_BRANCH, EN_CALLSTACK) in LBR_SELECT must be set to 1, bits (NEAR_REL_CALL, NEAR-IND_CALL, NEAR_RET) must be cleared. Due to a hardware bug of Haswell, this feature doesn't work well with FREEZE_LBRS_ON_PMI.
When the call stack feature is enabled, the LBR stack will capture unfiltered call data normally, but as return instructions are executed, the last captured branch record is flushed from the on-chip registers in a last-in first-out (LIFO) manner. Thus, branch information relative to leaf functions will not be captured, while preserving the call stack information of the main line execution path.
This patch defines a separate lbr_sel map for Haswell. The map contains a new entry for the call stack feature.
--- arch/x86/kernel/cpu/perf_event.h | 14 ++++- arch/x86/kernel/cpu/perf_event_intel.c | 2 +- arch/x86/kernel/cpu/perf_event_intel_lbr.c | 91 ++++++++++++++++++++++-------- 3 files changed, 83 insertions(+), 24 deletions(-)
arch/x86/kernel/cpu/perf_event.h +13 -1
@@ -511,7 +511,11 @@ struct x86_pmu { };enum { -PERF_SAMPLE_BRANCH_SELECT_MAP_SIZE =PERF_SAMPLE_BRANCH_MAX_SHIFT , +PERF_SAMPLE_BRANCH_CALL_STACK_SHIFT =PERF_SAMPLE_BRANCH_MAX_SHIFT , +PERF_SAMPLE_BRANCH_SELECT_MAP_SIZE , + +PERF_SAMPLE_BRANCH_CALL_STACK = +1U <<PERF_SAMPLE_BRANCH_CALL_STACK_SHIFT , };#define x86_add_quirk (func_) \
@@ -545,6 +549,12 @@ static struct perf_pmu_events_attr event_attr_##v = { \extern struct x86_pmu x86_pmu__read_mostly ; +static inline bool x86_pmu_has_lbr_callstack (void ) +{ +return x86_pmu.lbr_sel_map && + x86_pmu.lbr_sel_map[PERF_SAMPLE_BRANCH_CALL_STACK_SHIFT ] >0 ; +} + DECLARE_PER_CPU(struct cpu_hw_events, cpu_hw_events);int x86_perf_event_set_period (struct perf_event *event);
@@ -748,6 +758,8 @@ void intel_pmu_lbr_init_atom(void);void intel_pmu_lbr_init_snb (void ); +void intel_pmu_lbr_init_hsw (void ); +int intel_pmu_setup_lbr_filter (struct perf_event *event);int p4_pmu_init (void );
arch/x86/kernel/cpu/perf_event_intel.c +1 -1
@@ -2536,7 +2536,7 @@ __init int intel_pmu_init(void)memcpy (hw_cache_event_ids, snb_hw_cache_event_ids,sizeof (hw_cache_event_ids));memcpy (hw_cache_extra_regs, snb_hw_cache_extra_regs,sizeof (hw_cache_extra_regs)); -intel_pmu_lbr_init_snb (); +intel_pmu_lbr_init_hsw (); x86_pmu.event_constraints = intel_hsw_event_constraints; x86_pmu.pebs_constraints = intel_hsw_pebs_event_constraints;
arch/x86/kernel/cpu/perf_event_intel_lbr.c +69 -22
150 lines not on this page · raw message
Signature · 1 line
1.8.3.2
tip-bot for Yan, Zheng
merge bot[tip:perf/core] perf/x86/intel: Add basic Haswell LBR call stack support
perf/x86/intel: Add basic Haswell LBR call stack support
Commit-ID: e9d7f7cd97c45e2c612d3b38be05b4cfb27939ee Gitweb: http://git.kernel.org/tip/e9d7f7cd97c45e2c612d3b38be05b4cfb27939ee Author: Yan, Zheng <[email protected]> AuthorDate: Tue, 4 Nov 2014 21:56:00 -0500 Committer: Ingo Molnar <[email protected]> CommitDate: Wed, 18 Feb 2015 17:16:04 +0100
perf/x86/intel: Add basic Haswell LBR call stack support
Haswell has a new feature that utilizes the existing LBR facility to record call chains. To enable this feature, bits (JCC, NEAR_IND_JMP, NEAR_REL_JMP, FAR_BRANCH, EN_CALLSTACK) in LBR_SELECT must be set to 1, bits (NEAR_REL_CALL, NEAR-IND_CALL, NEAR_RET) must be cleared. Due to a hardware bug of Haswell, this feature doesn't work well with FREEZE_LBRS_ON_PMI.
When the call stack feature is enabled, the LBR stack will capture unfiltered call data normally, but as return instructions are executed, the last captured branch record is flushed from the on-chip registers in a last-in first-out (LIFO) manner. Thus, branch information relative to leaf functions will not be captured, while preserving the call stack information of the main line execution path.
This patch defines a separate lbr_sel map for Haswell. The map contains a new entry for the call stack feature.
--- arch/x86/kernel/cpu/perf_event.h | 14 ++++- arch/x86/kernel/cpu/perf_event_intel.c | 2 +- arch/x86/kernel/cpu/perf_event_intel_lbr.c | 91 ++++++++++++++++++++++-------- 3 files changed, 83 insertions(+), 24 deletions(-)
arch/x86/kernel/cpu/perf_event.h +13 -1
@@ -517,7 +517,11 @@ struct x86_pmu { };enum { -PERF_SAMPLE_BRANCH_SELECT_MAP_SIZE =PERF_SAMPLE_BRANCH_MAX_SHIFT , +PERF_SAMPLE_BRANCH_CALL_STACK_SHIFT =PERF_SAMPLE_BRANCH_MAX_SHIFT , +PERF_SAMPLE_BRANCH_SELECT_MAP_SIZE , + +PERF_SAMPLE_BRANCH_CALL_STACK = +1U <<PERF_SAMPLE_BRANCH_CALL_STACK_SHIFT , };#define x86_add_quirk (func_) \
@@ -551,6 +555,12 @@ static struct perf_pmu_events_attr event_attr_##v = { \extern struct x86_pmu x86_pmu__read_mostly ; +static inline bool x86_pmu_has_lbr_callstack (void ) +{ +return x86_pmu.lbr_sel_map && + x86_pmu.lbr_sel_map[PERF_SAMPLE_BRANCH_CALL_STACK_SHIFT ] >0 ; +} + DECLARE_PER_CPU(struct cpu_hw_events, cpu_hw_events);int x86_perf_event_set_period (struct perf_event *event);
@@ -754,6 +764,8 @@ void intel_pmu_lbr_init_atom(void);void intel_pmu_lbr_init_snb (void ); +void intel_pmu_lbr_init_hsw (void ); +int intel_pmu_setup_lbr_filter (struct perf_event *event);int p4_pmu_init (void );
arch/x86/kernel/cpu/perf_event_intel.c +1 -1
@@ -2537,7 +2537,7 @@ __init int intel_pmu_init(void)memcpy (hw_cache_event_ids, snb_hw_cache_event_ids,sizeof (hw_cache_event_ids));memcpy (hw_cache_extra_regs, snb_hw_cache_extra_regs,sizeof (hw_cache_extra_regs)); -intel_pmu_lbr_init_snb (); +intel_pmu_lbr_init_hsw (); x86_pmu.event_constraints = intel_hsw_event_constraints; x86_pmu.pebs_constraints = intel_hsw_pebs_event_constraints;
arch/x86/kernel/cpu/perf_event_intel_lbr.c +69 -22
150 lines not on this page · raw message
PATCH v7 5/17 perf, core: pmu specific data for perf task context
In reply to Kan LiangFrom: Yan, Zheng <[email protected]>
Introduce a new flag PERF_ATTACH_TASK_DATA for perf event's attach stata. The flag is set by PMU's event_init() callback, it indicates that perf event needs PMU specific data.
The PMU specific data are initialized to zeros. Later patches will use PMU specific data to save LBR stack.
--- include/linux/perf_event.h | 6 ++++++ kernel/events/core.c | 40 ++++++++++++++++++++++++++++++++++++---- 2 files changed, 42 insertions(+), 4 deletions(-)
include/linux/perf_event.h +6 -0
@@ -269,6 +269,10 @@ struct pmu {*/ void (*sched_task) (struct perf_event_context *ctx,bool sched_in); +/* +* PMU specific data size +*/ +size_t task_ctx_size; };
@@ -305,6 +309,7 @@ struct swevent_hlist {#define PERF_ATTACH_CONTEXT 0x01#define PERF_ATTACH_GROUP 0x02#define PERF_ATTACH_TASK 0x04 +#define PERF_ATTACH_TASK_DATA 0x08struct perf_cgroup ;struct ring_buffer ;
@@ -514,6 +519,7 @@ struct perf_event_context {u64 generation;int pin_count;int nr_cgroups;/* cgroup evts */ +void *task_ctx_data;/* pmu specific data */ struct rcu_head rcu_head;struct delayed_work orphans_remove;
kernel/events/core.c +36 -4
@@ -895,6 +895,15 @@ static void get_ctx(struct perf_event_context *ctx)WARN_ON (!atomic_inc_not_zero (&ctx->refcount)); } +static void free_ctx (struct rcu_head *head) +{ +struct perf_event_context *ctx; + + ctx = container_of(head, struct perf_event_context, rcu_head); +kfree (ctx->task_ctx_data); +kfree (ctx); +} +static void put_ctx (struct perf_event_context *ctx) {if (atomic_dec_and_test (&ctx->refcount)) {
@@ -902,7 +911,7 @@ static void put_ctx(struct perf_event_context *ctx)put_ctx (ctx->parent_ctx);if (ctx->task)put_task_struct (ctx->task); -kfree_rcu (ctx, rcu_head); +call_rcu (&ctx->rcu_head, free_ctx); } }
@@ -3188,12 +3197,15 @@ errout:* Returns a matching context with refcount and pincount. */ static struct perf_event_context * -find_get_context (struct pmu *pmu,struct task_struct *task,int cpu) +find_get_context (struct pmu *pmu,struct task_struct *task, +struct perf_event *event) {struct perf_event_context *ctx, *clone_ctx =NULL ;struct perf_cpu_context *cpuctx; +void *task_ctx_data =NULL ;unsigned long flags;int ctxn, err; +int cpu = event->cpu;if (!task) {/* Must be root to operate on a CPU event: */
@@ -3221,11 +3233,24 @@ find_get_context(struct pmu *pmu, struct task_struct *task, int cpu)if (ctxn <0 ) goto errout; +if (event->attach_state &PERF_ATTACH_TASK_DATA ) { + task_ctx_data =kzalloc (pmu->task_ctx_size,GFP_KERNEL ); +if (!task_ctx_data) { + err = -ENOMEM ; + goto errout; + } + } + retry: ctx =perf_lock_task_context (task, ctxn, &flags);if (ctx) { clone_ctx =unclone_ctx (ctx); ++ctx->pin_count; + +if (task_ctx_data && !ctx->task_ctx_data) { + ctx->task_ctx_data = task_ctx_data; + task_ctx_data =NULL ; + }raw_spin_unlock_irqrestore (&ctx->lock, flags);if (clone_ctx)
@@ -3236,6 +3261,11 @@ retry:if (!ctx) goto errout; +if (task_ctx_data) { + ctx->task_ctx_data = task_ctx_data; + task_ctx_data =NULL ; + } + err =0 ;mutex_lock (&task->perf_event_mutex);/*
@@ -3262,9 +3292,11 @@ retry: } } +kfree (task_ctx_data);return ctx; errout: +kfree (task_ctx_data);return ERR_PTR (err); }
@@ -7331,7 +7363,7 @@ SYSCALL_DEFINE5(perf_event_open,/* * Get the target context (task or percpu): */ - ctx =find_get_context (pmu, task, event->cpu); + ctx =find_get_context (pmu, task, event);if (IS_ERR (ctx)) { err =PTR_ERR (ctx); goto err_alloc;
@@ -7500,7 +7532,7 @@ perf_event_create_kernel_counter(struct perf_event_attr *attr, int cpu,account_event (event); - ctx =find_get_context (event->pmu, task, cpu); + ctx =find_get_context (event->pmu, task, event);if (IS_ERR (ctx)) { err =PTR_ERR (ctx); goto err_free;
Signature · 1 line
1.8.3.2
tip-bot for Yan, Zheng
merge bot[tip:perf/core] perf: Add pmu specific data for perf task context
perf: Add pmu specific data for perf task context
Commit-ID: 4af57ef28c2c1047fda9e1a5be02aa7a6a69cf9e Gitweb: http://git.kernel.org/tip/4af57ef28c2c1047fda9e1a5be02aa7a6a69cf9e Author: Yan, Zheng <[email protected]> AuthorDate: Tue, 4 Nov 2014 21:56:01 -0500 Committer: Ingo Molnar <[email protected]> CommitDate: Wed, 18 Feb 2015 17:16:05 +0100
perf: Add pmu specific data for perf task context
Introduce a new flag PERF_ATTACH_TASK_DATA for perf event's attach stata. The flag is set by PMU's event_init() callback, it indicates that perf event needs PMU specific data.
The PMU specific data are initialized to zeros. Later patches will use PMU specific data to save LBR stack.
--- include/linux/perf_event.h | 6 ++++++ kernel/events/core.c | 40 ++++++++++++++++++++++++++++++++++++---- 2 files changed, 42 insertions(+), 4 deletions(-)
include/linux/perf_event.h +6 -0
@@ -271,6 +271,10 @@ struct pmu {*/ void (*sched_task) (struct perf_event_context *ctx,bool sched_in); +/* +* PMU specific data size +*/ +size_t task_ctx_size; };
@@ -307,6 +311,7 @@ struct swevent_hlist {#define PERF_ATTACH_CONTEXT 0x01#define PERF_ATTACH_GROUP 0x02#define PERF_ATTACH_TASK 0x04 +#define PERF_ATTACH_TASK_DATA 0x08struct perf_cgroup ;struct ring_buffer ;
@@ -511,6 +516,7 @@ struct perf_event_context {u64 generation;int pin_count;int nr_cgroups;/* cgroup evts */ +void *task_ctx_data;/* pmu specific data */ struct rcu_head rcu_head;struct delayed_work orphans_remove;
kernel/events/core.c +36 -4
@@ -905,6 +905,15 @@ static void get_ctx(struct perf_event_context *ctx)WARN_ON (!atomic_inc_not_zero (&ctx->refcount)); } +static void free_ctx (struct rcu_head *head) +{ +struct perf_event_context *ctx; + + ctx = container_of(head, struct perf_event_context, rcu_head); +kfree (ctx->task_ctx_data); +kfree (ctx); +} +static void put_ctx (struct perf_event_context *ctx) {if (atomic_dec_and_test (&ctx->refcount)) {
@@ -912,7 +921,7 @@ static void put_ctx(struct perf_event_context *ctx)put_ctx (ctx->parent_ctx);if (ctx->task)put_task_struct (ctx->task); -kfree_rcu (ctx, rcu_head); +call_rcu (&ctx->rcu_head, free_ctx); } }
@@ -3309,12 +3318,15 @@ errout:* Returns a matching context with refcount and pincount. */ static struct perf_event_context * -find_get_context (struct pmu *pmu,struct task_struct *task,int cpu) +find_get_context (struct pmu *pmu,struct task_struct *task, +struct perf_event *event) {struct perf_event_context *ctx, *clone_ctx =NULL ;struct perf_cpu_context *cpuctx; +void *task_ctx_data =NULL ;unsigned long flags;int ctxn, err; +int cpu = event->cpu;if (!task) {/* Must be root to operate on a CPU event: */
@@ -3342,11 +3354,24 @@ find_get_context(struct pmu *pmu, struct task_struct *task, int cpu)if (ctxn <0 ) goto errout; +if (event->attach_state &PERF_ATTACH_TASK_DATA ) { + task_ctx_data =kzalloc (pmu->task_ctx_size,GFP_KERNEL ); +if (!task_ctx_data) { + err = -ENOMEM ; + goto errout; + } + } + retry: ctx =perf_lock_task_context (task, ctxn, &flags);if (ctx) { clone_ctx =unclone_ctx (ctx); ++ctx->pin_count; + +if (task_ctx_data && !ctx->task_ctx_data) { + ctx->task_ctx_data = task_ctx_data; + task_ctx_data =NULL ; + }raw_spin_unlock_irqrestore (&ctx->lock, flags);if (clone_ctx)
@@ -3357,6 +3382,11 @@ retry:if (!ctx) goto errout; +if (task_ctx_data) { + ctx->task_ctx_data = task_ctx_data; + task_ctx_data =NULL ; + } + err =0 ;mutex_lock (&task->perf_event_mutex);/*
@@ -3383,9 +3413,11 @@ retry: } } +kfree (task_ctx_data);return ctx; errout: +kfree (task_ctx_data);return ERR_PTR (err); }
@@ -7559,7 +7591,7 @@ SYSCALL_DEFINE5(perf_event_open,/* * Get the target context (task or percpu): */ - ctx =find_get_context (pmu, task, event->cpu); + ctx =find_get_context (pmu, task, event);if (IS_ERR (ctx)) { err =PTR_ERR (ctx); goto err_alloc;
@@ -7765,7 +7797,7 @@ perf_event_create_kernel_counter(struct perf_event_attr *attr, int cpu,account_event (event); - ctx =find_get_context (event->pmu, task, cpu); + ctx =find_get_context (event->pmu, task, event);if (IS_ERR (ctx)) { err =PTR_ERR (ctx); goto err_free;
Peter Zijlstra
maintainerRe: [tip:perf/core] perf: Add pmu specific data for perf task context
Quoted 50 lines · Zheng
(quoted diff) +22
-0+find_get_context(struct pmu *pmu, struct task_struct *task, + struct perf_event *event) { struct perf_event_context *ctx, *clone_ctx = NULL; struct perf_cpu_context *cpuctx; + void *task_ctx_data = NULL; unsigned long flags; int ctxn, err; + int cpu = event->cpu; if (!task) { /* Must be root to operate on a CPU event: */@@ -3342,11 +3354,24 @@ find_get_context(struct pmu *pmu, struct task_struct *task, int cpu) if (ctxn < 0) goto errout; + if (event->attach_state & PERF_ATTACH_TASK_DATA) { + task_ctx_data = kzalloc(pmu->task_ctx_size, GFP_KERNEL); + if (!task_ctx_data) { + err = -ENOMEM; + goto errout; + } + } + retry: ctx = perf_lock_task_context(task, ctxn, &flags); if (ctx) { clone_ctx = unclone_ctx(ctx); ++ctx->pin_count; + + if (task_ctx_data && !ctx->task_ctx_data) { + ctx->task_ctx_data = task_ctx_data; + task_ctx_data = NULL; + } raw_spin_unlock_irqrestore(&ctx->lock, flags); if (clone_ctx)@@ -3357,6 +3382,11 @@ retry: if (!ctx) goto errout; + if (task_ctx_data) { + ctx->task_ctx_data = task_ctx_data; + task_ctx_data = NULL; + } + err = 0; mutex_lock(&task->perf_event_mutex); /*
Review retry: · line 3422
Quoted 10 lines
(quoted diff) +2
-0@@ -3383,9 +3413,11 @@ retry: } } + kfree(task_ctx_data); return ctx; errout: + kfree(task_ctx_data); return ERR_PTR(err); }
kernel/events/core.c +4 -5
@@ -3508,11 +3515,6 @@ retry:if (!ctx) goto errout; -if (task_ctx_data) { - ctx->task_ctx_data = task_ctx_data; - task_ctx_data =NULL ; - } - err =0 ;mutex_lock (&task->perf_event_mutex);/*
@@ -3526,6 +3528,10 @@ retry:else {get_ctx (ctx); ++ctx->pin_count; +if (task_ctx_data) { + ctx->task_ctx_data = task_ctx_data; + task_ctx_data =NULL ; + }rcu_assign_pointer (task->perf_event_ctxp[ctxn], ctx); }mutex_unlock (&task->perf_event_mutex);
Does that make sense? No point in setting task_ctx_data if we're going to free the ctx and try again.
RE: [tip:perf/core] perf: Add pmu specific data for perf task context
Quoted 96 lines · Zheng
Review
Quoted 12 lines
(quoted diff) +4
-0+find_get_context(struct pmu *pmu, struct task_struct *task, + struct perf_event *event) { struct perf_event_context *ctx, *clone_ctx = NULL; struct perf_cpu_context *cpuctx; + void *task_ctx_data = NULL; unsigned long flags; int ctxn, err; + int cpu = event->cpu; if (!task) { /* Must be root to operate on a CPU event: */ @@ -3342,11 +3354,24
Quoted 48 lines
@@
find_get_context(struct pmu *pmu, struct task_struct *task, int cpu)kernel/events/core.c +20
-0if (ctxn <0 ) goto errout; +if (event->attach_state &PERF_ATTACH_TASK_DATA ) { + task_ctx_data =kzalloc (pmu->task_ctx_size,GFP_KERNEL ); +if (!task_ctx_data) { + err = -ENOMEM ; + goto errout; + } + } + retry: ctx =perf_lock_task_context (task, ctxn, &flags);if (ctx) { clone_ctx =unclone_ctx (ctx); ++ctx->pin_count; + +if (task_ctx_data && !ctx->task_ctx_data) { + ctx->task_ctx_data = task_ctx_data; + task_ctx_data =NULL ; + }raw_spin_unlock_irqrestore (&ctx->lock, flags);if (clone_ctx)@@ -3357,6 +3382,11 @@ retry:if (!ctx) goto errout; +if (task_ctx_data) { + ctx->task_ctx_data = task_ctx_data; + task_ctx_data =NULL ; + } + err =0 ;mutex_lock (&task->perf_event_mutex);/* @@ -3383,9 +3413,11 @@ retry: } } +kfree (task_ctx_data);return ctx; errout: +kfree (task_ctx_data);return ERR_PTR (err); }kernel/events/core.c index renamed from kernel/events/core.c +0
-036babfd..97aa610 100644
kernel/events/core.c +4
-5@@ -3508,11 +3515,6 @@ retry:if (!ctx) goto errout; -if (task_ctx_data) { - ctx->task_ctx_data = task_ctx_data; - task_ctx_data =NULL ; - } - err =0 ;mutex_lock (&task->perf_event_mutex);/* @@ -3526,6 +3528,10 @@ retry:else {get_ctx (ctx); ++ctx->pin_count; +if (task_ctx_data) { + ctx->task_ctx_data = task_ctx_data; + task_ctx_data =NULL ; + }rcu_assign_pointer (task->perf_event_ctxp[ctxn], ctx); }
mutex_unlock(&task->perf_event_mutex);
Quoted 2 lines
Does that make sense? No point in setting
task_ctx_dataif we're going to free the ctx and try again.
The task_ctx_data will be checked before use. So it wouldn't crash the system if it's NULL.
The problem is that LBR stack info will not be save/store on context switch anymore. The user probably get wrong call stack information. May I know why you want to do that?
Thanks,
Kan
Peter Zijlstra
maintainerRe: [tip:perf/core] perf: Add pmu specific data for perf task context
Quoted 30 lines · Kan
Quoted 30 lines
kernel/events/core.c index renamed from kernel/events/core.c +0
-036babfd..97aa610 100644
kernel/events/core.c +4
-5@@ -3508,11 +3515,6 @@ retry:if (!ctx) goto errout; -if (task_ctx_data) { - ctx->task_ctx_data = task_ctx_data; - task_ctx_data =NULL ; - } - err =0 ;mutex_lock (&task->perf_event_mutex);/* @@ -3526,6 +3528,10 @@ retry:else {get_ctx (ctx); ++ctx->pin_count; +if (task_ctx_data) { + ctx->task_ctx_data = task_ctx_data; + task_ctx_data =NULL ; + }rcu_assign_pointer (task->perf_event_ctxp[ctxn], ctx); }
mutex_unlock(&task->perf_event_mutex);
Quoted 5 lines
Quoted 2 lines
Does that make sense? No point in setting
task_ctx_dataif we're going to free the ctx and try again.The
task_ctx_datawill be checked before use. So it wouldn't crash the system if it's NULL.
Yeah, I know, I checked :-)
Quoted 2 lines
The problem is that LBR stack info will not be save/store on context switch anymore. The user probably get wrong call stack information.
Yep
Quoted 1 line
May I know why you want to do that?
Because this seemed like a less fragile construct. When there's multiple event creations racing it seems possible (ableit entirely unlikely) to assign the allocated task_ctx_data to a ctx that we'll delete, and on the second go around re-allocate a ctx, but are left wihtout task_ctx_data to assign to it.
So by only assigning the task_ctx_data when we _know_ we've succeeded, we'll avoid this scenario.
RE: [tip:perf/core] perf: Add pmu specific data for perf task context
Quoted 48 lines · Kan
Quoted 30 lines
Quoted 30 lines
kernel/events/core.c index renamed from kernel/events/core.c +0
-036babfd..97aa610 100644
kernel/events/core.c +4
-5@@ -3508,11 +3515,6 @@ retry:if (!ctx) goto errout; -if (task_ctx_data) { - ctx->task_ctx_data = task_ctx_data; - task_ctx_data =NULL ; - } - err =0 ;mutex_lock (&task->perf_event_mutex);/* @@ -3526,6 +3528,10 @@ retry:else {get_ctx (ctx); ++ctx->pin_count; +if (task_ctx_data) { + ctx->task_ctx_data = task_ctx_data; + task_ctx_data =NULL ; + }rcu_assign_pointer (task->perf_event_ctxp[ctxn], ctx); }
mutex_unlock(&task->perf_event_mutex);Quoted 5 lines
Quoted 2 lines
Does that make sense? No point in setting
task_ctx_dataif we're going to free the ctx and try again.The
task_ctx_datawill be checked before use. So it wouldn't crash the system if it's NULL.Yeah, I know, I checked :-)
Quoted 2 lines
The problem is that LBR stack info will not be save/store on context switch anymore. The user probably get wrong call stack information.
Yep
Quoted 1 line
May I know why you want to do that?
Quoted 7 lines
Because this seemed like a less fragile construct. When there's multiple event creations racing it seems possible (ableit entirely unlikely) to assign the allocated
task_ctx_datato a ctx that we'll delete, and on the second go around re-allocate a ctx, but are left wihtouttask_ctx_datato assign to it.So by only assigning the
task_ctx_datawhen we _know_ we've succeeded, we'll avoid this scenario.
Yes, I think it make sense to that.
Thanks,
Kan
PATCH v7 6/17 perf, core: always switch pmu specific data during context switch
In reply to Kan LiangFrom: Yan, Zheng <[email protected]>
If two tasks were both forked from the same parent task, Events in their perf task contexts can be the same. Perf core may leave out switching the perf event contexts.
Previous patch inroduces pmu specific data. The data is for saving the LBR stack, it is task specific. So we need to switch the data even when context switch is optimized out.
--- kernel/events/core.c | 3 +++ 1 file changed, 3 insertions(+)
kernel/events/core.c +3 -0
@@ -2420,6 +2420,9 @@ static void perf_event_context_sched_out(struct task_struct *task, int ctxn, next->perf_event_ctxp[ctxn] = ctx; ctx->task = next; next_ctx->task = task; + +swap (ctx->task_ctx_data, next_ctx->task_ctx_data); + do_switch =0 ;perf_event_sync_stat (ctx, next_ctx);
Signature · 1 line
1.8.3.2
tip-bot for Yan, Zheng
merge bot[tip:perf/core] perf: Always switch pmu specific data during context switch
perf: Always switch pmu specific data during context switch
Commit-ID: 5a158c3ccd2183a7b0866be6685d001fe653430f Gitweb: http://git.kernel.org/tip/5a158c3ccd2183a7b0866be6685d001fe653430f Author: Yan, Zheng <[email protected]> AuthorDate: Tue, 4 Nov 2014 21:56:02 -0500 Committer: Ingo Molnar <[email protected]> CommitDate: Wed, 18 Feb 2015 17:16:07 +0100
perf: Always switch pmu specific data during context switch
If two tasks were both forked from the same parent task, Events in their perf task contexts can be the same. Perf core may leave out switching the perf event contexts.
Previous patch inroduces pmu specific data. The data is for saving the LBR stack, it is task specific. So we need to switch the data even when context switch is optimized out.
--- kernel/events/core.c | 3 +++ 1 file changed, 3 insertions(+)
kernel/events/core.c +3 -0
@@ -2562,6 +2562,9 @@ static void perf_event_context_sched_out(struct task_struct *task, int ctxn, next->perf_event_ctxp[ctxn] = ctx; ctx->task = next; next_ctx->task = task; + +swap (ctx->task_ctx_data, next_ctx->task_ctx_data); + do_switch =0 ;perf_event_sync_stat (ctx, next_ctx);
PATCH v7 7/17 perf, x86: allocate space for storing LBR stack
In reply to Kan LiangFrom: Yan, Zheng <[email protected]>
When the LBR call stack is enabled, it is necessary to save/restore the LBR stack on context switch. We can use pmu specific data to store LBR stack when task is scheduled out. This patch adds code that allocates the pmu specific data.
--- arch/x86/kernel/cpu/perf_event.c | 4 ++++ arch/x86/kernel/cpu/perf_event.h | 7 +++++++ 2 files changed, 11 insertions(+)
arch/x86/kernel/cpu/perf_event.c +4 -0
@@ -428,6 +428,9 @@ int x86_pmu_hw_config(struct perf_event *event) } } +if (event->attr.branch_sample_type &PERF_SAMPLE_BRANCH_CALL_STACK ) + event->attach_state |=PERF_ATTACH_TASK_DATA ; +/* * Generate PMC IRQs: * (keep 'enabled' bit clear for now)
@@ -1912,6 +1915,7 @@ static struct pmu pmu = { .event_idx = x86_pmu_event_idx, .sched_task = x86_pmu_sched_task, + .task_ctx_size = sizeof(struct x86_perf_task_context), };void arch_perf_update_userpage (struct perf_event_mmap_page *userpg,u64 now)
arch/x86/kernel/cpu/perf_event.h +7 -0
@@ -510,6 +510,13 @@ struct x86_pmu {struct perf_guest_switch_msr *(*guest_get_msrs)(int *nr); }; +struct x86_perf_task_context { +u64 lbr_from[MAX_LBR_ENTRIES ]; +u64 lbr_to[MAX_LBR_ENTRIES ]; +int lbr_callstack_users; +int lbr_stack_state; +}; +enum {PERF_SAMPLE_BRANCH_CALL_STACK_SHIFT =PERF_SAMPLE_BRANCH_MAX_SHIFT ,PERF_SAMPLE_BRANCH_SELECT_MAP_SIZE ,
Signature · 1 line
1.8.3.2
tip-bot for Yan, Zheng
merge bot[tip:perf/core] perf/x86/intel: Allocate space for storing LBR stack
perf/x86/intel: Allocate space for storing LBR stack
Commit-ID: e18bf526422769611e7248135e36a4cea0e4e38d Gitweb: http://git.kernel.org/tip/e18bf526422769611e7248135e36a4cea0e4e38d Author: Yan, Zheng <[email protected]> AuthorDate: Tue, 4 Nov 2014 21:56:03 -0500 Committer: Ingo Molnar <[email protected]> CommitDate: Wed, 18 Feb 2015 17:16:08 +0100
perf/x86/intel: Allocate space for storing LBR stack
When the LBR call stack is enabled, it is necessary to save/restore the LBR stack on context switch. We can use pmu specific data to store LBR stack when task is scheduled out. This patch adds code that allocates the pmu specific data.
--- arch/x86/kernel/cpu/perf_event.c | 4 ++++ arch/x86/kernel/cpu/perf_event.h | 7 +++++++ 2 files changed, 11 insertions(+)
arch/x86/kernel/cpu/perf_event.c +4 -0
@@ -432,6 +432,9 @@ int x86_pmu_hw_config(struct perf_event *event) } } +if (event->attr.branch_sample_type &PERF_SAMPLE_BRANCH_CALL_STACK ) + event->attach_state |=PERF_ATTACH_TASK_DATA ; +/* * Generate PMC IRQs: * (keep 'enabled' bit clear for now)
@@ -1950,6 +1953,7 @@ static struct pmu pmu = { .event_idx = x86_pmu_event_idx, .sched_task = x86_pmu_sched_task, + .task_ctx_size = sizeof(struct x86_perf_task_context), }; void arch_perf_update_userpage(struct perf_event *event,
arch/x86/kernel/cpu/perf_event.h +7 -0
@@ -516,6 +516,13 @@ struct x86_pmu {struct perf_guest_switch_msr *(*guest_get_msrs)(int *nr); }; +struct x86_perf_task_context { +u64 lbr_from[MAX_LBR_ENTRIES ]; +u64 lbr_to[MAX_LBR_ENTRIES ]; +int lbr_callstack_users; +int lbr_stack_state; +}; +enum {PERF_SAMPLE_BRANCH_CALL_STACK_SHIFT =PERF_SAMPLE_BRANCH_MAX_SHIFT ,PERF_SAMPLE_BRANCH_SELECT_MAP_SIZE ,
PATCH v7 8/17 perf, x86: track number of events that use LBR callstack
In reply to Kan LiangFrom: Yan, Zheng <[email protected]>
When enabling/disabling an event, check if the event uses the LBR callstack feature, adjust the LBR callstack usage count accordingly. Later patch will use the usage count to decide if LBR stack should be saved/restored.
--- arch/x86/kernel/cpu/perf_event_intel_lbr.c | 19 +++++++++++++++++++ 1 file changed, 19 insertions(+)
arch/x86/kernel/cpu/perf_event_intel_lbr.c +19 -0
@@ -205,9 +205,15 @@ void intel_pmu_lbr_sched_task(struct perf_event_context *ctx, bool sched_in) } } +static inline bool branch_user_callstack (unsigned br_sel) +{ +return (br_sel &X86_BR_USER ) && (br_sel &X86_BR_CALL_STACK ); +} +void intel_pmu_lbr_enable (struct perf_event *event) {struct cpu_hw_events *cpuc =this_cpu_ptr (&cpu_hw_events); +struct x86_perf_task_context *task_ctx;if (!x86_pmu.lbr_nr)return ;
@@ -222,6 +228,12 @@ void intel_pmu_lbr_enable(struct perf_event *event) } cpuc->br_sel = event->hw.branch_reg.reg; +if (branch_user_callstack (cpuc->br_sel) && event->ctx && + event->ctx->task_ctx_data) { + task_ctx = event->ctx->task_ctx_data; + task_ctx->lbr_callstack_users++; + } + cpuc->lbr_users++;perf_sched_cb_inc (event->ctx->pmu); }
@@ -229,10 +241,17 @@ void intel_pmu_lbr_enable(struct perf_event *event)void intel_pmu_lbr_disable (struct perf_event *event) {struct cpu_hw_events *cpuc =this_cpu_ptr (&cpu_hw_events); +struct x86_perf_task_context *task_ctx;if (!x86_pmu.lbr_nr)return ; +if (branch_user_callstack (cpuc->br_sel) && event->ctx && + event->ctx->task_ctx_data) { + task_ctx = event->ctx->task_ctx_data; + task_ctx->lbr_callstack_users--; + } + cpuc->lbr_users--;WARN_ON_ONCE (cpuc->lbr_users <0 );perf_sched_cb_dec (event->ctx->pmu);
Signature · 1 line
1.8.3.2
tip-bot for Yan, Zheng
merge bot[tip:perf/core] perf/x86/intel: Track number of events that use the LBR callstack
perf/x86/intel: Track number of events that use the LBR callstack
Commit-ID: 63f0c1d84196b712fe9de99a8514486ab416d517 Gitweb: http://git.kernel.org/tip/63f0c1d84196b712fe9de99a8514486ab416d517 Author: Yan, Zheng <[email protected]> AuthorDate: Tue, 4 Nov 2014 21:56:04 -0500 Committer: Ingo Molnar <[email protected]> CommitDate: Wed, 18 Feb 2015 17:16:09 +0100
perf/x86/intel: Track number of events that use the LBR callstack
When enabling/disabling an event, check if the event uses the LBR callstack feature, adjust the LBR callstack usage count accordingly. Later patch will use the usage count to decide if LBR stack should be saved/restored.
--- arch/x86/kernel/cpu/perf_event_intel_lbr.c | 19 +++++++++++++++++++ 1 file changed, 19 insertions(+)
arch/x86/kernel/cpu/perf_event_intel_lbr.c +19 -0
@@ -205,9 +205,15 @@ void intel_pmu_lbr_sched_task(struct perf_event_context *ctx, bool sched_in) } } +static inline bool branch_user_callstack (unsigned br_sel) +{ +return (br_sel &X86_BR_USER ) && (br_sel &X86_BR_CALL_STACK ); +} +void intel_pmu_lbr_enable (struct perf_event *event) {struct cpu_hw_events *cpuc =this_cpu_ptr (&cpu_hw_events); +struct x86_perf_task_context *task_ctx;if (!x86_pmu.lbr_nr)return ;
@@ -222,6 +228,12 @@ void intel_pmu_lbr_enable(struct perf_event *event) } cpuc->br_sel = event->hw.branch_reg.reg; +if (branch_user_callstack (cpuc->br_sel) && event->ctx && + event->ctx->task_ctx_data) { + task_ctx = event->ctx->task_ctx_data; + task_ctx->lbr_callstack_users++; + } + cpuc->lbr_users++;perf_sched_cb_inc (event->ctx->pmu); }
@@ -229,10 +241,17 @@ void intel_pmu_lbr_enable(struct perf_event *event)void intel_pmu_lbr_disable (struct perf_event *event) {struct cpu_hw_events *cpuc =this_cpu_ptr (&cpu_hw_events); +struct x86_perf_task_context *task_ctx;if (!x86_pmu.lbr_nr)return ; +if (branch_user_callstack (cpuc->br_sel) && event->ctx && + event->ctx->task_ctx_data) { + task_ctx = event->ctx->task_ctx_data; + task_ctx->lbr_callstack_users--; + } + cpuc->lbr_users--;WARN_ON_ONCE (cpuc->lbr_users <0 );perf_sched_cb_dec (event->ctx->pmu);
PATCH v7 9/17 perf, x86: Save/resotre LBR stack during context switch
In reply to Kan LiangFrom: Yan, Zheng <[email protected]>
When the LBR call stack is enabled, it is necessary to save/restore the LBR stack on context switch. The solution is saving/restoring the LBR stack to/from task's perf event context.
The LBR stack is saved/restored only when there are events that use the LBR call stack. If no event uses LBR call stack, the LBR stack is reset when task is scheduled in.
--- arch/x86/kernel/cpu/perf_event_intel_lbr.c | 88 ++++++++++++++++++++++++++---- 1 file changed, 76 insertions(+), 12 deletions(-)
arch/x86/kernel/cpu/perf_event_intel_lbr.c +76 -12
@@ -180,14 +180,90 @@ void intel_pmu_lbr_reset(void)intel_pmu_lbr_reset_64 (); } +/* +* TOS = most recently recorded branch +*/ +static inline u64 intel_pmu_lbr_tos (void ) +{ +u64 tos; + +rdmsrl (x86_pmu.lbr_tos, tos); +return tos; +} + +enum { +LBR_NONE , +LBR_VALID , +}; + +static void __intel_pmu_lbr_restore (struct x86_perf_task_context *task_ctx) +{ +int i; +unsigned lbr_idx, mask; +u64 tos; + +if (task_ctx->lbr_callstack_users ==0 || + task_ctx->lbr_stack_state ==LBR_NONE ) { +intel_pmu_lbr_reset (); +return ; + } + + mask = x86_pmu.lbr_nr -1 ; + tos =intel_pmu_lbr_tos (); +for (i =0 ; i < x86_pmu.lbr_nr; i++) { + lbr_idx = (tos - i) & mask; +wrmsrl (x86_pmu.lbr_from + lbr_idx, task_ctx->lbr_from[i]); +wrmsrl (x86_pmu.lbr_to + lbr_idx, task_ctx->lbr_to[i]); + } + task_ctx->lbr_stack_state =LBR_NONE ; +} + +static void __intel_pmu_lbr_save (struct x86_perf_task_context *task_ctx) +{ +int i; +unsigned lbr_idx, mask; +u64 tos; + +if (task_ctx->lbr_callstack_users ==0 ) { + task_ctx->lbr_stack_state =LBR_NONE ; +return ; + } + + mask = x86_pmu.lbr_nr -1 ; + tos =intel_pmu_lbr_tos (); +for (i =0 ; i < x86_pmu.lbr_nr; i++) { + lbr_idx = (tos - i) & mask; +rdmsrl (x86_pmu.lbr_from + lbr_idx, task_ctx->lbr_from[i]); +rdmsrl (x86_pmu.lbr_to + lbr_idx, task_ctx->lbr_to[i]); + } + task_ctx->lbr_stack_state =LBR_VALID ; +} +void intel_pmu_lbr_sched_task (struct perf_event_context *ctx,bool sched_in) {struct cpu_hw_events *cpuc =this_cpu_ptr (&cpu_hw_events); +struct x86_perf_task_context *task_ctx;if (!x86_pmu.lbr_nr)return ;/* +* If LBR callstack feature is enabled and the stack was saved when +* the task was scheduled out, restore the stack. Otherwise flush +* the LBR stack. +*/ + task_ctx = ctx ? ctx->task_ctx_data :NULL ; +if (task_ctx) { +if (sched_in) { +__intel_pmu_lbr_restore (task_ctx); + cpuc->lbr_context = ctx; + }else { +__intel_pmu_lbr_save (task_ctx); + } +return ; + } + +/* * When sampling the branck stack in system-wide, it may be * necessary to flush the stack on context switch. This happens * when the branch stack does not tag its entries with the pid
@@ -279,18 +355,6 @@ void intel_pmu_lbr_disable_all(void)__intel_pmu_lbr_disable (); } -/* -* TOS = most recently recorded branch -*/ -static inline u64 intel_pmu_lbr_tos (void ) -{ -u64 tos; - -rdmsrl (x86_pmu.lbr_tos, tos); - -return tos; -} -static void intel_pmu_lbr_read_32 (struct cpu_hw_events *cpuc) {unsigned long mask = x86_pmu.lbr_nr -1 ;
Signature · 1 line
1.8.3.2
tip-bot for Yan, Zheng
merge bot[tip:perf/core] perf/x86/intel: Save/ restore LBR stack during context switch
perf/x86/intel: Save/restore LBR stack during context switch
Commit-ID: 76cb2c617f12a4dd53c0e899972813b805ad6cc2 Gitweb: http://git.kernel.org/tip/76cb2c617f12a4dd53c0e899972813b805ad6cc2 Author: Yan, Zheng <[email protected]> AuthorDate: Tue, 4 Nov 2014 21:56:05 -0500 Committer: Ingo Molnar <[email protected]> CommitDate: Wed, 18 Feb 2015 17:16:10 +0100
perf/x86/intel: Save/restore LBR stack during context switch
When the LBR call stack is enabled, it is necessary to save/restore the LBR stack on context switch. The solution is saving/restoring the LBR stack to/from task's perf event context.
The LBR stack is saved/restored only when there are events that use the LBR call stack. If no event uses LBR call stack, the LBR stack is reset when task is scheduled in.
--- arch/x86/kernel/cpu/perf_event_intel_lbr.c | 88 ++++++++++++++++++++++++++---- 1 file changed, 76 insertions(+), 12 deletions(-)
arch/x86/kernel/cpu/perf_event_intel_lbr.c +76 -12
@@ -180,14 +180,90 @@ void intel_pmu_lbr_reset(void)intel_pmu_lbr_reset_64 (); } +/* +* TOS = most recently recorded branch +*/ +static inline u64 intel_pmu_lbr_tos (void ) +{ +u64 tos; + +rdmsrl (x86_pmu.lbr_tos, tos); +return tos; +} + +enum { +LBR_NONE , +LBR_VALID , +}; + +static void __intel_pmu_lbr_restore (struct x86_perf_task_context *task_ctx) +{ +int i; +unsigned lbr_idx, mask; +u64 tos; + +if (task_ctx->lbr_callstack_users ==0 || + task_ctx->lbr_stack_state ==LBR_NONE ) { +intel_pmu_lbr_reset (); +return ; + } + + mask = x86_pmu.lbr_nr -1 ; + tos =intel_pmu_lbr_tos (); +for (i =0 ; i < x86_pmu.lbr_nr; i++) { + lbr_idx = (tos - i) & mask; +wrmsrl (x86_pmu.lbr_from + lbr_idx, task_ctx->lbr_from[i]); +wrmsrl (x86_pmu.lbr_to + lbr_idx, task_ctx->lbr_to[i]); + } + task_ctx->lbr_stack_state =LBR_NONE ; +} + +static void __intel_pmu_lbr_save (struct x86_perf_task_context *task_ctx) +{ +int i; +unsigned lbr_idx, mask; +u64 tos; + +if (task_ctx->lbr_callstack_users ==0 ) { + task_ctx->lbr_stack_state =LBR_NONE ; +return ; + } + + mask = x86_pmu.lbr_nr -1 ; + tos =intel_pmu_lbr_tos (); +for (i =0 ; i < x86_pmu.lbr_nr; i++) { + lbr_idx = (tos - i) & mask; +rdmsrl (x86_pmu.lbr_from + lbr_idx, task_ctx->lbr_from[i]); +rdmsrl (x86_pmu.lbr_to + lbr_idx, task_ctx->lbr_to[i]); + } + task_ctx->lbr_stack_state =LBR_VALID ; +} +void intel_pmu_lbr_sched_task (struct perf_event_context *ctx,bool sched_in) {struct cpu_hw_events *cpuc =this_cpu_ptr (&cpu_hw_events); +struct x86_perf_task_context *task_ctx;if (!x86_pmu.lbr_nr)return ;/* +* If LBR callstack feature is enabled and the stack was saved when +* the task was scheduled out, restore the stack. Otherwise flush +* the LBR stack. +*/ + task_ctx = ctx ? ctx->task_ctx_data :NULL ; +if (task_ctx) { +if (sched_in) { +__intel_pmu_lbr_restore (task_ctx); + cpuc->lbr_context = ctx; + }else { +__intel_pmu_lbr_save (task_ctx); + } +return ; + } + +/* * When sampling the branck stack in system-wide, it may be * necessary to flush the stack on context switch. This happens * when the branch stack does not tag its entries with the pid
@@ -279,18 +355,6 @@ void intel_pmu_lbr_disable_all(void)__intel_pmu_lbr_disable (); } -/* -* TOS = most recently recorded branch -*/ -static inline u64 intel_pmu_lbr_tos (void ) -{ -u64 tos; - -rdmsrl (x86_pmu.lbr_tos, tos); - -return tos; -} -static void intel_pmu_lbr_read_32 (struct cpu_hw_events *cpuc) {unsigned long mask = x86_pmu.lbr_nr -1 ;
PATCH v7 10/17 perf, core: simplify need branch stack check
In reply to Kan LiangFrom: Yan, Zheng <[email protected]>
Using event->attr.branch_sample_type to replace intel_pmu_needs_lbr_smpl() for avoiding duplicating code that implicitly enables the LBR.
Currently, branch stack can be enabled by user explicitly requested branch sampling or implicit branch sampling to correct PEBS skid. For user explicitly requested branch sampling, the branch_sample_type is explicitly set by user. For PEBS case, the branch_sample_type is also implicitly set to PERF_SAMPLE_BRANCH_ANY in x86_pmu_hw_config.
--- arch/x86/kernel/cpu/perf_event_intel.c | 20 +++----------------- include/linux/perf_event.h | 5 +++++ kernel/events/core.c | 3 +++ 3 files changed, 11 insertions(+), 17 deletions(-)
arch/x86/kernel/cpu/perf_event_intel.c +3 -17
@@ -1029,20 +1029,6 @@ static __initconst const u64 slm_hw_cache_event_ids }, }; -static inline bool intel_pmu_needs_lbr_smpl (struct perf_event *event) -{ -/* user explicitly requested branch sampling */ -if (has_branch_stack (event)) -return true; - -/* implicit branch sampling to correct PEBS skid */ -if (x86_pmu.intel_cap.pebs_trap && event->attr.precise_ip >1 && - x86_pmu.intel_cap.pebs_format <2 ) -return true; - -return false; -} -static void intel_pmu_disable_all (void ) {struct cpu_hw_events *cpuc =this_cpu_ptr (&cpu_hw_events);
@@ -1207,7 +1193,7 @@ static void intel_pmu_disable_event(struct perf_event *event)* must disable before any actual event * because any event may be combined with LBR */ -if (intel_pmu_needs_lbr_smpl (event)) +if (needs_branch_stack (event))intel_pmu_lbr_disable (event);if (unlikely (hwc->config_base ==MSR_ARCH_PERFMON_FIXED_CTR_CTRL )) {
@@ -1268,7 +1254,7 @@ static void intel_pmu_enable_event(struct perf_event *event)* must enabled before any actual event * because any event may be combined with LBR */ -if (intel_pmu_needs_lbr_smpl (event)) +if (needs_branch_stack (event))intel_pmu_lbr_enable (event);if (event->attr.exclude_host)
@@ -1747,7 +1733,7 @@ static int intel_pmu_hw_config(struct perf_event *event)if (event->attr.precise_ip && x86_pmu.pebs_aliases) x86_pmu.pebs_aliases (event); -if (intel_pmu_needs_lbr_smpl (event)) { +if (needs_branch_stack (event)) { ret =intel_pmu_setup_lbr_filter (event);if (ret)return ret;
include/linux/perf_event.h +5 -0
@@ -796,6 +796,11 @@ static inline bool has_branch_stack(struct perf_event *event)return event->attr.sample_type &PERF_SAMPLE_BRANCH_STACK ; } +static inline bool needs_branch_stack (struct perf_event *event) +{ +return event->attr.branch_sample_type !=0 ; +} +extern int perf_output_begin (struct perf_output_handle *handle,struct perf_event *event,unsigned int size);extern void perf_output_end (struct perf_output_handle *handle);
kernel/events/core.c +3 -0
@@ -7015,6 +7015,9 @@ perf_event_alloc(struct perf_event_attr *attr, int cpu,if (attr->inherit && (attr->read_format &PERF_FORMAT_GROUP )) goto err_ns; +if (!has_branch_stack (event)) + event->attr.branch_sample_type =0 ; + pmu =perf_init_event (event);if (!pmu) goto err_ns;
Signature · 1 line
1.8.3.2
tip-bot for Yan, Zheng
merge bot[tip:perf/core] perf: Simplify the branch stack check
perf: Simplify the branch stack check
Commit-ID: a46a23000198d929391aa9dac8de68734efa2703 Gitweb: http://git.kernel.org/tip/a46a23000198d929391aa9dac8de68734efa2703 Author: Yan, Zheng <[email protected]> AuthorDate: Tue, 4 Nov 2014 21:56:06 -0500 Committer: Ingo Molnar <[email protected]> CommitDate: Wed, 18 Feb 2015 17:16:11 +0100
perf: Simplify the branch stack check
Use event->attr.branch_sample_type to replace intel_pmu_needs_lbr_smpl() for avoiding duplicated code that implicitly enables the LBR.
Currently, branch stack can be enabled by user explicitly requesting branch sampling or implicit branch sampling to correct PEBS skid.
For user explicitly requested branch sampling, the branch_sample_type is explicitly set by user. For PEBS case, the branch_sample_type is also implicitly set to PERF_SAMPLE_BRANCH_ANY in x86_pmu_hw_config.
--- arch/x86/kernel/cpu/perf_event_intel.c | 20 +++----------------- include/linux/perf_event.h | 5 +++++ kernel/events/core.c | 3 +++ 3 files changed, 11 insertions(+), 17 deletions(-)
arch/x86/kernel/cpu/perf_event_intel.c +3 -17
@@ -1029,20 +1029,6 @@ static __initconst const u64 slm_hw_cache_event_ids }, }; -static inline bool intel_pmu_needs_lbr_smpl (struct perf_event *event) -{ -/* user explicitly requested branch sampling */ -if (has_branch_stack (event)) -return true; - -/* implicit branch sampling to correct PEBS skid */ -if (x86_pmu.intel_cap.pebs_trap && event->attr.precise_ip >1 && - x86_pmu.intel_cap.pebs_format <2 ) -return true; - -return false; -} -static void intel_pmu_disable_all (void ) {struct cpu_hw_events *cpuc =this_cpu_ptr (&cpu_hw_events);
@@ -1207,7 +1193,7 @@ static void intel_pmu_disable_event(struct perf_event *event)* must disable before any actual event * because any event may be combined with LBR */ -if (intel_pmu_needs_lbr_smpl (event)) +if (needs_branch_stack (event))intel_pmu_lbr_disable (event);if (unlikely (hwc->config_base ==MSR_ARCH_PERFMON_FIXED_CTR_CTRL )) {
@@ -1268,7 +1254,7 @@ static void intel_pmu_enable_event(struct perf_event *event)* must enabled before any actual event * because any event may be combined with LBR */ -if (intel_pmu_needs_lbr_smpl (event)) +if (needs_branch_stack (event))intel_pmu_lbr_enable (event);if (event->attr.exclude_host)
@@ -1747,7 +1733,7 @@ static int intel_pmu_hw_config(struct perf_event *event)if (event->attr.precise_ip && x86_pmu.pebs_aliases) x86_pmu.pebs_aliases (event); -if (intel_pmu_needs_lbr_smpl (event)) { +if (needs_branch_stack (event)) { ret =intel_pmu_setup_lbr_filter (event);if (ret)return ret;
include/linux/perf_event.h +5 -0
@@ -814,6 +814,11 @@ static inline bool has_branch_stack(struct perf_event *event)return event->attr.sample_type &PERF_SAMPLE_BRANCH_STACK ; } +static inline bool needs_branch_stack (struct perf_event *event) +{ +return event->attr.branch_sample_type !=0 ; +} +extern int perf_output_begin (struct perf_output_handle *handle,struct perf_event *event,unsigned int size);extern void perf_output_end (struct perf_output_handle *handle);
kernel/events/core.c +3 -0
@@ -7232,6 +7232,9 @@ perf_event_alloc(struct perf_event_attr *attr, int cpu,if (attr->inherit && (attr->read_format &PERF_FORMAT_GROUP )) goto err_ns; +if (!has_branch_stack (event)) + event->attr.branch_sample_type =0 ; + pmu =perf_init_event (event);if (!pmu) goto err_ns;
PATCH v7 11/17 perf, core: expose LBR call stack to user perf tool
In reply to Kan LiangFrom: Yan, Zheng <[email protected]>
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 format. The LBR call stack data will be output as PERF_SAMPLE_BRANCH_STACK data format.
Note: The LBR call stack is only available for user callchain. The kernel is always got from frame pointers.
The user space perf tool also need to be changed to handle these two sources.
--- arch/x86/kernel/cpu/perf_event.c | 7 +++++++ arch/x86/kernel/cpu/perf_event_intel.c | 2 +- arch/x86/kernel/cpu/perf_event_intel_ds.c | 2 +- arch/x86/kernel/cpu/perf_event_intel_lbr.c | 2 ++ include/linux/perf_event.h | 14 +++++++++++++- kernel/events/callchain.c | 1 + kernel/events/core.c | 22 +++++++++++++++++----- 7 files changed, 42 insertions(+), 8 deletions(-)
arch/x86/kernel/cpu/perf_event.c +7 -0
@@ -2041,6 +2041,10 @@ perf_callchain_user32(struct pt_regs *regs, struct perf_callchain_entry *entry)perf_callchain_store (entry, cs_base + frame.return_address); fp = compat_ptr(ss_base + frame.next_frame); } + +if (fp !=compat_ptr (regs->bp)) + entry->source |=PERF_FP_CALLCHAIN ; +return 1 ; }#else
@@ -2093,6 +2097,9 @@ perf_callchain_user(struct perf_callchain_entry *entry, struct pt_regs *regs)perf_callchain_store (entry, frame.return_address); fp = frame.next_frame; } + +if (fp != (void __user *)regs->bp) + entry->source |=PERF_FP_CALLCHAIN ; }/*
arch/x86/kernel/cpu/perf_event_intel.c +1 -1
@@ -1404,7 +1404,7 @@ again:perf_sample_data_init (&data,0 , event->hw.last_period); -if (has_branch_stack (event)) +if (needs_branch_stack (event)) data.br_stack = &cpuc->lbr_stack;if (perf_event_overflow (event, &data, regs))
arch/x86/kernel/cpu/perf_event_intel_ds.c +1 -1
@@ -907,7 +907,7 @@ static void __intel_pmu_pebs_event(struct perf_event *event, data.txn =intel_hsw_transaction (pebs); } -if (has_branch_stack (event)) +if (needs_branch_stack (event)) data.br_stack = &cpuc->lbr_stack;if (perf_event_overflow (event, &data, ®s))
arch/x86/kernel/cpu/perf_event_intel_lbr.c +2 -0
@@ -746,6 +746,8 @@ intel_pmu_lbr_filter(struct cpu_hw_events *cpuc)int i, j, type;bool compress = false; + cpuc->lbr_stack.user_callstack =branch_user_callstack (br_sel); +/* if sampling all branches, then nothing to filter */ if ((br_sel &X86_BR_ALL ) ==X86_BR_ALL )return ;
include/linux/perf_event.h +13 -1
@@ -55,7 +55,16 @@ struct perf_guest_info_callbacks {#include <linux/workqueue.h> #include <asm/local.h> +/* +* From Haswell, the existing Last Branch Record facility can +* also be used to record call chains. +* source: indicates the available call chains source. +*/ +#define PERF_FP_CALLCHAIN 0x01 +#define PERF_LBR_CALLCHAIN 0x02 +struct perf_callchain_entry { +__u64 source;__u64 nr;__u64 ip[PERF_MAX_STACK_DEPTH ]; };
@@ -67,7 +76,9 @@ struct perf_raw_record {/* * branch stack layout: -* nr: number of taken branches stored in entries[] +* user_callstack: LBR is enhanced to support call stack profiling. +* user_callstack indicates if it's call stack info. +* nr: number of taken branches stored in entries[] * * Note that nr can vary from sample to sample * branches (to, from) are stored from most recent
@@ -75,6 +86,7 @@ struct perf_raw_record {* recent branch. */ struct perf_branch_stack { +bool user_callstack;__u64 nr;struct perf_branch_entry entries[0 ]; };
kernel/events/callchain.c +1 -0
@@ -175,6 +175,7 @@ perf_callchain(struct perf_event *event, struct pt_regs *regs)if (!entry) goto exit_put; + entry->source =0 ; entry->nr =0 ;if (kernel && !user_mode (regs)) {
kernel/events/core.c +17 -5
@@ -4793,7 +4793,7 @@ void perf_output_sample(struct perf_output_handle *handle,if (sample_type &PERF_SAMPLE_CALLCHAIN ) {if (data->callchain) { -int size =1 ; +int size =2 ;if (data->callchain) size += data->callchain->nr;
@@ -4824,7 +4824,9 @@ void perf_output_sample(struct perf_output_handle *handle, } } -if (sample_type &PERF_SAMPLE_BRANCH_STACK ) { +/* LBR can be used for call stack, so it may be enabled implicitly. */ +if ((sample_type &PERF_SAMPLE_BRANCH_STACK ) || + (data->br_stack && data->br_stack->user_callstack)) {if (data->br_stack) {size_t size;
@@ -4908,13 +4910,21 @@ void perf_prepare_sample(struct perf_event_header *header, data->ip =perf_instruction_pointer (regs);if (sample_type &PERF_SAMPLE_CALLCHAIN ) { -int size =1 ; +int size =2 ; data->callchain =perf_callchain (event, regs); -if (data->callchain) +if (data->callchain) { size += data->callchain->nr; +if (data->br_stack && + data->br_stack->user_callstack && + !(sample_type &PERF_SAMPLE_BRANCH_STACK ) && + !(sample_type &PERF_SAMPLE_STACK_USER )) + data->callchain->source |= +PERF_LBR_CALLCHAIN ; + } + header->size += size *sizeof (u64); }
@@ -4930,7 +4940,9 @@ void perf_prepare_sample(struct perf_event_header *header, header->size += size; } -if (sample_type &PERF_SAMPLE_BRANCH_STACK ) { +/* LBR can be used for call stack, so it may be enabled implicitly. */ +if ((sample_type &PERF_SAMPLE_BRANCH_STACK ) || + (data->br_stack && data->br_stack->user_callstack)) {int size =sizeof (u64);/* nr */ if (data->br_stack) { size += data->br_stack->nr
Signature · 1 line
1.8.3.2
Peter Zijlstra
maintainerRe: [PATCH V7 11/17] perf, core: expose LBR call stack to user perf tool
Quoted 1 line · Kan Liang
From: Yan, Zheng <[email protected]>
Now for this patch I'm fairly sure Zheng didn't actually write it; his last posting did something different IIRC.
Quoted 1 line
With LBR call stack feature enable, there are two call chain data
_three_, LBR is the 3rd.
Quoted 6 lines
sources, traditional frame pointer and LBR call stack.
This patch extends theperf_callchain_entrystruct to mark the available call chain source.
The frame pointer is still output asPERF_SAMPLE_CALLCHAINdata format. The LBR call stack data will be output asPERF_SAMPLE_BRANCH_STACKdata format.
I'm not sure what this patch does?! Why do the FP based callchains need _any_ changes?
PATCH v7 12/17 perf, x86: re-organize code that implicitly enables LBR/PEBS
In reply to Kan LiangFrom: Yan, Zheng <[email protected]>
make later patch more readable, no logic change.
--- arch/x86/kernel/cpu/perf_event.c | 59 ++++++++++++++++++++-------------------- 1 file changed, 29 insertions(+), 30 deletions(-)
arch/x86/kernel/cpu/perf_event.c +29 -30
@@ -395,36 +395,35 @@ int x86_pmu_hw_config(struct perf_event *event)if (event->attr.precise_ip > precise)return -EOPNOTSUPP ; -/* -* check that PEBS LBR correction does not conflict with -* whatever the user is asking with attr->branch_sample_type -*/ -if (event->attr.precise_ip >1 && - x86_pmu.intel_cap.pebs_format <2 ) { -u64 *br_type = &event->attr.branch_sample_type; - -if (has_branch_stack (event)) { -if (!precise_br_compat (event)) -return -EOPNOTSUPP ; - -/* branch_sample_type is compatible */ - - }else { -/* -* user did not specify branch_sample_type -* -* For PEBS fixups, we capture all -* the branches at the priv level of the -* event. -*/ - *br_type =PERF_SAMPLE_BRANCH_ANY ; - -if (!event->attr.exclude_user) - *br_type |=PERF_SAMPLE_BRANCH_USER ; - -if (!event->attr.exclude_kernel) - *br_type |=PERF_SAMPLE_BRANCH_KERNEL ; - } + } +/* +* check that PEBS LBR correction does not conflict with +* whatever the user is asking with attr->branch_sample_type +*/ +if (event->attr.precise_ip >1 && x86_pmu.intel_cap.pebs_format <2 ) { +u64 *br_type = &event->attr.branch_sample_type; + +if (has_branch_stack (event)) { +if (!precise_br_compat (event)) +return -EOPNOTSUPP ; + +/* branch_sample_type is compatible */ + + }else { +/* +* user did not specify branch_sample_type +* +* For PEBS fixups, we capture all +* the branches at the priv level of the +* event. +*/ + *br_type =PERF_SAMPLE_BRANCH_ANY ; + +if (!event->attr.exclude_user) + *br_type |=PERF_SAMPLE_BRANCH_USER ; + +if (!event->attr.exclude_kernel) + *br_type |=PERF_SAMPLE_BRANCH_KERNEL ; } }
Signature · 1 line
1.8.3.2
tip-bot for Yan, Zheng
merge bot[tip:perf/core] perf/x86/intel: Re-organize code that implicitly enables LBR/PEBS
perf/x86/intel: Re-organize code that implicitly enables LBR/PEBS
Commit-ID: 4b854900995194601d767fcd112307b21ed278b2 Gitweb: http://git.kernel.org/tip/4b854900995194601d767fcd112307b21ed278b2 Author: Yan, Zheng <[email protected]> AuthorDate: Tue, 4 Nov 2014 21:56:08 -0500 Committer: Ingo Molnar <[email protected]> CommitDate: Wed, 18 Feb 2015 17:16:12 +0100
perf/x86/intel: Re-organize code that implicitly enables LBR/PEBS
Make later patch more readable, no logic change.
--- arch/x86/kernel/cpu/perf_event.c | 59 ++++++++++++++++++++-------------------- 1 file changed, 29 insertions(+), 30 deletions(-)
arch/x86/kernel/cpu/perf_event.c +29 -30
@@ -399,36 +399,35 @@ int x86_pmu_hw_config(struct perf_event *event)if (event->attr.precise_ip > precise)return -EOPNOTSUPP ; -/* -* check that PEBS LBR correction does not conflict with -* whatever the user is asking with attr->branch_sample_type -*/ -if (event->attr.precise_ip >1 && - x86_pmu.intel_cap.pebs_format <2 ) { -u64 *br_type = &event->attr.branch_sample_type; - -if (has_branch_stack (event)) { -if (!precise_br_compat (event)) -return -EOPNOTSUPP ; - -/* branch_sample_type is compatible */ - - }else { -/* -* user did not specify branch_sample_type -* -* For PEBS fixups, we capture all -* the branches at the priv level of the -* event. -*/ - *br_type =PERF_SAMPLE_BRANCH_ANY ; - -if (!event->attr.exclude_user) - *br_type |=PERF_SAMPLE_BRANCH_USER ; - -if (!event->attr.exclude_kernel) - *br_type |=PERF_SAMPLE_BRANCH_KERNEL ; - } + } +/* +* check that PEBS LBR correction does not conflict with +* whatever the user is asking with attr->branch_sample_type +*/ +if (event->attr.precise_ip >1 && x86_pmu.intel_cap.pebs_format <2 ) { +u64 *br_type = &event->attr.branch_sample_type; + +if (has_branch_stack (event)) { +if (!precise_br_compat (event)) +return -EOPNOTSUPP ; + +/* branch_sample_type is compatible */ + + }else { +/* +* user did not specify branch_sample_type +* +* For PEBS fixups, we capture all +* the branches at the priv level of the +* event. +*/ + *br_type =PERF_SAMPLE_BRANCH_ANY ; + +if (!event->attr.exclude_user) + *br_type |=PERF_SAMPLE_BRANCH_USER ; + +if (!event->attr.exclude_kernel) + *br_type |=PERF_SAMPLE_BRANCH_KERNEL ; } }
PATCH v7 13/17 perf, x86: enable LBR callstack when recording callchain
In reply to Kan LiangFrom: Yan, Zheng <[email protected]>
Only enable LBR callstack when user requires fp callgraph. The feature is not available when PERF_SAMPLE_BRANCH_STACK or PERF_SAMPLE_STACK_USER is required.
Also, this feature only affects how to get user callchain. The kernel callchain is always got by frame pointers.
--- arch/x86/kernel/cpu/perf_event.c | 18 ++++++++++++++++-- 1 file changed, 16 insertions(+), 2 deletions(-)
arch/x86/kernel/cpu/perf_event.c +16 -2
@@ -425,10 +425,24 @@ int x86_pmu_hw_config(struct perf_event *event)if (!event->attr.exclude_kernel) *br_type |=PERF_SAMPLE_BRANCH_KERNEL ; } - } + }else if (x86_pmu_has_lbr_callstack () && + (event->attr.sample_type &PERF_SAMPLE_CALLCHAIN ) && + !(event->attr.sample_type &PERF_SAMPLE_STACK_USER ) && + !has_branch_stack (event) && + !event->attr.exclude_user && + (event->attach_state &PERF_ATTACH_TASK )) { +/* +* user did not specify branch_sample_type, +* try using the LBR call stack facility to +* record call chains of user program. +*/ + event->attr.branch_sample_type = +PERF_SAMPLE_BRANCH_USER | +PERF_SAMPLE_BRANCH_CALL_STACK ; -if (event->attr.branch_sample_type &PERF_SAMPLE_BRANCH_CALL_STACK ) +/* needs PMU specific data to save LBR stack */ event->attach_state |=PERF_ATTACH_TASK_DATA ; + }/* * Generate PMC IRQs:
Signature · 1 line
1.8.3.2
Peter Zijlstra
maintainerRe: [PATCH V7 13/17] perf, x86: enable LBR callstack when recording callchain
Quoted 7 lines · Kan Liang
From: Yan, Zheng <[email protected]>
Only enable LBR callstack when user requires fp callgraph. The feature is not available when
PERF_SAMPLE_BRANCH_STACKorPERF_SAMPLE_STACK_USERis required.
Also, this feature only affects how to get user callchain. The kernel callchain is always got by frame pointers.
Since FP callchains should not change, this doesn't appear to make any sense either.
Re: [PATCH V7 13/17] perf, x86: enable LBR callstack when recording callchain
Quoted 11 lines · Peter Zijlstra
Quoted 7 lines · Kan Liang
From: Yan, Zheng <[email protected]>
Only enable LBR callstack when user requires fp callgraph. The feature is not available when
PERF_SAMPLE_BRANCH_STACKorPERF_SAMPLE_STACK_USERis required.
Also, this feature only affects how to get user callchain. The kernel callchain is always got by frame pointers.Since FP callchains should not change, this doesn't appear to make any sense either.
If I recall earlier discussion, the FP callchain are not changed. On HSW, when requesting
fp at the user level only, then the kernel automatically tries to use the LBR callstack mode.
Advantage is that the user app does not require frame-pointer or dwarf debug info to get
correct callchains with perf record. The downside is that LBR callstack does not work in
certain callchain corner cases.
The reason why using LBR call stack mode is restricted to user level only is because of
a bug in the LBR call stack hardware which forces the kernel to drop LBR_FREEZE_PMI.
In other words ,the LBR does not stop on counter overflow, thus it will be wiped out by
execution of kernel code leading to the PMU interrupt handler.
Peter Zijlstra
maintainerRe: [PATCH V7 13/17] perf, x86: enable LBR callstack when recording callchain
Quoted 13 lines · Stephane Eranian
Quoted 11 lines · Peter Zijlstra
Quoted 7 lines · Kan Liang
From: Yan, Zheng <[email protected]>
Only enable LBR callstack when user requires fp callgraph. The feature is not available when
PERF_SAMPLE_BRANCH_STACKorPERF_SAMPLE_STACK_USERis required.
Also, this feature only affects how to get user callchain. The kernel callchain is always got by frame pointers.Since FP callchains should not change, this doesn't appear to make any sense either.
Quoted 6 lines
If I recall earlier discussion, the FP callchain are not changed. On HSW, when requesting fp at the user level only, then the kernel automatically tries to use the LBR callstack mode. Advantage is that the user app does not require frame-pointer or dwarf debug info to get correct callchains with perf record. The downside is that LBR callstack does not work in certain callchain corner cases.
But this patch changes the FP callchain interface. I see no need of that. We already have multiple independent callchain options (FP and Dwarf) adding a third option should also be independent (LBR).
Allowing all 3 at the same time allows for identifying those corner cases.
That is I simply don't see a good reason intertwine these things at the interface level. All it does is reduce options. Would it not be 'nice' to allow both FP and LBR at the same time?
Re: [PATCH V7 13/17] perf, x86: enable LBR callstack when recording callchain
Quoted 25 lines · Peter Zijlstra
Quoted 13 lines · Stephane Eranian
Quoted 11 lines · Peter Zijlstra
Quoted 7 lines · Kan Liang
From: Yan, Zheng <[email protected]>
Only enable LBR callstack when user requires fp callgraph. The feature is not available when
PERF_SAMPLE_BRANCH_STACKorPERF_SAMPLE_STACK_USERis required.
Also, this feature only affects how to get user callchain. The kernel callchain is always got by frame pointers.Since FP callchains should not change, this doesn't appear to make any sense either.
Quoted 6 lines
If I recall earlier discussion, the FP callchain are not changed. On HSW, when requesting fp at the user level only, then the kernel automatically tries to use the LBR callstack mode. Advantage is that the user app does not require frame-pointer or dwarf debug info to get correct callchains with perf record. The downside is that LBR callstack does not work in certain callchain corner cases.
But this patch changes the FP callchain interface. I see no need of that. We already have multiple independent callchain options (FP and Dwarf) adding a third option should also be independent (LBR).
Quoted 6 lines
Allowing all 3 at the same time allows for identifying those corner cases.
That is I simply don't see a good reason intertwine these things at the interface level. All it does is reduce options. Would it not be 'nice' to allow both FP and LBR at the same time?
Yes, but I wonder how would the tool sort this out if you have FP and LBR for each sample.
My understanding of the patch is that it does not change the user interface, it changes the way callchains are gathered by the kernel on HSW.
Is there explicit mention in the API that CALLCHAIN is relying on FP?
I think in general it would be better for tools to know which low-level mechanism
is used to better interpret the results and especially be aware of the limitations of
each mechanism.
I think the patch is trying some auto-promotion of CALLCHAIN to FP based on the belief it is better in most cases. It reminds me of the discussion about precise mode. Why not default to precise for all events that support it?
I would be okay if the patch was introducing the 3rd mode for callchains.
Peter Zijlstra
maintainerRe: [PATCH V7 13/17] perf, x86: enable LBR callstack when recording callchain
Quoted 2 lines · Stephane Eranian
Yes, but I wonder how would the tool sort this out if you have FP and LBR for each sample.
That's the tools 'problem'. It currently can already have FP and Dwarf bits. And it does not need to request all of them.
Quoted 2 lines
My understanding of the patch is that it does not change the user interface, it changes the way callchains are gathered by the kernel on HSW.
I was under the impression it did change, but that shows how well the Changelog explained things I suppose :/
Quoted 1 line
Is there explicit mention in the API that CALLCHAIN is relying on FP?
Don't think so. Although I would much prefer if it uses a single method per arch across both kernel and user space. For x86 that is FP (since that's the only method available to the kernel).
Quoted 3 lines
I think in general it would be better for tools to know which low-level mechanism is used to better interpret the results and especially be aware of the limitations of each mechanism.
Agreed.
Quoted 2 lines
I think the patch is trying some auto-promotion of CALLCHAIN to FP based on the belief it is better in most cases.
We're all more familiar with FP, and it doesn't have the obvious problem if only 16 entries. I've worked on quite a bit of software that had much deeper callchains -- yay for recursive algorithms and/or C++.
With a bit of care FP can be 'perfect', although Andi likes to point out that glibc isn't and often wrecks FP :-(
Quoted 2 lines
It reminds me of the discussion about precise mode. Why not default to precise for all events that support it?
I've no idea where that discussion stranded.
Quoted 1 line
I would be okay if the patch was introducing the 3rd mode for callchains.
Right, I would prefer that (as should be clear by now), this would allow running with two (or even all three) and compare results.
Re: [PATCH V7 13/17] perf, x86: enable LBR callstack when recording callchain
Quoted 7 lines · Peter Zijlstra
Quoted 2 lines · Stephane Eranian
Yes, but I wonder how would the tool sort this out if you have FP and LBR for each sample.
That's the tools 'problem'. It currently can already have FP and Dwarf bits. And it does not need to request all of them.
I was thinking about the case where the tool would request both FP and LBR at the same to try and construct a complete callstack. Not sure how the tool could do that.
Quoted 6 lines
Quoted 2 lines
My understanding of the patch is that it does not change the user interface, it changes the way callchains are gathered by the kernel on HSW.
I was under the impression it did change, but that shows how well the Changelog explained things I suppose :/
With the current patches (or the latest version I looked at), there was no way to request explicitly LBR mode. It was automatic if CALLCHAIN + user mode only sampling.
Quoted 6 lines
Quoted 1 line
Is there explicit mention in the API that CALLCHAIN is relying on FP?
Don't think so. Although I would much prefer if it uses a single method per arch across both kernel and user space. For x86 that is FP (since that's the only method available to the kernel).
I tend to agree here. The problem with FP is that it is not easy to figure out how a binary has been compiled. Getting valid FP callchains for large binaries using lots of shared libraries is very challenging. All libraries must be compiled with FP. It is not easy to test if FP was compiled in. There is no ELF header flag for this. Need to inspect the x86 asm and look at function prologues.
This is where LBR has an advantage, it works regardless of how a binaries and shared libs have been compiled. That is why this is a good (or some would say better) approach which is using hardware assist.
Quoted 4 lines
Quoted 3 lines
I think in general it would be better for tools to know which low-level mechanism is used to better interpret the results and especially be aware of the limitations of each mechanism.
Quoted 9 lines
Agreed.
Quoted 2 lines
I think the patch is trying some auto-promotion of CALLCHAIN to FP based on the belief it is better in most cases.
We're all more familiar with FP, and it doesn't have the obvious problem if only 16 entries. I've worked on quite a bit of software that had much deeper callchains -- yay for recursive algorithms and/or C++.
Yes, this is true too. But it is not so clear to me if people really care about top of callchains that much. I think usually 2-6 would probably yield enough useful info.
LBR callstack fails for leaf function optimization. Where the callee does not return to its caller but instead to the caller's caller. That is the one case I know about. There are others I believe.
Quoted 3 lines
With a bit of care FP can be 'perfect', although Andi likes to point out that glibc isn't and often wrecks FP :-(
Especially any hand-crafted assembly...
Quoted 9 lines
Quoted 2 lines
It reminds me of the discussion about precise mode. Why not default to precise for all events that support it?
I've no idea where that discussion stranded.
Quoted 1 line
I would be okay if the patch was introducing the 3rd mode for callchains.
Right, I would prefer that (as should be clear by now), this would allow running with two (or even all three) and compare results.
I don't think it would be very hard to modify the patch set to make that 3rd mode visible. Just need to make that new PERF_RECORD_* type visible to user and modify the compatibility checks.
Peter Zijlstra
maintainerRe: [PATCH V7 13/17] perf, x86: enable LBR callstack when recording callchain
Quoted 6 lines · Stephane Eranian
I tend to agree here. The problem with FP is that it is not easy to figure out how a binary has been compiled. Getting valid FP callchains for large binaries using lots of shared libraries is very challenging. All libraries must be compiled with FP. It is not easy to test if FP was compiled in. There is no ELF header flag for this. Need to inspect the x86 asm and look at function prologues.
build world ftw :-), I realize that on many distros this is hard, but in some environments its really rather easy.
But yes, its tedious without the capability to build world.
Quoted 4 lines
This is where LBR has an advantage, it works regardless of how a binaries and shared libs have been compiled. That is why this is a good (or some would say better) approach which is using hardware assist.
Right, but only because we made of mess of the thing in the first place :-/
Quoted 7 lines
Quoted 4 lines
We're all more familiar with FP, and it doesn't have the obvious problem if only 16 entries. I've worked on quite a bit of software that had much deeper callchains -- yay for recursive algorithms and/or C++.
Yes, this is true too. But it is not so clear to me if people really care about top of callchains that much. I think usually 2-6 would probably yield enough useful info.
Right, with C++ if you have a particularly gruesome object hierarchy a simple constructor can blow your entire 16 calls out the window, so when you then get around to doing actual work there's nothing left.
But yes, that should not be too common I think.
Quoted 3 lines
LBR callstack fails for leaf function optimization. Where the callee does not return to its caller but instead to the caller's caller. That is the one case I know about. There are others I believe.
Yeah, tail call and jong jump might also confuse the thing, I can't remember.
Quoted 4 lines
Quoted 3 lines
With a bit of care FP can be 'perfect', although Andi likes to point out that glibc isn't and often wrecks FP :-(
Especially any hand-crafted assembly...
Well, it doesn't need to. But yes its easy to do wrong in that case.
Quoted 3 lines
I don't think it would be very hard to modify the patch set to make that 3rd mode visible. Just need to make that new PERF_RECORD_* type visible to user and modify the compatibility checks.
There's no new RECORD type afaict; would not the relatively simple patch I proposed be enough? It exposes PERF_SAMPLE_BRANCH_CALL_STACK and you'd get the data through the normal PERF_SAMPLE_BRANCH_STACK output.
RE: [PATCH V7 13/17] perf, x86: enable LBR callstack when recording callchain
In reply to Stephane EranianThanks for your comments. There are lots of discussion about the patch. It's hard to reply them one by one. So I try to reply all the concerns here.
The patchset doesn't try to introduce the 3rd independent callchain option That's because LBR callstack has some limitations (only available for user callchain, only 16 entries, cannot collect branch info at the same time, etc). So it’s designed as a supplement/extension of FP callchain options. It rely on FP, but can provide the callstack info when FP isn't available in some cases which Stephane and Andi mentioned.
Since it's not an independent callchain options, I didn't provide an explicit option for user to enable it.
However, I provide an option in perf report to show the LBR userspace callchain and FP callchain. That's the main difference between Zheng's previous patch and the latest patch.
Here are how it works.
When the user enable FP callchain on HSW, the kernel implicitly enable both LBR callstack and FP.
Zheng's previous patch does everything in kernel. If FP is not available, then LBR callstack data will be used implicitly. If FP is available, then LBR callstack data will be discarded.
While the latest patch expose both LBR callstack and FP data to user tool. A new option for perf report is introduced. The user can dump the callchain from either lbr or fp if they are both available.
E.g.
perf report --call-graph fp (both userspace and kernel callchain from FP) perf report --call-graph lbr (userspace callchain from LBR, kernel from FP)
Quoted 7 lines
Quoted 4 lines · Peter Zijlstra
Quoted 2 lines · Stephane Eranian
Yes, but I wonder how would the tool sort this out if you have FP and LBR for each sample.
Quoted 6 lines
Quoted 3 lines
That's the tools 'problem'. It currently can already have FP and Dwarf bits. And it does not need to request all of them.
I was thinking about the case where the tool would request both FP and LBR at the same to try and construct a complete callstack. Not sure how the tool could do that.
Both LBR and FP data are pushed to the tool. User can use newly introduced perf report call-graph option to choose how to construct the callstack.
Quoted 12 lines
Quoted 3 lines
Quoted 3 lines
My understanding of the patch is that it does not change the user interface, it changes the way callchains are gathered by the kernel on
HSW.
Quoted 4 lines
I was under the impression it did change, but that shows how well the Changelog explained things I suppose :/
With the current patches (or the latest version I looked at), there was no way to request explicitly LBR mode. It was automatic if CALLCHAIN + user mode only sampling.
Yes, currently there is no way to request explicitly LBR mode.
Quoted 13 lines
Quoted 6 lines
Quoted 1 line
Is there explicit mention in the API that CALLCHAIN is relying on FP?
Don't think so. Although I would much prefer if it uses a single method per arch across both kernel and user space. For x86 that is FP (since that's the only method available to the kernel).
I tend to agree here. The problem with FP is that it is not easy to figure out how a binary has been compiled. Getting valid FP callchains for large binaries using lots of shared libraries is very challenging. All libraries must be compiled with FP. It is not easy to test if FP was compiled in. There is no ELF header flag for this. Need to inspect the x86 asm and look at function prologues.
Quoted 4 lines
This is where LBR has an advantage, it works regardless of how a binaries and shared libs have been compiled. That is why this is a good (or some would say better) approach which is using hardware assist.
Agreed. LBR is a very good supplement.
Quoted 32 lines
Quoted 4 lines
Quoted 3 lines
I think in general it would be better for tools to know which low-level mechanism is used to better interpret the results and especially be aware of the limitations of each mechanism.
Quoted 8 lines
Agreed.
Quoted 2 lines
I think the patch is trying some auto-promotion of CALLCHAIN to FP based on the belief it is better in most cases.
We're all more familiar with FP, and it doesn't have the obvious problem if only 16 entries. I've worked on quite a bit of software that had much deeper callchains -- yay for recursive algorithms and/or
C++.
Quoted 1 line
Yes, this is true too. But it is not so clear to me if people really care about top of callchains that much. I think usually 2-6 would probably yield enough useful info.
LBR callstack fails for leaf function optimization. Where the callee does not return to its caller but instead to the caller's caller. That is the one case I know about. There are others I believe.
Quoted 3 lines
With a bit of care FP can be 'perfect', although Andi likes to point out that glibc isn't and often wrecks FP :-(
Especially any hand-crafted assembly...
Quoted 5 lines
Quoted 2 lines
It reminds me of the discussion about precise mode. Why not default to precise for all events that support it?
I've no idea where that discussion stranded.
Quoted 8 lines
Quoted 4 lines
Quoted 1 line
I would be okay if the patch was introducing the 3rd mode for callchains.
Right, I would prefer that (as should be clear by now), this would allow running with two (or even all three) and compare results.
I don't think it would be very hard to modify the patch set to make that 3rd mode visible. Just need to make that new PERF_RECORD_* type visible to user and modify the compatibility checks.
It's not hard. But LBR is not an independent callchain options. It's better to be a supplement of FP. Otherwise, it may confuse the user. He enables the BRANCH_CALL_STACK, but the data is partly or even not at all from hardware.
Thanks,
Kan ���{.n�+�������+%�����ݶ��w��{.n�+����{��G�����{ay�ʇڙ�,j��f���h��������z_�(�階�ݢj"���m������G������?����&���~��iO��z��v�^�m����������?�I�
Peter Zijlstra
maintainerRe: [PATCH V7 13/17] perf, x86: enable LBR callstack when recording callchain
Quoted 7 lines · Kan
Quoted 3 lines
I don't think it would be very hard to modify the patch set to make that 3rd mode visible. Just need to make that new PERF_RECORD_* type visible to user and modify the compatibility checks.
It's not hard. But LBR is not an independent callchain options. It's better to be a supplement of FP. Otherwise, it may confuse the user. He enables the
BRANCH_CALL_STACK, but the data is partly or even not at all from hardware.
What the user sees is up to userspace. It should not be forced by the kernel/user interface.
Re: [PATCH V7 13/17] perf, x86: enable LBR callstack when recording callchain
Quoted 11 lines · Peter Zijlstra
Quoted 7 lines · Kan
Quoted 3 lines
I don't think it would be very hard to modify the patch set to make that 3rd mode visible. Just need to make that new PERF_RECORD_* type visible to user and modify the compatibility checks.
It's not hard. But LBR is not an independent callchain options. It's better to be a supplement of FP. Otherwise, it may confuse the user. He enables the
BRANCH_CALL_STACK, but the data is partly or even not at all from hardware.What the user sees is up to userspace. It should not be forced by the kernel/user interface.
The original idea was to abstract it inside the kernel. Unlike dwarf the LBR callstack is simple enough that it can be easily abstracted. If you don't want to do that yes then handling it in the user tools is the right way.
-Andi
Signature · 1 line
[email protected] -- Speaking for myself only
Re: [PATCH V7 13/17] perf, x86: enable LBR callstack when recording callchain
In reply to Stephane EranianQuoted 3 lines
LBR callstack fails for leaf function optimization. Where the callee does not return to its caller but instead to the caller's caller. That is the one case I know about. There are others I believe.
No it should work fine for this case. You just don't see the tail call, but the call stack does not get out of sync, so future calls work fine. It's the same as with frame pointers or even dwarf.
Typical cases that throw it off are throwing exceptions or user space context switching.
One somewhat common case that used to throw it off was the call 1f ; 1: pop %ebx
older 32bit binaries used to do to get the PIC offset. That has been fixed in newer compilers by using an out of line function (and also Broadwell has a workaround for this)
-Andi
Signature · 1 line
[email protected] -- Speaking for myself only
Re: [PATCH V7 13/17] perf, x86: enable LBR callstack when recording callchain
In reply to Stephane EranianQuoted 4 lines
The reason why using LBR call stack mode is restricted to user level only is because of
a bug in the LBR call stack hardware which forces the kernel to dropLBR_FREEZE_PMI.
It works with PEBS events, just not with non PEBS (the patch currently does not implement this distinction and I'm not sure it's worth it)
Quoted 3 lines
In other words ,the LBR does not stop on counter overflow, thus it will be wiped out by
execution of kernel code leading to the PMU interrupt handler.
It stops, but it takes some time to stop so the call-return stack can get out of sync.
-Andi
Signature · 1 line
[email protected] -- Speaking for myself only
PATCH v7 14/17 perf, x86: disable FREEZE_LBRS_ON_PMI when LBR operates in callstack mode
In reply to Kan LiangFrom: Yan, Zheng <[email protected]>
LBR callstack is designed for PEBS, It does not work well with FREEZE_LBRS_ON_PMI for non PEBS event. If FREEZE_LBRS_ON_PMI is set for non PEBS event, PMIs near call/return instructions may cause superfluous increase/decrease of LBR_TOS.
This patch modifies __intel_pmu_lbr_enable() to not enable FREEZE_LBRS_ON_PMI when LBR operates in callstack mode. We currently don't use LBR callstack to capture kernel space callchain, so disabling FREEZE_LBRS_ON_PMI should not be a problem.
--- arch/x86/kernel/cpu/perf_event_intel_lbr.c | 17 +++++++++++++---- 1 file changed, 13 insertions(+), 4 deletions(-)
arch/x86/kernel/cpu/perf_event_intel_lbr.c +13 -4
@@ -131,14 +131,23 @@ static void intel_pmu_lbr_filter(struct cpu_hw_events *cpuc);static void __intel_pmu_lbr_enable (void ) { -u64 debugctl;struct cpu_hw_events *cpuc =this_cpu_ptr (&cpu_hw_events); +u64 debugctl, lbr_select =0 ; -if (cpuc->lbr_sel) -wrmsrl (MSR_LBR_SELECT , cpuc->lbr_sel->config); +if (cpuc->lbr_sel) { + lbr_select = cpuc->lbr_sel->config; +wrmsrl (MSR_LBR_SELECT , lbr_select); + }rdmsrl (MSR_IA32_DEBUGCTLMSR , debugctl); - debugctl |= (DEBUGCTLMSR_LBR |DEBUGCTLMSR_FREEZE_LBRS_ON_PMI ); + debugctl |=DEBUGCTLMSR_LBR ; +/* +* LBR callstack does not work well with FREEZE_LBRS_ON_PMI. +* If FREEZE_LBRS_ON_PMI is set, PMI near call/return instructions +* may cause superfluous increase/decrease of LBR_TOS. +*/ +if (!(lbr_select &LBR_CALL_STACK )) + debugctl |=DEBUGCTLMSR_FREEZE_LBRS_ON_PMI ;wrmsrl (MSR_IA32_DEBUGCTLMSR , debugctl); }
Signature · 1 line
1.8.3.2
tip-bot for Yan, Zheng
merge bot[tip:perf/core] perf/x86/intel: Disable FREEZE_LBRS_ON_PMI when LBR operates in callstack mode
perf/x86/intel: Disable FREEZE_LBRS_ON_PMI when LBR operates in callstack mode
Commit-ID: 2c70d0086e4e9e2440f0f78098090f32bde14277 Gitweb: http://git.kernel.org/tip/2c70d0086e4e9e2440f0f78098090f32bde14277 Author: Yan, Zheng <[email protected]> AuthorDate: Tue, 4 Nov 2014 21:56:10 -0500 Committer: Ingo Molnar <[email protected]> CommitDate: Wed, 18 Feb 2015 17:16:13 +0100
perf/x86/intel: Disable FREEZE_LBRS_ON_PMI when LBR operates in callstack mode
LBR callstack is designed for PEBS, It does not work well with FREEZE_LBRS_ON_PMI for non PEBS event. If FREEZE_LBRS_ON_PMI is set for non PEBS event, PMIs near call/return instructions may cause superfluous increase/decrease of LBR_TOS.
This patch modifies __intel_pmu_lbr_enable() to not enable FREEZE_LBRS_ON_PMI when LBR operates in callstack mode. We currently don't use LBR callstack to capture kernel space callchain, so disabling FREEZE_LBRS_ON_PMI should not be a problem.
--- arch/x86/kernel/cpu/perf_event_intel_lbr.c | 17 +++++++++++++---- 1 file changed, 13 insertions(+), 4 deletions(-)
arch/x86/kernel/cpu/perf_event_intel_lbr.c +13 -4
@@ -131,14 +131,23 @@ static void intel_pmu_lbr_filter(struct cpu_hw_events *cpuc);static void __intel_pmu_lbr_enable (void ) { -u64 debugctl;struct cpu_hw_events *cpuc =this_cpu_ptr (&cpu_hw_events); +u64 debugctl, lbr_select =0 ; -if (cpuc->lbr_sel) -wrmsrl (MSR_LBR_SELECT , cpuc->lbr_sel->config); +if (cpuc->lbr_sel) { + lbr_select = cpuc->lbr_sel->config; +wrmsrl (MSR_LBR_SELECT , lbr_select); + }rdmsrl (MSR_IA32_DEBUGCTLMSR , debugctl); - debugctl |= (DEBUGCTLMSR_LBR |DEBUGCTLMSR_FREEZE_LBRS_ON_PMI ); + debugctl |=DEBUGCTLMSR_LBR ; +/* +* LBR callstack does not work well with FREEZE_LBRS_ON_PMI. +* If FREEZE_LBRS_ON_PMI is set, PMI near call/return instructions +* may cause superfluous increase/decrease of LBR_TOS. +*/ +if (!(lbr_select &LBR_CALL_STACK )) + debugctl |=DEBUGCTLMSR_FREEZE_LBRS_ON_PMI ;wrmsrl (MSR_IA32_DEBUGCTLMSR , debugctl); }
PATCH v7 15/17 perf, x86: Discard zero length call entries in LBR call stack
In reply to Kan LiangFrom: Yan, Zheng <[email protected]>
"Zero length call" uses the attribute of the call instruction to push the immediate instruction pointer on to the stack and then pops off that address into a register. This is accomplished without any matching return instruction. It confuses the hardware and make the recorded call stack incorrect.
We can partially resolve this issue by: decode call instructions and discard any zero length call entry in the LBR stack.
--- arch/x86/kernel/cpu/perf_event_intel_lbr.c | 13 +++++++++++-- 1 file changed, 11 insertions(+), 2 deletions(-)
arch/x86/kernel/cpu/perf_event_intel_lbr.c +11 -2
@@ -94,7 +94,8 @@ enum {X86_BR_ABORT =1 <<12 ,/* transaction abort */ X86_BR_IN_TX =1 <<13 ,/* in transaction */ X86_BR_NO_TX =1 <<14 ,/* not in transaction */ - X86_BR_CALL_STACK = 1 << 15,/* call stack */ +X86_BR_ZERO_CALL =1 <<15 ,/* zero length call */ + X86_BR_CALL_STACK = 1 << 16,/* call stack */ };#define X86_BR_PLM (X86_BR_USER | X86_BR_KERNEL)
@@ -111,13 +112,15 @@ enum { X86_BR_JMP |\ X86_BR_IRQ |\ X86_BR_ABORT |\ - X86_BR_IND_CALL) + X86_BR_IND_CALL |\ + X86_BR_ZERO_CALL)#define X86_BR_ALL (X86_BR_PLM | X86_BR_ANY)#define X86_BR_ANY_CALL \ (X86_BR_CALL |\ X86_BR_IND_CALL |\ + X86_BR_ZERO_CALL |\ X86_BR_SYSCALL |\ X86_BR_IRQ |\ X86_BR_INT)
@@ -689,6 +692,12 @@ static int branch_type(unsigned long from, unsigned long to, int abort) ret =X86_BR_INT ;break ;case 0xe8 :/* call near rel */ +insn_get_immediate (&insn); +if (insn.immediate1.value ==0 ) { +/* zero length call */ + ret =X86_BR_ZERO_CALL ; +break ; + }case 0x9a :/* call far absolute */ ret =X86_BR_CALL ;break ;
Signature · 1 line
1.8.3.2
tip-bot for Yan, Zheng
merge bot[tip:perf/core] perf/x86/intel: Discard zero length call entries in LBR call stack
perf/x86/intel: Discard zero length call entries in LBR call stack
Commit-ID: aa54ae9b87b83af7edabcc34a299e7e014609af4 Gitweb: http://git.kernel.org/tip/aa54ae9b87b83af7edabcc34a299e7e014609af4 Author: Yan, Zheng <[email protected]> AuthorDate: Tue, 4 Nov 2014 21:56:11 -0500 Committer: Ingo Molnar <[email protected]> CommitDate: Wed, 18 Feb 2015 17:16:14 +0100
perf/x86/intel: Discard zero length call entries in LBR call stack
"Zero length call" uses the attribute of the call instruction to push the immediate instruction pointer on to the stack and then pops off that address into a register. This is accomplished without any matching return instruction. It confuses the hardware and make the recorded call stack incorrect.
We can partially resolve this issue by: decode call instructions and discard any zero length call entry in the LBR stack.
--- arch/x86/kernel/cpu/perf_event_intel_lbr.c | 13 +++++++++++-- 1 file changed, 11 insertions(+), 2 deletions(-)
arch/x86/kernel/cpu/perf_event_intel_lbr.c +11 -2
@@ -94,7 +94,8 @@ enum {X86_BR_ABORT =1 <<12 ,/* transaction abort */ X86_BR_IN_TX =1 <<13 ,/* in transaction */ X86_BR_NO_TX =1 <<14 ,/* not in transaction */ - X86_BR_CALL_STACK = 1 << 15,/* call stack */ +X86_BR_ZERO_CALL =1 <<15 ,/* zero length call */ + X86_BR_CALL_STACK = 1 << 16,/* call stack */ };#define X86_BR_PLM (X86_BR_USER | X86_BR_KERNEL)
@@ -111,13 +112,15 @@ enum { X86_BR_JMP |\ X86_BR_IRQ |\ X86_BR_ABORT |\ - X86_BR_IND_CALL) + X86_BR_IND_CALL |\ + X86_BR_ZERO_CALL)#define X86_BR_ALL (X86_BR_PLM | X86_BR_ANY)#define X86_BR_ANY_CALL \ (X86_BR_CALL |\ X86_BR_IND_CALL |\ + X86_BR_ZERO_CALL |\ X86_BR_SYSCALL |\ X86_BR_IRQ |\ X86_BR_INT)
@@ -702,6 +705,12 @@ static int branch_type(unsigned long from, unsigned long to, int abort) ret =X86_BR_INT ;break ;case 0xe8 :/* call near rel */ +insn_get_immediate (&insn); +if (insn.immediate1.value ==0 ) { +/* zero length call */ + ret =X86_BR_ZERO_CALL ; +break ; + }case 0x9a :/* call far absolute */ ret =X86_BR_CALL ;break ;
PATCH v7 16/17 perf tools: handle LBR call stack data
In reply to Kan LiangFrom: Kan Liang <[email protected]>
The LBR call stack data will be output as PERF_SAMPLE_BRANCH_STACK data format. ip_callchain is changed to show available callchain source. LBR call stack also need to be shown in user space.
Perf test also changes accordingly.
--- tools/perf/tests/hists_cumulate.c | 20 ++++++++++---------- tools/perf/tests/sample-parsing.c | 2 +- tools/perf/util/event.h | 8 ++++++++ tools/perf/util/evsel.c | 21 +++++++++++++-------- 4 files changed, 32 insertions(+), 19 deletions(-)
tools/perf/tests/hists_cumulate.c +10 -10
@@ -48,29 +48,29 @@ static struct sample fake_samples[] = {*/ static u64 fake_callchains[][10 ] = {/* schedule => run_command => main */ - {3 ,FAKE_IP_KERNEL_SCHEDULE ,FAKE_IP_PERF_RUN_COMMAND ,FAKE_IP_PERF_MAIN , }, + {1 ,3 ,FAKE_IP_KERNEL_SCHEDULE ,FAKE_IP_PERF_RUN_COMMAND ,FAKE_IP_PERF_MAIN , },/* main */ - {1 ,FAKE_IP_PERF_MAIN , }, + {1 ,1 ,FAKE_IP_PERF_MAIN , },/* cmd_record => run_command => main */ - {3 ,FAKE_IP_PERF_CMD_RECORD ,FAKE_IP_PERF_RUN_COMMAND ,FAKE_IP_PERF_MAIN , }, + {1 ,3 ,FAKE_IP_PERF_CMD_RECORD ,FAKE_IP_PERF_RUN_COMMAND ,FAKE_IP_PERF_MAIN , },/* malloc => cmd_record => run_command => main */ - {4 ,FAKE_IP_LIBC_MALLOC ,FAKE_IP_PERF_CMD_RECORD ,FAKE_IP_PERF_RUN_COMMAND , + {1 ,4 ,FAKE_IP_LIBC_MALLOC ,FAKE_IP_PERF_CMD_RECORD ,FAKE_IP_PERF_RUN_COMMAND ,FAKE_IP_PERF_MAIN , },/* free => cmd_record => run_command => main */ - {4 ,FAKE_IP_LIBC_FREE ,FAKE_IP_PERF_CMD_RECORD ,FAKE_IP_PERF_RUN_COMMAND , + {1 ,4 ,FAKE_IP_LIBC_FREE ,FAKE_IP_PERF_CMD_RECORD ,FAKE_IP_PERF_RUN_COMMAND ,FAKE_IP_PERF_MAIN , },/* main */ - {1 ,FAKE_IP_PERF_MAIN , }, + {1 ,1 ,FAKE_IP_PERF_MAIN , },/* page_fault => sys_perf_event_open => run_command => main */ - {4 ,FAKE_IP_KERNEL_PAGE_FAULT ,FAKE_IP_KERNEL_SYS_PERF_EVENT_OPEN , + {1 ,4 ,FAKE_IP_KERNEL_PAGE_FAULT ,FAKE_IP_KERNEL_SYS_PERF_EVENT_OPEN ,FAKE_IP_PERF_RUN_COMMAND ,FAKE_IP_PERF_MAIN , },/* main */ - {1 ,FAKE_IP_BASH_MAIN , }, + {1 ,1 ,FAKE_IP_BASH_MAIN , },/* xmalloc => malloc => xmalloc => malloc => xmalloc => main */ - {6 ,FAKE_IP_BASH_XMALLOC ,FAKE_IP_LIBC_MALLOC ,FAKE_IP_BASH_XMALLOC , + {1 ,6 ,FAKE_IP_BASH_XMALLOC ,FAKE_IP_LIBC_MALLOC ,FAKE_IP_BASH_XMALLOC ,FAKE_IP_LIBC_MALLOC ,FAKE_IP_BASH_XMALLOC ,FAKE_IP_BASH_MAIN , },/* page_fault => malloc => main */ - {3 ,FAKE_IP_KERNEL_PAGE_FAULT ,FAKE_IP_LIBC_MALLOC ,FAKE_IP_BASH_MAIN , }, + {1 ,3 ,FAKE_IP_KERNEL_PAGE_FAULT ,FAKE_IP_LIBC_MALLOC ,FAKE_IP_BASH_MAIN , }, };static int add_hist_entries (struct hists *hists,struct machine *machine)
tools/perf/tests/sample-parsing.c +1 -1
@@ -145,7 +145,7 @@ static int do_test(u64 sample_type, u64 sample_regs_user, u64 read_format)u64 data[64 ]; } callchain = {/* 3 ips */ - .data = {3, 201, 202, 203}, + .data = {1, 3, 201, 202, 203}, };union {struct branch_stack branch_stack;
tools/perf/util/event.h +8 -0
@@ -119,7 +119,15 @@ struct sample_read { }; }; +/* +* From Haswell, the existing Last Branch Record facility can +* also be used to record call chains. +* source: indicates the available call chains source. +*/ +#define PERF_FP_CALLCHAIN 0x01 +#define PERF_LBR_CALLCHAIN 0x02struct ip_callchain { +u64 source;u64 nr;u64 ips[0 ]; };
tools/perf/util/evsel.c +13 -8
@@ -1028,7 +1028,6 @@ static size_t perf_event_attr__fprintf(struct perf_event_attr *attr, FILE *fp) ret +=PRINT_ATTR2 (exclude_host, exclude_guest); ret +=PRINT_ATTR2N ("excl.callchain_kern" , exclude_callchain_kernel,"excl.callchain_user" , exclude_callchain_user); - ret +=PRINT_ATTR_U32 (wakeup_events); ret +=PRINT_ATTR_U32 (wakeup_watermark); ret +=PRINT_ATTR_X32 (bp_type);
@@ -1440,10 +1439,10 @@ int perf_evsel__parse_sample(struct perf_evsel *evsel, union perf_event *event,const u64 max_callchain_nr =UINT64_MAX /sizeof (u64);OVERFLOW_CHECK_u64 (array); - data->callchain = (struct ip_callchain *)array++; + data->callchain = (struct ip_callchain *)array;if (data->callchain->nr > max_callchain_nr)return -EFAULT ; - sz = data->callchain->nr *sizeof (u64); + sz = (data->callchain->nr +2 ) *sizeof (u64);OVERFLOW_CHECK (array, sz, max_size); array = (void *)array + sz; }
@@ -1466,7 +1465,9 @@ int perf_evsel__parse_sample(struct perf_evsel *evsel, union perf_event *event, array = (void *)array + data->raw_size; } -if (type &PERF_SAMPLE_BRANCH_STACK ) { +if ((type &PERF_SAMPLE_BRANCH_STACK ) || + (data->callchain && + (data->callchain->source &PERF_LBR_CALLCHAIN ))) {const u64 max_branch_nr =UINT64_MAX /sizeof (struct branch_entry );
@@ -1590,7 +1591,7 @@ size_t perf_event__sample_event_size(const struct perf_sample *sample, u64 type, }if (type &PERF_SAMPLE_CALLCHAIN ) { - sz = (sample->callchain->nr +1 ) *sizeof (u64); + sz = (sample->callchain->nr +2 ) *sizeof (u64); result += sz; }
@@ -1599,7 +1600,9 @@ size_t perf_event__sample_event_size(const struct perf_sample *sample, u64 type, result += sample->raw_size; } -if (type &PERF_SAMPLE_BRANCH_STACK ) { +if ((type &PERF_SAMPLE_BRANCH_STACK ) || + (sample->callchain && + (sample->callchain->source &PERF_LBR_CALLCHAIN ))) { sz = sample->branch_stack->nr *sizeof (struct branch_entry ); sz +=sizeof (u64); result += sz;
@@ -1745,7 +1748,7 @@ int perf_event__synthesize_sample(union perf_event *event, u64 type, }if (type &PERF_SAMPLE_CALLCHAIN ) { - sz = (sample->callchain->nr +1 ) *sizeof (u64); + sz = (sample->callchain->nr +2 ) *sizeof (u64);memcpy (array, sample->callchain, sz); array = (void *)array + sz; }
@@ -1768,7 +1771,9 @@ int perf_event__synthesize_sample(union perf_event *event, u64 type, array = (void *)array + sample->raw_size; } -if (type &PERF_SAMPLE_BRANCH_STACK ) { +if ((type &PERF_SAMPLE_BRANCH_STACK ) || + (sample->callchain && + (sample->callchain->source &PERF_LBR_CALLCHAIN ))) { sz = sample->branch_stack->nr *sizeof (struct branch_entry ); sz +=sizeof (u64);memcpy (array, sample->branch_stack, sz);
Signature · 1 line
1.8.3.2
PATCH v7 17/17 perf tools: choose to dump callchain from LBR and FP
In reply to Kan LiangFrom: Kan Liang <[email protected]>
Extend call-graph option in perf report to support callchain source (fp or lbr).
The default value is fp. It means that frame pointers is preferred call chain source. If it isn't available, lbr data will be used then. If the value is set to lbr, it means lbr data is preferred call chain source. If lbr data isn't available, try fp data then.
--- tools/perf/builtin-report.c | 8 +- tools/perf/util/callchain.c | 18 +++- tools/perf/util/callchain.h | 6 ++ tools/perf/util/machine.c | 198 ++++++++++++++++++++++++++++++-------------- tools/perf/util/session.c | 34 +++++++- 5 files changed, 194 insertions(+), 70 deletions(-)
tools/perf/builtin-report.c +4 -4
@@ -575,7 +575,7 @@ int cmd_report(int argc, const char **argv, const char *prefix __maybe_unused)struct stat st;bool has_br_stack = false;int branch_mode =-1 ; -char callchain_default_opt[] ="fractal,0.5,callee" ; +char callchain_default_opt[] ="fractal,0.5,callee,function,fp" ;const char *const report_usage[] = {"perf report [<options>]" ,NULL
@@ -637,9 +637,9 @@ int cmd_report(int argc, const char **argv, const char *prefix __maybe_unused) "regex filter to identify parent, see: '--sort parent'"),OPT_BOOLEAN ('x' ,"exclude-other" , &symbol_conf.exclude_other,"Only display entries with parent-match" ), -OPT_CALLBACK_DEFAULT ('g' ,"call-graph" , &report,"output_type,min_percent[,print_limit],call_order" , -"Display callchains using output_type (graph, flat, fractal, or none) , min percent threshold, optional print limit, callchain order, key (function or address). " -"Default: fractal,0.5,callee,function" , &report_parse_callchain_opt, callchain_default_opt), +OPT_CALLBACK_DEFAULT ('g' ,"call-graph" , &report,"output_type,min_percent[,print_limit],call_order,source" , +"Display callchains using output_type (graph, flat, fractal, or none) , min percent threshold, optional print limit, callchain order, key (function or address), callchain source(fp or lbr). " +"Default: fractal,0.5,callee,function,fp" , &report_parse_callchain_opt, callchain_default_opt),OPT_BOOLEAN (0 ,"children" , &symbol_conf.cumulate_callchain,"Accumulate callchains of children and show total overhead as well" ), OPT_INTEGER(0, "max-stack", &report.max_stack,
tools/perf/util/callchain.c +17 -1
@@ -152,6 +152,19 @@ static int parse_callchain_sort_key(const char *value)return -1 ; } +static int parse_callchain_source (const char *value) +{ +if (!strncmp (value,"fp" ,strlen (value))) { + callchain_param.source =SOURCE_FP ; +return 0 ; + } +if (!strncmp (value,"lbr" ,strlen (value))) { + callchain_param.source =SOURCE_LBR ; +return 0 ; + } +return -1 ; +} +int parse_callchain_report_opt (const char *arg) {
@@ -173,7 +186,8 @@ parse_callchain_report_opt(const char *arg)if (!parse_callchain_mode (tok) || !parse_callchain_order (tok) || - !parse_callchain_sort_key (tok)) { + !parse_callchain_sort_key (tok) || + !parse_callchain_source (tok)) {/* parsing ok - move on to the next */ }else if (!minpcnt_set) {/* try to get the min percent */
@@ -225,6 +239,8 @@ int perf_callchain_config(const char *var, const char *value)return parse_callchain_order (value);if (!strcmp (var,"sort-key" ))return parse_callchain_sort_key (value); +if (!strcmp (var,"source" )) +return parse_callchain_source (value);if (!strcmp (var,"threshold" )) { callchain_param.min_percent =strtod (value, &endptr);if (value == endptr)
tools/perf/util/callchain.h +6 -0
@@ -53,6 +53,11 @@ enum chain_key {CCKEY_ADDRESS }; +enum chain_source { +SOURCE_FP , +SOURCE_LBR +}; +struct callchain_param {bool enabled;enum perf_call_graph_mode record_mode;
@@ -63,6 +68,7 @@ struct callchain_param {sort_chain_func_t sort;enum chain_order order;enum chain_key key; +enum chain_source source; };extern struct callchain_param callchain_param;
tools/perf/util/machine.c +135 -63
233 lines not on this page · raw message
tools/perf/util/session.c +32 -2
@@ -560,12 +560,42 @@ int perf_session_queue_event(struct perf_session *s, union perf_event *event,static void callchain__printf (struct perf_sample *sample) {unsigned int i; +u64 total_nr, callchain_nr; +int use_fp = (callchain_param.source ==SOURCE_FP ) ?1 :0 ; -printf ("... chain: nr:%" PRIu64"\n" , sample->callchain->nr); + total_nr = callchain_nr = sample->callchain->nr; -for (i =0 ; i < sample->callchain->nr; i++) +/* If there isn't user fp callchain available, try LBR */ +if (!(sample->callchain->source &PERF_FP_CALLCHAIN )) + use_fp =0 ; + +if (!use_fp && (sample->callchain->source &PERF_LBR_CALLCHAIN )) { +struct branch_stack *lbr_stack = sample->branch_stack; + +for (i =0 ; i < callchain_nr; i++) { +if (sample->callchain->ips[i] ==PERF_CONTEXT_USER ) +break ; + } + +if (i != callchain_nr) { + total_nr = i +1 + lbr_stack->nr; + callchain_nr = i +1 ; + } + } + +printf ("... chain: nr:%" PRIu64"\n" , total_nr); + +for (i =0 ; i < callchain_nr +1 ; i++)printf ("..... %2d: %016" PRIx64"\n" , i, sample->callchain->ips[i]); + +if (total_nr > callchain_nr) { +struct branch_stack *lbr_stack = sample->branch_stack; + +for (i =0 ; i < lbr_stack->nr; i++) +printf ("..... %2d: %016" PRIx64"\n" , + (int )(i + callchain_nr +1 ), lbr_stack->entries[i].from); + } }static void branch_stack__printf (struct perf_sample *sample)
Signature · 1 line
1.8.3.2
Peter Zijlstra
maintainerSo if I take all except 11,13,16,17 but instead do something like the below, everything will work just fine, right?
Or am I missing something?
--- arch/x86/kernel/cpu/perf_event.h | 8 -------- arch/x86/kernel/cpu/perf_event_intel_lbr.c | 8 ++++---- include/uapi/linux/perf_event.h | 16 ++++++++-------- 3 files changed, 12 insertions(+), 20 deletions(-)
arch/x86/kernel/cpu/perf_event.h +0 -8
@@ -521,14 +521,6 @@ struct x86_perf_task_context {int lbr_stack_state; }; -enum { -PERF_SAMPLE_BRANCH_CALL_STACK_SHIFT =PERF_SAMPLE_BRANCH_MAX_SHIFT , -PERF_SAMPLE_BRANCH_SELECT_MAP_SIZE , - -PERF_SAMPLE_BRANCH_CALL_STACK = -1U <<PERF_SAMPLE_BRANCH_CALL_STACK_SHIFT , -}; -#define x86_add_quirk (func_) \ do { \ static struct x86_pmu_quirk __quirk __initdata = { \
arch/x86/kernel/cpu/perf_event_intel_lbr.c +4 -4
@@ -537,7 +537,7 @@ static int intel_pmu_setup_hw_lbr_filteru64 mask =0 , v;int i; -for (i =0 ; i <PERF_SAMPLE_BRANCH_SELECT_MAP_SIZE ; i++) { +for (i =0 ; i <PERF_SAMPLE_BRANCH_MAX_SHIFT ; i++) {if (!(br_type & (1ULL << i)))continue ;
@@ -808,7 +808,7 @@ intel_pmu_lbr_filter(struct cpu_hw_event/* * Map interface branch filters onto LBR filters */ -static const int nhm_lbr_sel_map[PERF_SAMPLE_BRANCH_SELECT_MAP_SIZE ] = { +static const int nhm_lbr_sel_map[PERF_SAMPLE_BRANCH_MAX_SHIFT ] = { [PERF_SAMPLE_BRANCH_ANY_SHIFT ] =LBR_ANY , [PERF_SAMPLE_BRANCH_USER_SHIFT ] =LBR_USER , [PERF_SAMPLE_BRANCH_KERNEL_SHIFT ] =LBR_KERNEL ,
@@ -827,7 +827,7 @@ static const int nhm_lbr_sel_map[PERF_SA [PERF_SAMPLE_BRANCH_COND_SHIFT] = LBR_JCC, }; -static const int snb_lbr_sel_map[PERF_SAMPLE_BRANCH_SELECT_MAP_SIZE ] = { +static const int snb_lbr_sel_map[PERF_SAMPLE_BRANCH_MAX_SHIFT ] = { [PERF_SAMPLE_BRANCH_ANY_SHIFT ] =LBR_ANY , [PERF_SAMPLE_BRANCH_USER_SHIFT ] =LBR_USER , [PERF_SAMPLE_BRANCH_KERNEL_SHIFT ] =LBR_KERNEL ,
@@ -839,7 +839,7 @@ static const int snb_lbr_sel_map[PERF_SA [PERF_SAMPLE_BRANCH_COND_SHIFT] = LBR_JCC, }; -static const int hsw_lbr_sel_map[PERF_SAMPLE_BRANCH_SELECT_MAP_SIZE ] = { +static const int hsw_lbr_sel_map[PERF_SAMPLE_BRANCH_MAX_SHIFT ] = { [PERF_SAMPLE_BRANCH_ANY_SHIFT ] =LBR_ANY , [PERF_SAMPLE_BRANCH_USER_SHIFT ] =LBR_USER , [PERF_SAMPLE_BRANCH_KERNEL_SHIFT ] =LBR_KERNEL ,
include/uapi/linux/perf_event.h +8 -8
@@ -166,6 +166,8 @@ enum perf_branch_sample_type_shift {PERF_SAMPLE_BRANCH_NO_TX_SHIFT =9 ,/* not in transaction */ PERF_SAMPLE_BRANCH_COND_SHIFT =10 ,/* conditional branches */ +PERF_SAMPLE_BRANCH_CALL_STACK_SHIFT =11 ,/* call/ret stack */ + PERF_SAMPLE_BRANCH_MAX_SHIFT /* non-ABI */ };
@@ -175,18 +177,16 @@ enum perf_branch_sample_type {PERF_SAMPLE_BRANCH_HV =1U <<PERF_SAMPLE_BRANCH_HV_SHIFT ,PERF_SAMPLE_BRANCH_ANY =1U <<PERF_SAMPLE_BRANCH_ANY_SHIFT , -PERF_SAMPLE_BRANCH_ANY_CALL = -1U <<PERF_SAMPLE_BRANCH_ANY_CALL_SHIFT , -PERF_SAMPLE_BRANCH_ANY_RETURN = -1U <<PERF_SAMPLE_BRANCH_ANY_RETURN_SHIFT , -PERF_SAMPLE_BRANCH_IND_CALL = -1U <<PERF_SAMPLE_BRANCH_IND_CALL_SHIFT , -PERF_SAMPLE_BRANCH_ABORT_TX = -1U <<PERF_SAMPLE_BRANCH_ABORT_TX_SHIFT , +PERF_SAMPLE_BRANCH_ANY_CALL =1U <<PERF_SAMPLE_BRANCH_ANY_CALL_SHIFT , +PERF_SAMPLE_BRANCH_ANY_RETURN =1U <<PERF_SAMPLE_BRANCH_ANY_RETURN_SHIFT , +PERF_SAMPLE_BRANCH_IND_CALL =1U <<PERF_SAMPLE_BRANCH_IND_CALL_SHIFT , +PERF_SAMPLE_BRANCH_ABORT_TX =1U <<PERF_SAMPLE_BRANCH_ABORT_TX_SHIFT ,PERF_SAMPLE_BRANCH_IN_TX =1U <<PERF_SAMPLE_BRANCH_IN_TX_SHIFT ,PERF_SAMPLE_BRANCH_NO_TX =1U <<PERF_SAMPLE_BRANCH_NO_TX_SHIFT ,PERF_SAMPLE_BRANCH_COND =1U <<PERF_SAMPLE_BRANCH_COND_SHIFT , +PERF_SAMPLE_BRANCH_CALL_STACK =1U <<PERF_SAMPLE_BRANCH_CALL_STACK_SHIFT , + PERF_SAMPLE_BRANCH_MAX = 1U << PERF_SAMPLE_BRANCH_MAX_SHIFT, };
Quoted 8 lines
Quoted 2 lines
So if I take all except 11,13,16,17 but instead do something like the below, everything will work just fine, right?
Or am I missing something?
Yes, it should work. Then LBR callstack will rely on user to enable it. But user never get the LBR callstack data if it's available. I'm not sure why you do that?
Quoted 123 lines
--- arch/x86/kernel/cpu/perf_event.h | 8 -------- arch/x86/kernel/cpu/perf_event_intel_lbr.c | 8 ++++---- include/uapi/linux/perf_event.h | 16 ++++++++-------- 3 files changed, 12 insertions(+), 20 deletions(-)arch/x86/kernel/cpu/perf_event.h +0
-8@@ -521,14 +521,6 @@ struct x86_perf_task_context {int lbr_stack_state; }; -enum { -PERF_SAMPLE_BRANCH_CALL_STACK_SHIFT =PERF_SAMPLE_BRANCH_MAX_SHIFT , -PERF_SAMPLE_BRANCH_SELECT_MAP_SIZE , - -PERF_SAMPLE_BRANCH_CALL_STACK = -1U <<PERF_SAMPLE_BRANCH_CALL_STACK_SHIFT , -}; - #define x86_add_quirk(func_) \do { \
arch/x86/kernel/cpu/perf_event.h +0
-0static struct x86_pmu_quirk __quirk __initdata = { \arch/x86/kernel/cpu/perf_event_intel_lbr.c +2
-2@@ -537,7 +537,7 @@ static int intel_pmu_setup_hw_lbr_filteru64 mask =0 , v;int i; -for (i =0 ; i <PERF_SAMPLE_BRANCH_SELECT_MAP_SIZE ; i++) { +for (i =0 ; i <PERF_SAMPLE_BRANCH_MAX_SHIFT ; i++) {if (!(br_type & (1ULL << i)))continue ;@@ -808,7 +808,7 @@ intel_pmu_lbr_filter(struct cpu_hw_event/* * Map interface branch filters onto LBR filters */ -static const int nhm_lbr_sel_map[PERF_SAMPLE_BRANCH_SELECT_MAP_SIZE] = { +static const int nhm_lbr_sel_map[PERF_SAMPLE_BRANCH_MAX_SHIFT ] = { [PERF_SAMPLE_BRANCH_ANY_SHIFT ] =LBR_ANY ,arch/x86/kernel/cpu/perf_event_intel_lbr.c +1
-1[PERF_SAMPLE_BRANCH_USER_SHIFT] = LBR_USER, [PERF_SAMPLE_BRANCH_KERNEL_SHIFT] = LBR_KERNEL,@@ -827,7 +827,7 @@ static const int nhm_lbr_sel_map[PERF_SA [PERF_SAMPLE_BRANCH_COND_SHIFT ] =LBR_JCC , }; -static const int snb_lbr_sel_map[PERF_SAMPLE_BRANCH_SELECT_MAP_SIZE ] = { +static const int snb_lbr_sel_map[PERF_SAMPLE_BRANCH_MAX_SHIFT] = { [PERF_SAMPLE_BRANCH_ANY_SHIFT ] =LBR_ANY ,arch/x86/kernel/cpu/perf_event_intel_lbr.c +1
-1[PERF_SAMPLE_BRANCH_USER_SHIFT] = LBR_USER, [PERF_SAMPLE_BRANCH_KERNEL_SHIFT] = LBR_KERNEL,@@ -839,7 +839,7 @@ static const int snb_lbr_sel_map[PERF_SA [PERF_SAMPLE_BRANCH_COND_SHIFT ] =LBR_JCC , }; -static const int hsw_lbr_sel_map[PERF_SAMPLE_BRANCH_SELECT_MAP_SIZE ] = { +static const int hsw_lbr_sel_map[PERF_SAMPLE_BRANCH_MAX_SHIFT] = { [PERF_SAMPLE_BRANCH_ANY_SHIFT ] =LBR_ANY ,arch/x86/kernel/cpu/perf_event_intel_lbr.c +0
-0[PERF_SAMPLE_BRANCH_USER_SHIFT] = LBR_USER, [PERF_SAMPLE_BRANCH_KERNEL_SHIFT] = LBR_KERNEL,include/uapi/linux/perf_event.h +0
-0@@ -166,6 +166,8 @@ enum perf_branch_sample_type_shift { PERF_SAMPLE_BRANCH_NO_TX_SHIFT = 9, /* notin transaction */
PERF_SAMPLE_BRANCH_COND_SHIFT= 10, /* conditional
branches */include/uapi/linux/perf_event.h +1
-0+ PERF_SAMPLE_BRANCH_CALL_STACK_SHIFT = 11, /* call/retstack */
include/uapi/linux/perf_event.h +3
-8+ PERF_SAMPLE_BRANCH_MAX_SHIFT /* non-ABI */ };@@ -175,18 +177,16 @@ enum perf_branch_sample_type {PERF_SAMPLE_BRANCH_HV =1U <<PERF_SAMPLE_BRANCH_HV_SHIFT ,PERF_SAMPLE_BRANCH_ANY =1U <<PERF_SAMPLE_BRANCH_ANY_SHIFT , -PERF_SAMPLE_BRANCH_ANY_CALL = -1U <<PERF_SAMPLE_BRANCH_ANY_CALL_SHIFT , -PERF_SAMPLE_BRANCH_ANY_RETURN = -1U <<PERF_SAMPLE_BRANCH_ANY_RETURN_SHIFT , -PERF_SAMPLE_BRANCH_IND_CALL = -1U <<PERF_SAMPLE_BRANCH_IND_CALL_SHIFT , -PERF_SAMPLE_BRANCH_ABORT_TX = -1U <<PERF_SAMPLE_BRANCH_ABORT_TX_SHIFT , +PERF_SAMPLE_BRANCH_ANY_CALL =1U <<PERF_SAMPLE_BRANCH_ANY_CALL_SHIFT , + PERF_SAMPLE_BRANCH_ANY_RETURN = 1U <<
PERF_SAMPLE_BRANCH_ANY_RETURN_SHIFT,include/uapi/linux/perf_event.h +1
-0+ PERF_SAMPLE_BRANCH_IND_CALL = 1U <<
PERF_SAMPLE_BRANCH_IND_CALL_SHIFT,include/uapi/linux/perf_event.h +1
-0+ PERF_SAMPLE_BRANCH_ABORT_TX = 1U <<
PERF_SAMPLE_BRANCH_ABORT_TX_SHIFT,
PERF_SAMPLE_BRANCH_IN_TX= 1U <<PERF_SAMPLE_BRANCH_IN_TX_SHIFT,
PERF_SAMPLE_BRANCH_NO_TX= 1U <<PERF_SAMPLE_BRANCH_NO_TX_SHIFT,
PERF_SAMPLE_BRANCH_COND= 1U <<PERF_SAMPLE_BRANCH_COND_SHIFT,include/uapi/linux/perf_event.h +1
-0+ PERF_SAMPLE_BRANCH_CALL_STACK = 1U <<
PERF_SAMPLE_BRANCH_CALL_STACK_SHIFT,include/uapi/linux/perf_event.h +1
-0+ PERF_SAMPLE_BRANCH_MAX = 1U <<
PERF_SAMPLE_BRANCH_MAX_SHIFT,
};
Peter Zijlstra
maintainerQuoted 6 lines · Kan
Quoted 6 lines
Quoted 2 lines
So if I take all except 11,13,16,17 but instead do something like the below, everything will work just fine, right?
Quoted 6 lines
Quoted 2 lines
Or am I missing something?
Yes, it should work. Then LBR callstack will rely on user to enable it. But user never get the LBR callstack data if it's available. I'm not sure why you do that?
Uhm what? If you request PERF_SAMPLE_BRANCH_CALL_STACK the user will get the data through the regular PERF_SAMPLE_BRANCH_STACK output of PERF_RECORD_SAMPLE, right?
Quoted 12 lines · Kan
Quoted 9 lines
Quoted 8 lines
Quoted 2 lines
So if I take all except 11,13,16,17 but instead do something like the below, everything will work just fine, right?
Or am I missing something?
Quoted 7 lines
Quoted 3 lines
Yes, it should work. Then LBR callstack will rely on user to enable it. But user never get the LBR callstack data if it's available. I'm not sure why you do that?
Uhm what? If you request
PERF_SAMPLE_BRANCH_CALL_STACKthe user will get the data through the regularPERF_SAMPLE_BRANCH_STACKoutput ofPERF_RECORD_SAMPLE, right?
OK, I think I should understand your meaning.
Quoted 1 line
From the kernel side, we provide a 3rd callchain option to user.
The kernel only tries to enable LBR and prepare the data if possible. The kernel doesn't guarantee the data must come from hardware LBR, even user choose LBR callchain option.
It's user tool's responsibility to filter the request, choose the data source and reconstruct the data. It's not the scope of this kernel patch. That should depend on the implementation of another user tool patchset.
What do you think?
Thanks,
Kan
tip-bot for Peter Zijlstra
merge bot[tip:perf/core] perf/x86/intel: Expose LBR callstack to user space tooling
In reply to Peter Zijlstraperf/x86/intel: Expose LBR callstack to user space tooling
Commit-ID: 2c44b1936bb3b135a3fac8b3493394d42e51cf70 Gitweb: http://git.kernel.org/tip/2c44b1936bb3b135a3fac8b3493394d42e51cf70 Author: Peter Zijlstra <[email protected]> AuthorDate: Wed, 5 Nov 2014 10:36:45 +0100 Committer: Ingo Molnar <[email protected]> CommitDate: Wed, 18 Feb 2015 17:16:15 +0100
perf/x86/intel: Expose LBR callstack to user space tooling
With LBR call stack feature enable, there are three callchain options. Enable the 3rd callchain option (LBR callstack) to user space tooling.
--- arch/x86/kernel/cpu/perf_event.h | 8 -------- arch/x86/kernel/cpu/perf_event_intel_lbr.c | 8 ++++---- include/uapi/linux/perf_event.h | 16 ++++++++-------- 3 files changed, 12 insertions(+), 20 deletions(-)
arch/x86/kernel/cpu/perf_event.h +0 -8
@@ -523,14 +523,6 @@ struct x86_perf_task_context {int lbr_stack_state; }; -enum { -PERF_SAMPLE_BRANCH_CALL_STACK_SHIFT =PERF_SAMPLE_BRANCH_MAX_SHIFT , -PERF_SAMPLE_BRANCH_SELECT_MAP_SIZE , - -PERF_SAMPLE_BRANCH_CALL_STACK = -1U <<PERF_SAMPLE_BRANCH_CALL_STACK_SHIFT , -}; -#define x86_add_quirk (func_) \ do { \ static struct x86_pmu_quirk __quirk __initdata = { \
arch/x86/kernel/cpu/perf_event_intel_lbr.c +4 -4
@@ -537,7 +537,7 @@ static int intel_pmu_setup_hw_lbr_filter(struct perf_event *event)u64 mask =0 , v;int i; -for (i =0 ; i <PERF_SAMPLE_BRANCH_SELECT_MAP_SIZE ; i++) { +for (i =0 ; i <PERF_SAMPLE_BRANCH_MAX_SHIFT ; i++) {if (!(br_type & (1ULL << i)))continue ;
@@ -821,7 +821,7 @@ intel_pmu_lbr_filter(struct cpu_hw_events *cpuc)/* * Map interface branch filters onto LBR filters */ -static const int nhm_lbr_sel_map[PERF_SAMPLE_BRANCH_SELECT_MAP_SIZE ] = { +static const int nhm_lbr_sel_map[PERF_SAMPLE_BRANCH_MAX_SHIFT ] = { [PERF_SAMPLE_BRANCH_ANY_SHIFT ] =LBR_ANY , [PERF_SAMPLE_BRANCH_USER_SHIFT ] =LBR_USER , [PERF_SAMPLE_BRANCH_KERNEL_SHIFT ] =LBR_KERNEL ,
@@ -840,7 +840,7 @@ static const int nhm_lbr_sel_map[PERF_SAMPLE_BRANCH_SELECT_MAP_SIZE] = { [PERF_SAMPLE_BRANCH_COND_SHIFT] = LBR_JCC, }; -static const int snb_lbr_sel_map[PERF_SAMPLE_BRANCH_SELECT_MAP_SIZE ] = { +static const int snb_lbr_sel_map[PERF_SAMPLE_BRANCH_MAX_SHIFT ] = { [PERF_SAMPLE_BRANCH_ANY_SHIFT ] =LBR_ANY , [PERF_SAMPLE_BRANCH_USER_SHIFT ] =LBR_USER , [PERF_SAMPLE_BRANCH_KERNEL_SHIFT ] =LBR_KERNEL ,
@@ -852,7 +852,7 @@ static const int snb_lbr_sel_map[PERF_SAMPLE_BRANCH_SELECT_MAP_SIZE] = { [PERF_SAMPLE_BRANCH_COND_SHIFT] = LBR_JCC, }; -static const int hsw_lbr_sel_map[PERF_SAMPLE_BRANCH_SELECT_MAP_SIZE ] = { +static const int hsw_lbr_sel_map[PERF_SAMPLE_BRANCH_MAX_SHIFT ] = { [PERF_SAMPLE_BRANCH_ANY_SHIFT ] =LBR_ANY , [PERF_SAMPLE_BRANCH_USER_SHIFT ] =LBR_USER , [PERF_SAMPLE_BRANCH_KERNEL_SHIFT ] =LBR_KERNEL ,
include/uapi/linux/perf_event.h +8 -8
@@ -166,6 +166,8 @@ enum perf_branch_sample_type_shift {PERF_SAMPLE_BRANCH_NO_TX_SHIFT =9 ,/* not in transaction */ PERF_SAMPLE_BRANCH_COND_SHIFT =10 ,/* conditional branches */ +PERF_SAMPLE_BRANCH_CALL_STACK_SHIFT =11 ,/* call/ret stack */ + PERF_SAMPLE_BRANCH_MAX_SHIFT /* non-ABI */ };
@@ -175,18 +177,16 @@ enum perf_branch_sample_type {PERF_SAMPLE_BRANCH_HV =1U <<PERF_SAMPLE_BRANCH_HV_SHIFT ,PERF_SAMPLE_BRANCH_ANY =1U <<PERF_SAMPLE_BRANCH_ANY_SHIFT , -PERF_SAMPLE_BRANCH_ANY_CALL = -1U <<PERF_SAMPLE_BRANCH_ANY_CALL_SHIFT , -PERF_SAMPLE_BRANCH_ANY_RETURN = -1U <<PERF_SAMPLE_BRANCH_ANY_RETURN_SHIFT , -PERF_SAMPLE_BRANCH_IND_CALL = -1U <<PERF_SAMPLE_BRANCH_IND_CALL_SHIFT , -PERF_SAMPLE_BRANCH_ABORT_TX = -1U <<PERF_SAMPLE_BRANCH_ABORT_TX_SHIFT , +PERF_SAMPLE_BRANCH_ANY_CALL =1U <<PERF_SAMPLE_BRANCH_ANY_CALL_SHIFT , +PERF_SAMPLE_BRANCH_ANY_RETURN =1U <<PERF_SAMPLE_BRANCH_ANY_RETURN_SHIFT , +PERF_SAMPLE_BRANCH_IND_CALL =1U <<PERF_SAMPLE_BRANCH_IND_CALL_SHIFT , +PERF_SAMPLE_BRANCH_ABORT_TX =1U <<PERF_SAMPLE_BRANCH_ABORT_TX_SHIFT ,PERF_SAMPLE_BRANCH_IN_TX =1U <<PERF_SAMPLE_BRANCH_IN_TX_SHIFT ,PERF_SAMPLE_BRANCH_NO_TX =1U <<PERF_SAMPLE_BRANCH_NO_TX_SHIFT ,PERF_SAMPLE_BRANCH_COND =1U <<PERF_SAMPLE_BRANCH_COND_SHIFT , +PERF_SAMPLE_BRANCH_CALL_STACK =1U <<PERF_SAMPLE_BRANCH_CALL_STACK_SHIFT , + PERF_SAMPLE_BRANCH_MAX = 1U << PERF_SAMPLE_BRANCH_MAX_SHIFT, };