From: Adrian Hunter <adrian.hunter@intel.com>
To: Arnaldo Carvalho de Melo <acme@kernel.org>,
Namhyung Kim <namhyung@kernel.org>
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>,
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>, Jiri Olsa <jolsa@kernel.org>,
Ian Rogers <irogers@google.com>, Andi Kleen <ak@linux.intel.com>,
linux-kernel@vger.kernel.org, linux-perf-users@vger.kernel.org,
Leo Yan <leo.yan@arm.com>, Peter Zijlstra <peterz@infradead.org>
Subject: Re: [PATCH V9 06/13] perf tools: Enable evsel__is_aux_event() to work for S390_CPUMSF
Date: Tue, 23 Jul 2024 12:09:46 +0300 [thread overview]
Message-ID: <cb2433e2-d6a3-4d70-9b88-0047a9dd01d2@intel.com> (raw)
In-Reply-To: <dbfae024-c7ce-4311-9f7b-419aacc7e7d9@arm.com>
On 23/07/24 11:26, Leo Yan wrote:
> On 7/15/2024 5:07 PM, Adrian Hunter wrote:
>>
>> evsel__is_aux_event() identifies AUX area tracing selected events.
>>
>> S390_CPUMSF uses a raw event type (PERF_TYPE_RAW - refer
>> s390_cpumsf_evsel_is_auxtrace()) not a PMU type value that could be checked
>> in evsel__is_aux_event(). However it sets needs_auxtrace_mmap (refer
>> auxtrace_record__init()), so check that first.
>>
>> Currently, the features that use evsel__is_aux_event() are used only by
>> Intel PT, but that may change in the future.
>>
>> Signed-off-by: Adrian Hunter <adrian.hunter@intel.com>
>> Acked-by: Ian Rogers <irogers@google.com>
>> Reviewed-by: Andi Kleen <ak@linux.intel.com>
>
> Reviewed-by: Leo Yan <leo.yan@arm.com>
Namhyung, could we get patches 5 and 6 from this series
applied? They are independent and Leo's new patch set is
dependent on patch 5.
>
>> ---
>> tools/perf/util/pmu.c | 6 +++++-
>> 1 file changed, 5 insertions(+), 1 deletion(-)
>>
>> diff --git a/tools/perf/util/pmu.c b/tools/perf/util/pmu.c
>> index 986166bc7c78..0b38c51bd6eb 100644
>> --- a/tools/perf/util/pmu.c
>> +++ b/tools/perf/util/pmu.c
>> @@ -1199,8 +1199,12 @@ void perf_pmu__warn_invalid_formats(struct perf_pmu *pmu)
>>
>> bool evsel__is_aux_event(const struct evsel *evsel)
>> {
>> - struct perf_pmu *pmu = evsel__find_pmu(evsel);
>> + struct perf_pmu *pmu;
>>
>> + if (evsel->needs_auxtrace_mmap)
>> + return true;
>> +
>> + pmu = evsel__find_pmu(evsel);
>> return pmu && pmu->auxtrace;
>> }
>>
>> --
>> 2.34.1
>>
>>
next prev parent reply other threads:[~2024-07-23 9:09 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-15 16:06 [PATCH V9 00/13] perf/core: Add ability for an event to "pause" or "resume" AUX area tracing Adrian Hunter
2024-07-15 16:07 ` [PATCH V9 01/13] perf/x86/intel/pt: Fix sampling synchronization Adrian Hunter
2024-07-15 16:07 ` [PATCH V9 02/13] perf/core: Add aux_pause, aux_resume, aux_start_paused Adrian Hunter
2024-07-18 9:38 ` Peter Zijlstra
2024-07-18 11:19 ` Adrian Hunter
2024-07-18 11:51 ` Peter Zijlstra
2024-07-18 12:58 ` Peter Zijlstra
2024-07-18 15:06 ` Adrian Hunter
2024-07-26 14:41 ` Arnaldo Carvalho de Melo
2024-07-26 16:00 ` Adrian Hunter
2024-07-26 18:24 ` Arnaldo Carvalho de Melo
2024-07-15 16:07 ` [PATCH V9 03/13] perf/x86/intel/pt: Add support for pause / resume Adrian Hunter
2024-07-15 16:07 ` [PATCH V9 04/13] perf/x86/intel: Do not enable large PEBS for events with aux actions or aux sampling Adrian Hunter
2024-07-15 16:07 ` [PATCH V9 05/13] perf tools: Enable evsel__is_aux_event() to work for ARM/ARM64 Adrian Hunter
2024-07-22 15:13 ` Leo Yan
2024-07-15 16:07 ` [PATCH V9 06/13] perf tools: Enable evsel__is_aux_event() to work for S390_CPUMSF Adrian Hunter
2024-07-23 8:26 ` Leo Yan
2024-07-23 9:09 ` Adrian Hunter [this message]
2024-07-26 14:46 ` Arnaldo Carvalho de Melo
2024-07-15 16:07 ` [PATCH V9 07/13] perf tools: Add aux_start_paused, aux_pause and aux_resume Adrian Hunter
2024-07-15 16:07 ` [PATCH V9 08/13] perf tools: Add aux-action config term Adrian Hunter
2024-07-15 16:07 ` [PATCH V9 09/13] perf tools: Parse aux-action Adrian Hunter
2024-07-15 16:07 ` [PATCH V9 10/13] perf tools: Add missing_features for aux_start_paused, aux_pause, aux_resume Adrian Hunter
2024-07-15 16:07 ` [PATCH V9 11/13] perf intel-pt: Improve man page format Adrian Hunter
2024-07-15 16:07 ` [PATCH V9 12/13] perf intel-pt: Add documentation for pause / resume Adrian Hunter
2024-07-15 16:07 ` [PATCH V9 13/13] perf intel-pt: Add a test " 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=cb2433e2-d6a3-4d70-9b88-0047a9dd01d2@intel.com \
--to=adrian.hunter@intel.com \
--cc=acme@kernel.org \
--cc=ak@linux.intel.com \
--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=leo.yan@arm.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;
as well as URLs for NNTP newsgroup(s).