From: Adrian Hunter <adrian.hunter@intel.com>
To: James Clark <james.clark@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>,
Suzuki K Poulose <suzuki.poulose@arm.com>,
Mike Leach <mike.leach@linaro.org>,
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 V3 4/4] coresight: Have a stab at support for pause / resume
Date: Fri, 5 Jan 2024 14:56:37 +0200 [thread overview]
Message-ID: <ce87308f-1b9b-41b1-8282-04c81d316c58@intel.com> (raw)
In-Reply-To: <e80f75ea-99e9-e4d2-6477-443e521ef90a@arm.com>
On 20/12/23 17:59, James Clark wrote:
>
>
> On 15/12/2023 06:42, Adrian Hunter wrote:
>> For discussion only, un-tested...
>>
>
> If anyone wants to test Coresight, the diff below is required to get the
> most basic use case working. It also probably needs more thought and
> some edge case handling:
Makes sense to me
>
> diff --git a/drivers/hwtracing/coresight/coresight-etm-perf.c b/drivers/hwtracing/coresight/coresight-etm-perf.c
> index 596c01e37624..bd0767356277 100644
> --- a/drivers/hwtracing/coresight/coresight-etm-perf.c
> +++ b/drivers/hwtracing/coresight/coresight-etm-perf.c
> @@ -556,7 +556,8 @@ static void etm_event_stop(struct perf_event *event, int mode)
> struct etm_event_data *event_data;
> struct list_head *path;
>
> - if (mode & PERF_EF_PAUSE && !READ_ONCE(ctxt->pr_allowed))
> + if ((mode & PERF_EF_PAUSE && !READ_ONCE(ctxt->pr_allowed)) ||
> + event->hw.state == PERF_HES_STOPPED)
> return;
>
> WRITE_ONCE(ctxt->pr_allowed, 0);
> @@ -573,9 +574,6 @@ static void etm_event_stop(struct perf_event *event, int mode)
> /* Clear the event_data as this ETM is stopping the trace. */
> ctxt->event_data = NULL;
>
> - if (event->hw.state == PERF_HES_STOPPED)
> - goto out_pr_allowed;
> -
> /* We must have a valid event_data for a running event */
> if (WARN_ON(!event_data))
> return;
> @@ -586,7 +584,7 @@ static void etm_event_stop(struct perf_event *event, int mode)
> * nothing needs to be torn down other than outputting a
> * zero sized record.
> */
> - if (handle->event && (mode & PERF_EF_UPDATE) &&
> + if (handle->event && (mode & (PERF_EF_UPDATE | PERF_EF_PAUSE)) &&
> !cpumask_test_cpu(cpu, &event_data->mask)) {
> event->hw.state = PERF_HES_STOPPED;
> perf_aux_output_end(handle, 0);
> @@ -616,7 +614,7 @@ static void etm_event_stop(struct perf_event *event, int mode)
> * handle due to lack of buffer space), we don't
> * have to do anything here.
> */
> - if (handle->event && (mode & PERF_EF_UPDATE)) {
> + if (handle->event && (mode & (PERF_EF_UPDATE | PERF_EF_PAUSE))) {
> if (WARN_ON_ONCE(handle->event != event))
> return;
>
> @@ -646,7 +644,6 @@ static void etm_event_stop(struct perf_event *event, int mode)
> /* Disabling the path make its elements available to other sessions */
> coresight_disable_path(path);
>
> -out_pr_allowed:
> if (mode & PERF_EF_PAUSE)
> WRITE_ONCE(ctxt->pr_allowed, 1);
> }
> @@ -656,7 +653,7 @@ static int etm_event_add(struct perf_event *event, int mode)
> int ret = 0;
> struct hw_perf_event *hwc = &event->hw;
>
> - if (mode & PERF_EF_START && !READ_ONCE(event->aux_paused)) {
> + if (mode & PERF_EF_START) {
> etm_event_start(event, 0);
> if (hwc->state & PERF_HES_STOPPED)
> ret = -EINVAL;
next prev parent reply other threads:[~2024-01-05 12:56 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
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 [this message]
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=ce87308f-1b9b-41b1-8282-04c81d316c58@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®