From: Adrian Hunter <adrian.hunter@intel.com>
To: Suzuki K Poulose <suzuki.poulose@arm.com>
Cc: Ingo Molnar <mingo@redhat.com>,
Mark Rutland <mark.rutland@arm.com>,
Alexander Shishkin <alexander.shishkin@linux.intel.com>,
Heiko Carstens <hca@linux.ibm.com>,
Thomas Richter <tmricht@linux.ibm.com>,
Hendrik Brueckner <brueckner@linux.ibm.com>,
Mike Leach <mike.leach@linaro.org>,
James Clark <james.clark@arm.com>,
coresight@lists.linaro.org, linux-arm-kernel@lists.infradead.org,
Yicong Yang <yangyicong@hisilicon.com>,
Jonathan Cameron <jonathan.cameron@huawei.com>,
Will Deacon <will@kernel.org>,
Arnaldo Carvalho de Melo <acme@kernel.org>,
Jiri Olsa <jolsa@kernel.org>, Namhyung Kim <namhyung@kernel.org>,
Ian Rogers <irogers@google.com>,
linux-kernel@vger.kernel.org, linux-perf-users@vger.kernel.org,
Peter Zijlstra <peterz@infradead.org>
Subject: Re: [PATCH RFC V2 1/4] perf/core: Add aux_pause, aux_resume, aux_start_paused
Date: Fri, 5 Jan 2024 14:57:42 +0200 [thread overview]
Message-ID: <4ca142a7-f46e-4bf0-b32d-99b7955fc012@intel.com> (raw)
In-Reply-To: <7023e9fb-0bde-4a17-aa9e-e29e6b8b4bf1@arm.com>
On 20/12/23 19:41, Suzuki K Poulose wrote:
> On 08/12/2023 17:24, Adrian Hunter wrote:
>> Hardware traces, such as instruction traces, can produce a vast amount of
>> trace data, so being able to reduce tracing to more specific circumstances
>> can be useful.
>>
>> The ability to pause or resume tracing when another event happens, can do
>> that.
>>
>> Add ability for an event to "pause" or "resume" AUX area tracing.
>>
>> Add aux_pause bit to perf_event_attr to indicate that, if the event
>> happens, the associated AUX area tracing should be paused. Ditto
>> aux_resume. Do not allow aux_pause and aux_resume to be set together.
>>
>> Add aux_start_paused bit to perf_event_attr to indicate to an AUX area
>> event that it should start in a "paused" state.
>>
>> Add aux_paused to struct perf_event for AUX area events to keep track of
>> the "paused" state. aux_paused is initialized to aux_start_paused.
>>
>> Add PERF_EF_PAUSE and PERF_EF_RESUME modes for ->stop() and ->start()
>> callbacks. Call as needed, during __perf_event_output(). Add
>> aux_in_pause_resume to struct perf_buffer to prevent races with the NMI
>> handler. Pause/resume in NMI context will miss out if it coincides with
>> another pause/resume.
>>
>> To use aux_pause or aux_resume, an event must be in a group with the AUX
>> area event as the group leader.
>>
>> Example (requires Intel PT and tools patches also):
>>
>> $ perf record --kcore -e '{intel_pt/aux-start-paused/k,syscalls:sys_enter_newuname/aux-resume/,syscalls:sys_exit_newuname/aux-pause/}' uname
>> Linux
>> [ perf record: Woken up 1 times to write data ]
>> [ perf record: Captured and wrote 0.041 MB perf.data ]
>> $ perf script --call-trace
>> uname 5712 [007] 83.855580930: name: 0x7ffd9dcebec0
>> uname 5712 [007] 83.855582518: psb offs: 0
>> uname 5712 [007] 83.855582518: cbr: 42 freq: 4205 MHz (150%)
>> uname 5712 [007] 83.855582723: ([kernel.kallsyms]) debug_smp_processor_id
>> uname 5712 [007] 83.855582723: ([kernel.kallsyms]) __x64_sys_newuname
>> uname 5712 [007] 83.855582723: ([kernel.kallsyms]) down_read
>> uname 5712 [007] 83.855582723: ([kernel.kallsyms]) __cond_resched
>> uname 5712 [007] 83.855582932: ([kernel.kallsyms]) preempt_count_add
>> uname 5712 [007] 83.855582932: ([kernel.kallsyms]) in_lock_functions
>> uname 5712 [007] 83.855582932: ([kernel.kallsyms]) preempt_count_sub
>> uname 5712 [007] 83.855582932: ([kernel.kallsyms]) up_read
>> uname 5712 [007] 83.855582932: ([kernel.kallsyms]) preempt_count_add
>> uname 5712 [007] 83.855583348: ([kernel.kallsyms]) in_lock_functions
>> uname 5712 [007] 83.855583348: ([kernel.kallsyms]) preempt_count_sub
>> uname 5712 [007] 83.855583348: ([kernel.kallsyms]) _copy_to_user
>> uname 5712 [007] 83.855583557: ([kernel.kallsyms]) syscall_exit_to_user_mode
>> uname 5712 [007] 83.855583557: ([kernel.kallsyms]) syscall_exit_work
>> uname 5712 [007] 83.855583557: ([kernel.kallsyms]) perf_syscall_exit
>> uname 5712 [007] 83.855583557: ([kernel.kallsyms]) debug_smp_processor_id
>> uname 5712 [007] 83.855583557: ([kernel.kallsyms]) perf_trace_buf_alloc
>> uname 5712 [007] 83.855583557: ([kernel.kallsyms]) perf_swevent_get_recursion_context
>> uname 5712 [007] 83.855583557: ([kernel.kallsyms]) debug_smp_processor_id
>> uname 5712 [007] 83.855583557: ([kernel.kallsyms]) debug_smp_processor_id
>> uname 5712 [007] 83.855583557: ([kernel.kallsyms]) perf_tp_event
>> uname 5712 [007] 83.855583557: ([kernel.kallsyms]) perf_trace_buf_update
>> uname 5712 [007] 83.855583557: ([kernel.kallsyms]) tracing_gen_ctx_irq_test
>> uname 5712 [007] 83.855583557: ([kernel.kallsyms]) perf_swevent_event
>> uname 5712 [007] 83.855583765: ([kernel.kallsyms]) __perf_event_account_interrupt
>> uname 5712 [007] 83.855583765: ([kernel.kallsyms]) __this_cpu_preempt_check
>> uname 5712 [007] 83.855583765: ([kernel.kallsyms]) perf_event_output_forward
>> uname 5712 [007] 83.855583765: ([kernel.kallsyms]) perf_event_aux_pause
>> uname 5712 [007] 83.855583765: ([kernel.kallsyms]) ring_buffer_get
>> uname 5712 [007] 83.855583765: ([kernel.kallsyms]) __rcu_read_lock
>> uname 5712 [007] 83.855583765: ([kernel.kallsyms]) __rcu_read_unlock
>> uname 5712 [007] 83.855583765: ([kernel.kallsyms]) pt_event_stop
>> uname 5712 [007] 83.855583765: ([kernel.kallsyms]) debug_smp_processor_id
>> uname 5712 [007] 83.855583765: ([kernel.kallsyms]) debug_smp_processor_id
>> uname 5712 [007] 83.855583973: ([kernel.kallsyms]) native_write_msr
>> uname 5712 [007] 83.855583973: ([kernel.kallsyms]) native_write_msr
>> uname 5712 [007] 83.855584175: 0x0
>>
>> Signed-off-by: Adrian Hunter <adrian.hunter@intel.com>
>> ---
>> include/linux/perf_event.h | 15 +++++++
>> include/uapi/linux/perf_event.h | 11 ++++-
>> kernel/events/core.c | 72 +++++++++++++++++++++++++++++++--
>> kernel/events/internal.h | 1 +
>> 4 files changed, 95 insertions(+), 4 deletions(-)
>>
>> diff --git a/include/linux/perf_event.h b/include/linux/perf_event.h
>> index e85cd1c0eaf3..252c4aac3b79 100644
>> --- a/include/linux/perf_event.h
>> +++ b/include/linux/perf_event.h
>> @@ -291,6 +291,7 @@ struct perf_event_pmu_context;
>> #define PERF_PMU_CAP_NO_EXCLUDE 0x0040
>> #define PERF_PMU_CAP_AUX_OUTPUT 0x0080
>> #define PERF_PMU_CAP_EXTENDED_HW_TYPE 0x0100
>> +#define PERF_PMU_CAP_AUX_PAUSE 0x0200
>> struct perf_output_handle;
>> @@ -363,6 +364,8 @@ struct pmu {
>> #define PERF_EF_START 0x01 /* start the counter when adding */
>> #define PERF_EF_RELOAD 0x02 /* reload the counter when starting */
>> #define PERF_EF_UPDATE 0x04 /* update the counter when stopping */
>> +#define PERF_EF_PAUSE 0x08 /* AUX area event, pause tracing */
>> +#define PERF_EF_RESUME 0x10 /* AUX area event, resume tracing */
>> /*
>> * Adds/Removes a counter to/from the PMU, can be done inside a
>> @@ -402,6 +405,15 @@ struct pmu {
>> *
>> * ->start() with PERF_EF_RELOAD will reprogram the counter
>> * value, must be preceded by a ->stop() with PERF_EF_UPDATE.
>> + *
>> + * ->stop() with PERF_EF_PAUSE will stop as simply as possible. Will not
>> + * overlap another ->stop() with PERF_EF_PAUSE nor ->start() with
>> + * PERF_EF_RESUME.
>> + *
>> + * ->start() with PERF_EF_RESUME will start as simply as possible but
>> + * only if the counter is not otherwise stopped. Will not overlap
>> + * another ->start() with PERF_EF_RESUME nor ->stop() with
>> + * PERF_EF_PAUSE.
>> */
>> void (*start) (struct perf_event *event, int flags);
>> void (*stop) (struct perf_event *event, int flags);
>> @@ -797,6 +809,9 @@ struct perf_event {
>> /* for aux_output events */
>> struct perf_event *aux_event;
>> + /* for AUX area events */
>> + unsigned int aux_paused;
>> +
>> void (*destroy)(struct perf_event *);
>> struct rcu_head rcu_head;
>> diff --git a/include/uapi/linux/perf_event.h b/include/uapi/linux/perf_event.h
>> index 39c6a250dd1b..437bc2a8d50c 100644
>> --- a/include/uapi/linux/perf_event.h
>> +++ b/include/uapi/linux/perf_event.h
>> @@ -507,7 +507,16 @@ struct perf_event_attr {
>> __u16 sample_max_stack;
>> __u16 __reserved_2;
>> __u32 aux_sample_size;
>> - __u32 __reserved_3;
>> +
>> + union {
>> + __u32 aux_output_cfg;
>> + struct {
>> + __u64 aux_pause : 1, /* on overflow, pause AUX area tracing */
>
> Did you mean __u32 ? Otherwise look good to me.
True, thanks!
next prev parent reply other threads:[~2024-01-05 12:57 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-08 17:24 [PATCH RFC V2 0/4] perf/core: Add ability for an event to "pause" or "resume" AUX area tracing Adrian Hunter
2023-12-08 17:24 ` [PATCH RFC V2 1/4] perf/core: Add aux_pause, aux_resume, aux_start_paused Adrian Hunter
2023-12-19 13:42 ` Arnaldo Carvalho de Melo
2023-12-20 15:54 ` James Clark
2023-12-20 16:16 ` Adrian Hunter
2023-12-21 10:05 ` James Clark
2023-12-20 17:41 ` Suzuki K Poulose
2024-01-05 12:57 ` Adrian Hunter [this message]
2023-12-08 17:24 ` [PATCH RFC V2 2/4] perf/x86/intel/pt: Add support for pause / resume Adrian Hunter
2023-12-08 17:24 ` [PATCH RFC V2 3/4] perf tools: Add support for AUX area " Adrian Hunter
2023-12-08 17:24 ` [PATCH RFC V2 4/4] coresight: Have a stab at support for " Adrian Hunter
2023-12-15 6:42 ` [PATCH RFC V3 " Adrian Hunter
2023-12-20 15:59 ` James Clark
2024-01-05 12:56 ` Adrian Hunter
2023-12-19 6:05 ` [PATCH RFC V2 0/4] perf/core: Add ability for an event to "pause" or "resume" AUX area tracing Adrian Hunter
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4ca142a7-f46e-4bf0-b32d-99b7955fc012@intel.com \
--to=adrian.hunter@intel.com \
--cc=acme@kernel.org \
--cc=alexander.shishkin@linux.intel.com \
--cc=brueckner@linux.ibm.com \
--cc=coresight@lists.linaro.org \
--cc=hca@linux.ibm.com \
--cc=irogers@google.com \
--cc=james.clark@arm.com \
--cc=jolsa@kernel.org \
--cc=jonathan.cameron@huawei.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=mike.leach@linaro.org \
--cc=mingo@redhat.com \
--cc=namhyung@kernel.org \
--cc=peterz@infradead.org \
--cc=suzuki.poulose@arm.com \
--cc=tmricht@linux.ibm.com \
--cc=will@kernel.org \
--cc=yangyicong@hisilicon.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®