From: Anshuman Khandual <anshuman.khandual@arm.com>
To: linux-kernel@vger.kernel.org, linux-perf-users@vger.kernel.org,
linux-arm-kernel@lists.infradead.org
Cc: robh@kernel.org, Anshuman Khandual <anshuman.khandual@arm.com>,
Peter Zijlstra <peterz@infradead.org>,
Ingo Molnar <mingo@redhat.com>,
Arnaldo Carvalho de Melo <acme@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
Alexander Shishkin <alexander.shishkin@linux.intel.com>,
Jiri Olsa <jolsa@redhat.com>, Namhyung Kim <namhyung@kernel.org>,
Will Deacon <will@kernel.org>
Subject: [PATCH 2/2] perf: Expand perf_branch_entry.type
Date: Fri, 28 Jan 2022 11:14:13 +0530 [thread overview]
Message-ID: <1643348653-24367-3-git-send-email-anshuman.khandual@arm.com> (raw)
In-Reply-To: <1643348653-24367-1-git-send-email-anshuman.khandual@arm.com>
Current perf_branch_entry.type is a 4 bits field just enough to accommodate
16 generic branch types. This is insufficient to accommodate platforms like
arm64 which has much more branch types. Lets just expands this field into a
6 bits one, which can now hold 64 generic branch types. This also adds more
generic branch types.
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: 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>
---
include/uapi/linux/perf_event.h | 10 ++++++++--
tools/include/uapi/linux/perf_event.h | 10 ++++++++--
tools/perf/util/branch.c | 8 +++++++-
tools/perf/util/branch.h | 4 ++--
4 files changed, 25 insertions(+), 7 deletions(-)
diff --git a/include/uapi/linux/perf_event.h b/include/uapi/linux/perf_event.h
index b91d0f575d0c..361fdc6b87a0 100644
--- a/include/uapi/linux/perf_event.h
+++ b/include/uapi/linux/perf_event.h
@@ -256,6 +256,12 @@ enum {
PERF_BR_FIQ = 13, /* fiq */
PERF_BR_DEBUG_HALT = 14, /* debug halt */
PERF_BR_DEBUG_EXIT = 15, /* debug exit */
+ PERF_BR_DEBUG_INST = 16, /* instruciton debug */
+ PERF_BR_DEBUG_DATA = 17, /* data debug */
+ PERF_BR_FAULT_ALGN = 18, /* alignment fault */
+ PERF_BR_FAULT_DATA = 19, /* data fault */
+ PERF_BR_FAULT_INST = 20, /* instruction fault */
+ PERF_BR_SERROR = 21, /* system error */
PERF_BR_MAX,
};
@@ -1370,8 +1376,8 @@ struct perf_branch_entry {
in_tx:1, /* in transaction */
abort:1, /* transaction abort */
cycles:16, /* cycle count to last branch */
- type:4, /* branch type */
- reserved:40;
+ type:6, /* branch type */
+ reserved:38;
};
union perf_sample_weight {
diff --git a/tools/include/uapi/linux/perf_event.h b/tools/include/uapi/linux/perf_event.h
index 1882054e8684..9a82b8aaed93 100644
--- a/tools/include/uapi/linux/perf_event.h
+++ b/tools/include/uapi/linux/perf_event.h
@@ -256,6 +256,12 @@ enum {
PERF_BR_FIQ = 13, /* fiq */
PERF_BR_DEBUG_HALT = 14, /* debug halt */
PERF_BR_DEBUG_EXIT = 15, /* debug exit */
+ PERF_BR_DEBUG_INST = 16, /* instruciton debug */
+ PERF_BR_DEBUG_DATA = 17, /* data debug */
+ PERF_BR_FAULT_ALGN = 18, /* alignment fault */
+ PERF_BR_FAULT_DATA = 19, /* data fault */
+ PERF_BR_FAULT_INST = 20, /* instruction fault */
+ PERF_BR_SERROR = 21, /* system error */
PERF_BR_MAX,
};
@@ -1370,8 +1376,8 @@ struct perf_branch_entry {
in_tx:1, /* in transaction */
abort:1, /* transaction abort */
cycles:16, /* cycle count to last branch */
- type:4, /* branch type */
- reserved:40;
+ type:6, /* branch type */
+ reserved:38;
};
union perf_sample_weight {
diff --git a/tools/perf/util/branch.c b/tools/perf/util/branch.c
index 74e5e67b1779..1e216ea2e2a8 100644
--- a/tools/perf/util/branch.c
+++ b/tools/perf/util/branch.c
@@ -54,7 +54,13 @@ const char *branch_type_name(int type)
"IRQ",
"FIQ",
"DEBUG_HALT",
- "DEBUG_EXIT"
+ "DEBUG_EXIT",
+ "DEBUG_INST",
+ "DEBUG_DATA",
+ "FAULT_ALGN",
+ "FAULT_DATA",
+ "FAULT_INST",
+ "SERROR"
};
if (type >= 0 && type < PERF_BR_MAX)
diff --git a/tools/perf/util/branch.h b/tools/perf/util/branch.h
index 17b2ccc61094..875d99abdc36 100644
--- a/tools/perf/util/branch.h
+++ b/tools/perf/util/branch.h
@@ -23,8 +23,8 @@ struct branch_flags {
u64 in_tx:1;
u64 abort:1;
u64 cycles:16;
- u64 type:4;
- u64 reserved:40;
+ u64 type:6;
+ u64 reserved:38;
};
};
};
--
2.25.1
next prev parent reply other threads:[~2022-01-28 5:44 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-28 5:44 [PATCH 0/2] perf: Expand captured branch types Anshuman Khandual
2022-01-28 5:44 ` [PATCH 1/2] perf: Add more generic " Anshuman Khandual
2022-02-02 11:58 ` Mark Rutland
2022-02-04 4:56 ` Anshuman Khandual
2022-02-24 5:51 ` Anshuman Khandual
2022-02-24 7:10 ` Anshuman Khandual
2022-01-28 5:44 ` Anshuman Khandual [this message]
2022-02-02 11:57 ` [PATCH 2/2] perf: Expand perf_branch_entry.type Mark Rutland
2022-02-04 4:55 ` Anshuman Khandual
2022-02-04 16:02 ` Mark Rutland
2022-02-15 19:01 ` Rob Herring
2022-02-15 19:45 ` Mark Rutland
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=1643348653-24367-3-git-send-email-anshuman.khandual@arm.com \
--to=anshuman.khandual@arm.com \
--cc=acme@kernel.org \
--cc=alexander.shishkin@linux.intel.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=robh@kernel.org \
--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).