Re: [RFC v3 5/5] perf tools: Add support to process multi spe events

From: Tan Xiaojun
Date: Sun Dec 08 2019 - 19:46:59 EST

Next message: Al Viro: "Re: [PATCH v2 0/6] Delete timespec64_trunc()"
Previous message: Stephen Rothwell: "Re: linux-next: manual merge of the vhost tree with Linus' tree"
Next in thread: James Clark: "Re: [RFC v3 5/5] perf tools: Add support to process multi spe events"
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

On 2019/12/6 23:48, James Clark wrote:
> Hi Xiaojun,
>
>>
>> What do you think of this current implementation? Or you prefer the previous way(like branch-misses:pp dTLB-load-misses:pp cache-misses:pp), then I will modify it again.
>>
>
> Yes I think I prefer the previous way. The reason to add support for :p on the standard event names was to make the user experience more similar to x86. What was the reason for moving to arm_spe_x/branch_miss/? If we are going to use this format then I don't see the need for requiring users to add :p to the end of arm_spe_x/branch_miss/.
>

Hi, James,

OK, I will reconsider how to modify it.

> I've tested these patches, but unfortunately I don't see the new events when I do perf list:
> ...
> arm_spe_0// [Kernel PMU event]
> armv8_pmuv3/l3d_cache_wb/ [Kernel PMU event]
> armv8_pmuv3/sample_collision/ [Kernel PMU event]
> armv8_pmuv3/sample_feed/ [Kernel PMU event]
> armv8_pmuv3/sample_filtrate/ [Kernel PMU event]
> armv8_pmuv3/sample_pop/ [Kernel PMU event]
>
> branch:
> br_mis_pred
> ...
>
> Should I see events like /arm_spe_0/branch_miss/ in that list?
>
> And then if I attempt to record them I get this error:
>
> ./perf record -e arm_spe_0/branch_miss/ ls
> event syntax error: 'arm_spe_0/branch_miss/'
> \___ unknown term
>
> But using the plain event name still works:
>
> ./perf record -e arm_spe/ts_enable=1/ ls
> ...
> [ perf record: Woken up 1 times to write data ]
> [ perf record: Captured and wrote 0.571 MB perf.data ]
>

It may be that you did not recompile the kernel. In order to support this method, I modified the spe driver, which requires recompiling the kernel to support it.

Thanks.
Xiaojun.

