From: Leo Yan <leo.yan@arm.com>
To: James Clark <james.clark@linaro.org>
Cc: Peter Zijlstra <peterz@infradead.org>,
Ingo Molnar <mingo@redhat.com>,
Arnaldo Carvalho de Melo <acme@kernel.org>,
Namhyung Kim <namhyung@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
Alexander Shishkin <alexander.shishkin@linux.intel.com>,
Jiri Olsa <jolsa@kernel.org>, Ian Rogers <irogers@google.com>,
Adrian Hunter <adrian.hunter@intel.com>,
"Liang, Kan" <kan.liang@linux.intel.com>,
Marco Elver <elver@google.com>,
Sebastian Andrzej Siewior <bigeasy@linutronix.de>,
linux-perf-users@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] perf/aux: Properly launch pending disable flow
Date: Tue, 24 Jun 2025 14:32:17 +0100 [thread overview]
Message-ID: <20250624133217.GO794930@e132581.arm.com> (raw)
In-Reply-To: <d87ddbbb-862d-4cf7-b2c4-a5eb0d072a33@linaro.org>
On Tue, Jun 24, 2025 at 02:11:38PM +0100, James Clark wrote:
[...]
> > @@ -441,7 +441,7 @@ void *perf_aux_output_begin(struct perf_output_handle *handle,
> > * store that will be enabled on successful return
> > */
> > if (!handle->size) { /* A, matches D */
> > - event->pending_disable = smp_processor_id();
> > + perf_event_disable_inatomic(handle->event);
> > perf_output_wakeup(handle);
> > WRITE_ONCE(rb->aux_nest, 0);
> > goto err_put;
> > @@ -526,7 +526,7 @@ void perf_aux_output_end(struct perf_output_handle *handle, unsigned long size)
> > if (wakeup) {
> > if (handle->aux_flags & PERF_AUX_FLAG_TRUNCATED)
> > - handle->event->pending_disable = smp_processor_id();
> > + perf_event_disable_inatomic(handle->event);
> > perf_output_wakeup(handle);
> > }
>
> The types are now a bit misleading and pending_wakeup and pending_disable
> could be bool types. The other pending_*s do use their types properly
> though.
>
> __perf_pending_disable() also still contains a big comment that describes
> use of CPU ID and -1 values.
I might use an extra patch to address type and comment issue.
> Other than that it makes sense.
>
> Reviewed-by: James Clark <james.clark@linaro.org>
Thanks for review!
next prev parent reply other threads:[~2025-06-24 13:32 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-22 15:05 [PATCH] perf/aux: Properly launch pending disable flow Leo Yan
2025-06-09 12:57 ` Leo Yan
2025-06-19 16:52 ` Leo Yan
2025-06-09 14:57 ` Yeoreum Yun
2025-06-24 13:11 ` James Clark
2025-06-24 13:32 ` Leo Yan [this message]
2025-06-25 17:18 ` Leo Yan
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=20250624133217.GO794930@e132581.arm.com \
--to=leo.yan@arm.com \
--cc=acme@kernel.org \
--cc=adrian.hunter@intel.com \
--cc=alexander.shishkin@linux.intel.com \
--cc=bigeasy@linutronix.de \
--cc=elver@google.com \
--cc=irogers@google.com \
--cc=james.clark@linaro.org \
--cc=jolsa@kernel.org \
--cc=kan.liang@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=mingo@redhat.com \
--cc=namhyung@kernel.org \
--cc=peterz@infradead.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.