From: Namhyung Kim <namhyung@kernel.org>
To: Yeo Reum Yun <YeoReum.Yun@arm.com>
Cc: "linux-perf-users@vger.kernel.org"
<linux-perf-users@vger.kernel.org>,
"mhiramat@kernel.org" <mhiramat@kernel.org>,
"mathieu.desnoyers@efficios.com" <mathieu.desnoyers@efficios.com>,
"a.p.zijlstra@chello.nl" <a.p.zijlstra@chello.nl>,
"mingo@elte.hu" <mingo@elte.hu>,
Mark Rutland <Mark.Rutland@arm.com>,
"james.clark@linaro.org" <james.clark@linaro.org>,
nd <nd@arm.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-trace-kernel@vger.kernel.org"
<linux-trace-kernel@vger.kernel.org>,
Peter Zijlstra <peterz@infradead.org>,
Frederic Weisbecker <fweisbec@gmail.com>,
Arnaldo Carvalho de Melo <acme@kernel.org>,
Steven Rostedt <rostedt@goodmis.org>
Subject: Re: [PATCH v2] trace/trace_event_perf: remove duplicate samples on the first tracepoint event
Date: Thu, 3 Oct 2024 17:44:40 -0700 [thread overview]
Message-ID: <Zv86eKWFcSOnzS4J@google.com> (raw)
In-Reply-To: <GV1PR08MB10521EC72BDB730710F3973D4FB772@GV1PR08MB10521.eurprd08.prod.outlook.com>
Hello,
On Tue, Oct 01, 2024 at 08:48:45AM +0000, Yeo Reum Yun wrote:
> Gentle ping in case of forgotten.
>
> ________________________________________
> From: Steven Rostedt <rostedt@goodmis.org>
> Sent: 26 September 2024 13:51
> To: Yeo Reum Yun
> Cc: mhiramat@kernel.org; mathieu.desnoyers@efficios.com; a.p.zijlstra@chello.nl; mingo@elte.hu; Mark Rutland; james.clark@linaro.org; nd; linux-kernel@vger.kernel.org; linux-trace-kernel@vger.kernel.org; Peter Zijlstra; Frederic Weisbecker; Arnaldo Carvalho de Melo; Namhyung Kim
> Subject: Re: [PATCH v2] trace/trace_event_perf: remove duplicate samples on the first tracepoint event
>
> Can one of the perf folks give me an Ack, and I'll take this through my tree.
I'm not sure if we want to support freq mode or period other than 1 for
tracepoint events. But it looks broken apparently, so
Acked-by: Namhyung Kim <namhyung@kernel.org>
Thanks,
Namhyung
>
> On Fri, 13 Sep 2024 03:13:47 +0100
> Levi Yun <yeoreum.yun@arm.com> wrote:
>
> > When a tracepoint event is created with attr.freq = 1,
> > 'hwc->period_left' is not initialized correctly. As a result,
> > in the perf_swevent_overflow() function, when the first time the event occurs,
> > it calculates the event overflow and the perf_swevent_set_period() returns 3,
> > this leads to the event are recorded for three duplicate times.
> >
> > Step to reproduce:
> > 1. Enable the tracepoint event & starting tracing
> > $ echo 1 > /sys/kernel/tracing/events/module/module_free
> > $ echo 1 > /sys/kernel/tracing/tracing_on
> >
> > 2. Record with perf
> > $ perf record -a --strict-freq -F 1 -e "module:module_free"
> >
> > 3. Trigger module_free event.
> > $ modprobe -i sunrpc
> > $ modprobe -r sunrpc
> >
> > Result:
> > - Trace pipe result:
> > $ cat trace_pipe
> > modprobe-174509 [003] ..... 6504.868896: module_free: sunrpc
> >
> > - perf sample:
> > modprobe 174509 [003] 6504.868980: module:module_free: sunrpc
> > modprobe 174509 [003] 6504.868980: module:module_free: sunrpc
> > modprobe 174509 [003] 6504.868980: module:module_free: sunrpc
> >
> > By setting period_left via perf_swevent_set_period() as other sw_event did,
> > This problem could be solved.
> >
> > After patch:
> > - Trace pipe result:
> > $ cat trace_pipe
> > modprobe 1153096 [068] 613468.867774: module:module_free: xfs
> >
> > - perf sample
> > modprobe 1153096 [068] 613468.867794: module:module_free: xfs
> >
> > Fixes: bd2b5b12849a ("perf_counter: More aggressive frequency adjustment")
> > Signed-off-by: Levi Yun <yeoreum.yun@arm.com>
> > ---
> > Changes in v2:
> > - Fix build error.
> > ---
> > kernel/trace/trace_event_perf.c | 6 ++++++
> > 1 file changed, 6 insertions(+)
> >
> > diff --git a/kernel/trace/trace_event_perf.c b/kernel/trace/trace_event_perf.c
> > index 05e791241812..3ff9caa4a71b 100644
> > --- a/kernel/trace/trace_event_perf.c
> > +++ b/kernel/trace/trace_event_perf.c
> > @@ -352,10 +352,16 @@ void perf_uprobe_destroy(struct perf_event *p_event)
> > int perf_trace_add(struct perf_event *p_event, int flags)
> > {
> > struct trace_event_call *tp_event = p_event->tp_event;
> > + struct hw_perf_event *hwc = &p_event->hw;
> >
> > if (!(flags & PERF_EF_START))
> > p_event->hw.state = PERF_HES_STOPPED;
> >
> > + if (is_sampling_event(p_event)) {
> > + hwc->last_period = hwc->sample_period;
> > + perf_swevent_set_period(p_event);
> > + }
> > +
> > /*
> > * If TRACE_REG_PERF_ADD returns false; no custom action was performed
> > * and we need to take the default action of enqueueing our event on
> > --
> > LEVI:{C3F47F37-75D8-414A-A8BA-3980EC8A46D7}
>
prev parent reply other threads:[~2024-10-04 0:44 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-13 2:13 [PATCH v2] trace/trace_event_perf: remove duplicate samples on the first tracepoint event Levi Yun
2024-09-24 7:13 ` Yeo Reum Yun
2024-09-26 12:51 ` Steven Rostedt
2024-10-01 8:48 ` Yeo Reum Yun
2024-10-04 0:44 ` Namhyung Kim [this message]
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=Zv86eKWFcSOnzS4J@google.com \
--to=namhyung@kernel.org \
--cc=Mark.Rutland@arm.com \
--cc=YeoReum.Yun@arm.com \
--cc=a.p.zijlstra@chello.nl \
--cc=acme@kernel.org \
--cc=fweisbec@gmail.com \
--cc=james.clark@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=linux-trace-kernel@vger.kernel.org \
--cc=mathieu.desnoyers@efficios.com \
--cc=mhiramat@kernel.org \
--cc=mingo@elte.hu \
--cc=nd@arm.com \
--cc=peterz@infradead.org \
--cc=rostedt@goodmis.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.