>
> Thanks
> James
>
> On 30/11/2019 00:42, Tan Xiaojun wrote:
>> On 2019/11/30 0:32, James Clark wrote:
>>> Hi Xiaojun,
>>>
>>> Sorry for not replying earlier, I was at a conference. Unfortunately I have temporarily lost access to SPE enabled hardware but I will test this out and get back to you as soon as possible.
>>>
>>>
>>> Thanks
>>> James
>>>
>>
>> OK.
>>
>> Thanks.
>> Xiaojun.
>>
>>> On 23/11/2019 10:11, Tan Xiaojun wrote:
>>>> Under the original logic, if the user specifies multiple spe
>>>> events during the record, perf will report an error and exit
>>>> without actually running. This is not very friendly.
>>>>
>>>> This patch slightly modifies this logic, in which case a
>>>> warning is reported and the first spe event is taken as a
>>>> record.
>>>>
>>>> At the same time, this patch also supports the recording of
>>>> multi new synthetic events. However, if the user specifies the
>>>> spe event and then specifies the synthetic spe events, a warning
>>>> will be reported and the above principles will still be followed,
>>>> only the first spe event will be recorded.
>>>>
>>>> Example:
>>>> ------------------------------------------------------------------
>>>> 1) For multiple spe events
>>>> $ perf record -e arm_spe_0/ts_enable=0,load_filter=1,jitter=1,min_latency=0/ -e arm_spe_0/ts_enable=0,store_filter=1,jitter=1,min_latency=0/ ls
>>>> Warning:
>>>> There may be only one arm_spe_x event. More than one spe event will be ignored, unless they are synthetic events of spe, like:
>>>> arm_spe_x/llc_miss/
>>>> arm_spe_x/branch_miss/
>>>> arm_spe_x/tlb_miss/
>>>> arm_spe_x/remote_access/
>>>> (see 'perf list')
>>>> ...
>>>> [ perf record: Woken up 1 times to write data ]
>>>> [ perf record: Captured and wrote 0.078 MB perf.data ]
>>>>
>>>> $ perf report --stdio
>>>> ...
>>>> # Samples: 0 of event 'arm_spe_0/ts_enable=0,load_filter=1,jitter=1,min_latency=0/'
>>>> ...
>>>>
>>>> 2) For multiple spe precise ip events (synthetic event)
>>>> $ perf record -e arm_spe_0/llc_miss/ -e arm_spe_0/llc_miss/ -e arm_spe_0/tlb_miss/ ls
>>>> Warning:
>>>> These events are precise ip events, please add :p/pp/ppp after the event.
>>>> ...
>>>> [ perf record: Woken up 1 times to write data ]
>>>> [ perf record: Captured and wrote 0.343 MB perf.data ]
>>>>
>>>> $ perf report --stdio
>>>> # To display the perf.data header info, please use --header/--header-only options.
>>>> #
>>>> #
>>>> # Total Lost Samples: 0
>>>> #
>>>> # Samples: 0 of event 'arm_spe_0/llc_miss/, arm_spe_0/tlb_miss/'
>>>> # Event count (approx.): 0
>>>> #
>>>> # Children Self Command Shared Object Symbol
>>>> # ........ ........ ....... ............. ......
>>>> #
>>>>
>>>> # Samples: 0 of event 'dummy:u'
>>>> # Event count (approx.): 0
>>>> #
>>>> # Children Self Command Shared Object Symbol
>>>> # ........ ........ ....... ............. ......
>>>> #
>>>>
>>>> # Samples: 83 of event 'llc-miss'
>>>> # Event count (approx.): 83
>>>> #
>>>> # Children Self Command Shared Object Symbol
>>>> # ........ ........ ....... ................. ....................................
>>>> #
>>>> 42.17% 42.17% ls [kernel.kallsyms] [k] perf_iterate_ctx.constprop.64
>>>> 14.46% 14.46% ls [kernel.kallsyms] [k] memchr_inv
>>>> 13.25% 13.25% ls [kernel.kallsyms] [k] perf_event_mmap
>>>> 2.41% 2.41% ls [kernel.kallsyms] [k] available_idle_cpu
>>>> 2.41% 2.41% ls [kernel.kallsyms] [k] copy_page
>>>> 2.41% 2.41% ls [kernel.kallsyms] [k] try_to_wake_up
>>>> 2.41% 2.41% ls [kernel.kallsyms] [k] vma_interval_tree_insert
>>>> 2.41% 2.41% ls ld-2.28.so [.] _dl_lookup_symbol_x
>>>> 2.41% 2.41% ls ld-2.28.so [.] _dl_relocate_object
>>>> 1.20% 1.20% ls [kernel.kallsyms] [k] ext4_getattr
>>>> 1.20% 1.20% ls [kernel.kallsyms] [k] get_page_from_freelist
>>>> 1.20% 1.20% ls [kernel.kallsyms] [k] get_partial_node.isra.25
>>>> 1.20% 1.20% ls [kernel.kallsyms] [k] lock_page_memcg
>>>> 1.20% 1.20% ls [kernel.kallsyms] [k] may_open
>>>> 1.20% 1.20% ls [kernel.kallsyms] [k] radix_tree_next_chunk
>>>> 1.20% 1.20% ls [kernel.kallsyms] [k] rb_prev
>>>> 1.20% 1.20% ls ld-2.28.so [.] _dl_map_object_from_fd
>>>> 1.20% 1.20% ls ld-2.28.so [.] _dl_start
>>>> 1.20% 1.20% ls ld-2.28.so [.] do_lookup_x
>>>> 1.20% 1.20% ls ld-2.28.so [.] rtld_lock_default_lock_recursive
>>>> 1.20% 1.20% ls libc-2.28.so [.] getenv
>>>> 1.20% 1.20% ls [unknown] [.] 0xffff29f1190029b8
>>>>
>>>> # Samples: 13 of event 'tlb-miss'
>>>> # Event count (approx.): 13
>>>> #
>>>> # Children Self Command Shared Object Symbol
>>>> # ........ ........ ....... ................. ............................
>>>> #
>>>> 15.38% 15.38% ls [kernel.kallsyms] [k] __audit_syscall_entry
>>>> 15.38% 15.38% ls [kernel.kallsyms] [k] get_partial_node.isra.25
>>>> 15.38% 15.38% ls ld-2.28.so [.] _dl_relocate_object
>>>> 15.38% 15.38% ls ld-2.28.so [.] do_lookup_x
>>>> 7.69% 7.69% ls [kernel.kallsyms] [k] memchr_inv
>>>> 7.69% 7.69% ls ld-2.28.so [.] _dl_map_object_from_fd
>>>> 7.69% 7.69% ls ld-2.28.so [.] _dl_setup_hash
>>>> 7.69% 7.69% ls ld-2.28.so [.] _dl_start
>>>> 7.69% 7.69% ls ls [.] 0x00000000000097a0
>>>>
>>>> ------------------------------------------------------------------
>>>>
>>>> Signed-off-by: Tan Xiaojun <tanxiaojun@xxxxxxxxxx>
>>>> ---
>>>> tools/perf/arch/arm64/util/arm-spe.c | 47 +++++++++++++++++++++++++---
>>>> tools/perf/util/arm-spe.c | 25 +++++++++++++++
>>>> tools/perf/util/arm-spe.h | 20 ++++++++++++
>>>> 3 files changed, 88 insertions(+), 4 deletions(-)
>>>>
>>>> diff --git a/tools/perf/arch/arm64/util/arm-spe.c b/tools/perf/arch/arm64/util/arm-spe.c
>>>> index eba6541ec0f1..68e91f3c9614 100644
>>>> --- a/tools/perf/arch/arm64/util/arm-spe.c
>>>> +++ b/tools/perf/arch/arm64/util/arm-spe.c
>>>> @@ -67,21 +67,60 @@ static int arm_spe_recording_options(struct auxtrace_record *itr,
>>>> struct arm_spe_recording *sper =
>>>> container_of(itr, struct arm_spe_recording, itr);
>>>> struct perf_pmu *arm_spe_pmu = sper->arm_spe_pmu;
>>>> - struct evsel *evsel, *arm_spe_evsel = NULL;
>>>> + struct evsel *evsel, *tmp, *arm_spe_evsel = NULL;
>>>> bool privileged = perf_event_paranoid_check(-1);
>>>> struct evsel *tracking_evsel;
>>>> + char evsel_name[128];
>>>> int err;
>>>>
>>>> sper->evlist = evlist;
>>>>
>>>> - evlist__for_each_entry(evlist, evsel) {
>>>> + evlist__for_each_entry_safe(evlist, tmp, evsel) {
>>>> if (evsel->core.attr.type == arm_spe_pmu->type) {
>>>> if (arm_spe_evsel) {
>>>> - pr_err("There may be only one " ARM_SPE_PMU_NAME "x event\n");
>>>> - return -EINVAL;
>>>> + if ((evsel->core.attr.config
>>>> + & GENMASK_ULL(ARM_SPE_EVENT_HI,
>>>> + ARM_SPE_EVENT_LO))
>>>> + && (arm_spe_evsel->core.attr.config
>>>> + & GENMASK_ULL(ARM_SPE_EVENT_HI,
>>>> + ARM_SPE_EVENT_LO))) {
>>>> + arm_spe_evsel->core.attr.config |=
>>>> + evsel->core.attr.config;
>>>> +
>>>> + if (!strstr(arm_spe_evsel->name, evsel->name)) {
>>>> + scnprintf(evsel_name, sizeof(evsel_name),
>>>> + "%s, %s", arm_spe_evsel->name,
>>>> + evsel->name);
>>>> + arm_spe_evsel->name = strdup(evsel_name);
>>>> + }
>>>> + } else
>>>> + pr_warning("Warning:\n"
>>>> + "There may be only one "
>>>> + ARM_SPE_PMU_NAME "x event."
>>>> + " More than one spe event"
>>>> + " will be ignored, unless"
>>>> + " they are synthetic events"
>>>> + " of spe, like:"
>>>> + "\narm_spe_x/llc_miss/"
>>>> + "\narm_spe_x/branch_miss/"
>>>> + "\narm_spe_x/tlb_miss/"
>>>> + "\narm_spe_x/remote_access/"
>>>> + "\n(see 'perf list')\n");
>>>> + evlist__remove(evlist, evsel);
>>>> + evsel__delete(evsel);
>>>> + continue;
>>>> }
>>>> evsel->core.attr.freq = 0;
>>>> evsel->core.attr.sample_period = 1;
>>>> + if (evsel->core.attr.config
>>>> + & GENMASK_ULL(ARM_SPE_EVENT_HI, ARM_SPE_EVENT_LO)) {
>>>> + evsel->core.attr.config |= SPE_ATTR_TS_ENABLE;
>>>> + if (!evsel->core.attr.precise_ip)
>>>> + pr_warning("Warning:\n"
>>>> + "These events are precise ip events,"
>>>> + " please add :p/pp/ppp after the event.\n");
>>>> + }
>>>> +
>>>> arm_spe_evsel = evsel;
>>>> opts->full_auxtrace = true;
>>>> }
>>>> diff --git a/tools/perf/util/arm-spe.c b/tools/perf/util/arm-spe.c
>>>> index e7282c2616f3..0c9d7fa518a5 100644
>>>> --- a/tools/perf/util/arm-spe.c
>>>> +++ b/tools/perf/util/arm-spe.c
>>>> @@ -779,6 +779,31 @@ arm_spe_synth_events(struct arm_spe *spe, struct perf_session *session)
>>>> attr.sample_id_all = evsel->core.attr.sample_id_all;
>>>> attr.read_format = evsel->core.attr.read_format;
>>>>
>>>> + if (evsel->core.attr.config
>>>> + & GENMASK_ULL(ARM_SPE_EVENT_HI,
>>>> + ARM_SPE_EVENT_LO)) {
>>>> + spe->synth_opts.llc_miss = false;
>>>> + spe->synth_opts.tlb_miss = false;
>>>> + spe->synth_opts.branch_miss = false;
>>>> + spe->synth_opts.remote_access = false;
>>>> +
>>>> + if (evsel->core.attr.config
>>>> + & (ARM_SPE_EVENT_LLC_MISS << ARM_SPE_EVENT_LO))
>>>> + spe->synth_opts.llc_miss = true;
>>>> +
>>>> + if (evsel->core.attr.config
>>>> + & (ARM_SPE_EVENT_TLB_MISS << ARM_SPE_EVENT_LO))
>>>> + spe->synth_opts.tlb_miss = true;
>>>> +
>>>> + if (evsel->core.attr.config
>>>> + & (ARM_SPE_EVENT_BRANCH_MISS << ARM_SPE_EVENT_LO))
>>>> + spe->synth_opts.branch_miss = true;
>>>> +
>>>> + if (evsel->core.attr.config
>>>> + & (ARM_SPE_EVENT_REMOTE_ACCESS << ARM_SPE_EVENT_LO))
>>>> + spe->synth_opts.remote_access = true;
>>>> + }
>>>> +
>>>> /* create new id val to be a fixed offset from evsel id */
>>>> id = evsel->core.id[0] + 1000000000;
>>>>
>>>> diff --git a/tools/perf/util/arm-spe.h b/tools/perf/util/arm-spe.h
>>>> index 98d3235781c3..db7420121979 100644
>>>> --- a/tools/perf/util/arm-spe.h
>>>> +++ b/tools/perf/util/arm-spe.h
>>>> @@ -9,6 +9,26 @@
>>>>
>>>> #define ARM_SPE_PMU_NAME "arm_spe_"
>>>>
>>>> +#define ARM_SPE_EVENT_LO 3
>>>> +#define ARM_SPE_EVENT_HI 6
>>>> +#define ARM_SPE_EVENT_LLC_MISS BIT(0)
>>>> +#define ARM_SPE_EVENT_BRANCH_MISS BIT(1)
>>>> +#define ARM_SPE_EVENT_TLB_MISS BIT(2)
>>>> +#define ARM_SPE_EVENT_REMOTE_ACCESS BIT(3)
>>>> +
>>>> +#define SPE_ATTR_TS_ENABLE BIT(0)
>>>> +#define SPE_ATTR_PA_ENABLE BIT(1)
>>>> +#define SPE_ATTR_PCT_ENABLE BIT(2)
>>>> +#define SPE_ATTR_JITTER BIT(16)
>>>> +#define SPE_ATTR_BRANCH_FILTER BIT(32)
>>>> +#define SPE_ATTR_LOAD_FILTER BIT(33)
>>>> +#define SPE_ATTR_STORE_FILTER BIT(34)
>>>> +
>>>> +#define SPE_ATTR_EV_RETIRED BIT(1)
>>>> +#define SPE_ATTR_EV_CACHE BIT(3)
>>>> +#define SPE_ATTR_EV_TLB BIT(5)
>>>> +#define SPE_ATTR_EV_BRANCH BIT(7)
>>>> +
>>>> enum {
>>>> ARM_SPE_PMU_TYPE,
>>>> ARM_SPE_PER_CPU_MMAPS,
>>>>
>>> IMPORTANT NOTICE: The contents of this email and any attachments are confidential and may also be privileged. If you are not the intended recipient, please notify the sender immediately and do not disclose the contents to any other person, use it for any purpose, or store or copy the information in any medium. Thank you.
>>>
>>
>>

Next message: Al Viro: "Re: [PATCH v2 0/6] Delete timespec64_trunc()"
Previous message: Stephen Rothwell: "Re: linux-next: manual merge of the vhost tree with Linus' tree"
Next in thread: James Clark: "Re: [RFC v3 5/5] perf tools: Add support to process multi spe events"
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]