From: Anshuman Khandual <anshuman.khandual@arm.com>
To: German Gomez <german.gomez@arm.com>,
linux-kernel@vger.kernel.org, linux-perf-users@vger.kernel.org,
peterz@infradead.org, alexander.shishkin@linux.intel.com,
jolsa@redhat.com, acme@kernel.org
Cc: Robin Murphy <robin.murphy@arm.com>,
Suzuki Poulose <suzuki.poulose@arm.com>,
James Clark <james.clark@arm.com>, Ingo Molnar <mingo@redhat.com>,
Mark Rutland <mark.rutland@arm.com>,
Namhyung Kim <namhyung@kernel.org>,
Thomas Gleixner <tglx@linutronix.de>,
Will Deacon <will@kernel.org>,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH V6 6/8] perf/tools: Extend branch type classification
Date: Wed, 15 Jun 2022 08:51:40 +0530 [thread overview]
Message-ID: <8bfce917-84a6-23a2-d926-a1efa901f4f1@arm.com> (raw)
In-Reply-To: <e0f29bc9-eae4-e433-2d4e-4dd53e31967d@arm.com>
On 6/14/22 22:23, German Gomez wrote:
> Hi Anshuman,
>
> On 10/06/2022 04:50, Anshuman Khandual wrote:
>> This updates the perf tool with generic branch type classification with new
>> ABI extender place holder i.e PERF_BR_EXTEND_ABI, the new 4 bit branch type
>> field i.e perf_branch_entry.new_type, new generic page fault related branch
>> types and some arch specific branch types as added earlier in the kernel.
>>
>> Cc: Peter Zijlstra <peterz@infradead.org>
>> Cc: Ingo Molnar <mingo@redhat.com>
>> Cc: Arnaldo Carvalho de Melo <acme@kernel.org>
>> Cc: Mark Rutland <mark.rutland@arm.com>
>> Cc: Alexander Shishkin <alexander.shishkin@linux.intel.com>
>> Cc: Jiri Olsa <jolsa@redhat.com>
>> Cc: Namhyung Kim <namhyung@kernel.org>
>> Cc: Thomas Gleixner <tglx@linutronix.de>
>> Cc: Will Deacon <will@kernel.org>
>> Cc: linux-arm-kernel@lists.infradead.org
>> Cc: linux-perf-users@vger.kernel.org
>> Cc: linux-kernel@vger.kernel.org
>> Signed-off-by: Anshuman Khandual <anshuman.khandual@arm.com>
>> ---
>> tools/include/uapi/linux/perf_event.h | 16 ++++++++-
>> tools/perf/builtin-script.c | 2 +-
>> tools/perf/util/branch.c | 52 ++++++++++++++++++++++++++-
>> tools/perf/util/branch.h | 6 +++-
>> tools/perf/util/session.c | 2 +-
>> 5 files changed, 73 insertions(+), 5 deletions(-)
>>
>> diff --git a/tools/include/uapi/linux/perf_event.h b/tools/include/uapi/linux/perf_event.h
>> index 26d8f0b5ac0d..d29280adc3c4 100644
>> --- a/tools/include/uapi/linux/perf_event.h
>> +++ b/tools/include/uapi/linux/perf_event.h
>> @@ -255,9 +255,22 @@ enum {
>> PERF_BR_IRQ = 12, /* irq */
>> PERF_BR_SERROR = 13, /* system error */
>> PERF_BR_NO_TX = 14, /* not in transaction */
>> + PERF_BR_EXTEND_ABI = 15, /* extend ABI */
>> PERF_BR_MAX,
>> };
>>
>> +enum {
>> + PERF_BR_NEW_FAULT_ALGN = 0, /* Alignment fault */
>> + PERF_BR_NEW_FAULT_DATA = 1, /* Data fault */
>> + PERF_BR_NEW_FAULT_INST = 2, /* Inst fault */
>> + PERF_BR_NEW_ARCH_1 = 3, /* Architecture specific */
>> + PERF_BR_NEW_ARCH_2 = 4, /* Architecture specific */
>> + PERF_BR_NEW_ARCH_3 = 5, /* Architecture specific */
>> + PERF_BR_NEW_ARCH_4 = 6, /* Architecture specific */
>> + PERF_BR_NEW_ARCH_5 = 7, /* Architecture specific */
>> + PERF_BR_NEW_MAX,
>> +};
>> +
>> #define PERF_SAMPLE_BRANCH_PLM_ALL \
>> (PERF_SAMPLE_BRANCH_USER|\
>> PERF_SAMPLE_BRANCH_KERNEL|\
>> @@ -1372,7 +1385,8 @@ struct perf_branch_entry {
>> abort:1, /* transaction abort */
>> cycles:16, /* cycle count to last branch */
>> type:4, /* branch type */
>> - reserved:40;
>> + new_type:4, /* additional branch type */
>> + reserved:36;
>> };
>>
>> union perf_sample_weight {
>> diff --git a/tools/perf/builtin-script.c b/tools/perf/builtin-script.c
>> index c689054002cc..d4d581230f23 100644
>> --- a/tools/perf/builtin-script.c
>> +++ b/tools/perf/builtin-script.c
>> @@ -866,7 +866,7 @@ static int print_bstack_flags(FILE *fp, struct branch_entry *br)
>> br->flags.in_tx ? 'X' : '-',
>> br->flags.abort ? 'A' : '-',
>> br->flags.cycles,
>> - br->flags.type ? branch_type_name(br->flags.type) : "-");
>> + get_branch_type(br));
> (Small comment below regarding this line)
>
>> }
>>
>> static int perf_sample__fprintf_brstack(struct perf_sample *sample,
>> diff --git a/tools/perf/util/branch.c b/tools/perf/util/branch.c
>> index abc673347bee..6d962b0a4532 100644
>> --- a/tools/perf/util/branch.c
>> +++ b/tools/perf/util/branch.c
>> @@ -21,7 +21,10 @@ void branch_type_count(struct branch_type_stat *st, struct branch_flags *flags,
>> if (flags->type == PERF_BR_UNKNOWN || from == 0)
>> return;
>>
>> - st->counts[flags->type]++;
>> + if (flags->type == PERF_BR_EXTEND_ABI)
>> + st->new_counts[flags->new_type]++;
>> + else
>> + st->counts[flags->type]++;
>>
>> if (flags->type == PERF_BR_COND) {
>> if (to > from)
>> @@ -36,6 +39,25 @@ void branch_type_count(struct branch_type_stat *st, struct branch_flags *flags,
>> st->cross_4k++;
>> }
>>
>> +const char *branch_new_type_name(int new_type)
>> +{
>> + const char *branch_new_names[PERF_BR_NEW_MAX] = {
>> + "FAULT_ALGN",
>> + "FAULT_DATA",
>> + "FAULT_INST",
>> + "ARCH_1",
>> + "ARCH_2",
>> + "ARCH_3",
>> + "ARCH_4",
>> + "ARCH_5"
>> + };
>> +
>> + if (new_type >= 0 && new_type < PERF_BR_NEW_MAX)
>> + return branch_new_names[new_type];
>> +
>> + return NULL;
>> +}
>> +
>> const char *branch_type_name(int type)
>> {
>> const char *branch_names[PERF_BR_MAX] = {
>> @@ -62,6 +84,17 @@ const char *branch_type_name(int type)
>> return NULL;
>> }
>>
>> +const char *get_branch_type(struct branch_entry *e)
>> +{
>> + if (e->flags.type == PERF_BR_UNKNOWN)
>> + return "";
> There is a small change of behavior in "perf script --field brstack".
> Unknown branches were printed as "-" before but now it's an empty
> string.
get_branch_type() replaces print output in two different functions.
branch_stack__printf() used to print a space " " for PERF_BR_UNKNOWN,
and print_bstack_flags() used to print a "-" for PERF_BR_UNKNOWN.
When they are factorized via get_branch_type(), one of those print
formats need to be choosen.
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2022-06-15 3:23 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-10 3:50 [PATCH V6 0/8] perf: Expand perf_branch_entry Anshuman Khandual
2022-06-10 3:50 ` [PATCH V6 1/8] perf: Add system error and not in transaction branch types Anshuman Khandual
2022-06-10 3:50 ` [PATCH V6 2/8] perf: Extend branch type classification Anshuman Khandual
2022-06-10 3:50 ` [PATCH V6 3/8] perf: Capture branch privilege information Anshuman Khandual
2022-06-10 3:50 ` [PATCH V6 4/8] perf: Add PERF_BR_NEW_ARCH_[N] map for BRBE on arm64 platform Anshuman Khandual
2022-06-10 3:50 ` [PATCH V6 5/8] perf/tools: Add system error and not in transaction branch types Anshuman Khandual
2022-06-10 3:50 ` [PATCH V6 6/8] perf/tools: Extend branch type classification Anshuman Khandual
2022-06-14 16:53 ` German Gomez
2022-06-15 3:21 ` Anshuman Khandual [this message]
2022-06-15 13:39 ` German Gomez
2022-06-10 3:51 ` [PATCH V6 7/8] perf/tools: Add branch privilege information request flag Anshuman Khandual
2022-06-10 3:51 ` [PATCH V6 8/8] perf/tools: Add PERF_BR_NEW_ARCH_[N] map for BRBE on arm64 platform Anshuman Khandual
2022-06-13 9:06 ` [PATCH V6 0/8] perf: Expand perf_branch_entry Anshuman Khandual
2022-06-29 4:44 ` Anshuman Khandual
2022-07-13 5:40 ` Anshuman Khandual
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=8bfce917-84a6-23a2-d926-a1efa901f4f1@arm.com \
--to=anshuman.khandual@arm.com \
--cc=acme@kernel.org \
--cc=alexander.shishkin@linux.intel.com \
--cc=german.gomez@arm.com \
--cc=james.clark@arm.com \
--cc=jolsa@redhat.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=mingo@redhat.com \
--cc=namhyung@kernel.org \
--cc=peterz@infradead.org \
--cc=robin.murphy@arm.com \
--cc=suzuki.poulose@arm.com \
--cc=tglx@linutronix.de \
--cc=will@kernel.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 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).