From: James Clark <james.clark@arm.com>
To: Anshuman Khandual <anshuman.khandual@arm.com>,
linux-kernel@vger.kernel.org, linux-perf-users@vger.kernel.org,
peterz@infradead.org, acme@kernel.org
Cc: Robin Murphy <robin.murphy@arm.com>,
Suzuki Poulose <suzuki.poulose@arm.com>,
Ingo Molnar <mingo@redhat.com>,
Mark Rutland <mark.rutland@arm.com>,
Alexander Shishkin <alexander.shishkin@linux.intel.com>,
Jiri Olsa <jolsa@redhat.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 V5 1/8] perf: Add system error and not in transaction branch types
Date: Tue, 19 Apr 2022 14:55:42 +0100 [thread overview]
Message-ID: <d934c6a2-ecc3-48cb-a65f-99f7789af7bc@arm.com> (raw)
In-Reply-To: <20220404045046.634522-2-anshuman.khandual@arm.com>
On 04/04/2022 05:50, Anshuman Khandual wrote:
> This expands generic branch type classification by adding two more entries
> there in i.e system error and not in transaction. This also updates the x86
> implementation to process X86_BR_NO_TX records as appropriate. This changes
> branch types reported to user space on x86 platform but it should not be a
> problem. The possible scenarios and impacts are enumerated here.
>
> --------------------------------------------------------------------------
> | kernel | perf tool | Impact |
> --------------------------------------------------------------------------
> | old | old | Works as before |
> --------------------------------------------------------------------------
> | old | new | PERF_BR_UNKNOWN is processed |
> --------------------------------------------------------------------------
> | new | old | PERF_BR_NO_TX are blocked via old PERF_BR_MAX |
> --------------------------------------------------------------------------
> | new | new | NO_TX are recognized |
> --------------------------------------------------------------------------
>
> When PERF_BR_NO_TX is blocked via old PERF_BR_MAX (new kernel with old perf
> tool) the user space might throw up an warning complaining about an
> unrecognized branch types being reported, but it's expected. PERF_BR_SERROR
> & PERF_BR_NO_TX branch types will be used for BRBE implementation on arm64
> platform.
>
> PERF_BR_NO_TX complements 'abort' and 'in_tx' elements in perf_branch_entry
> which represent other transaction states for a given branch record. Because
> this completes the transaction state classification.
>
> 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>
Reviewed-by: James Clark <james.clark@arm.com>
> ---
> arch/x86/events/intel/lbr.c | 2 +-
> include/uapi/linux/perf_event.h | 2 ++
> 2 files changed, 3 insertions(+), 1 deletion(-)
>
> diff --git a/arch/x86/events/intel/lbr.c b/arch/x86/events/intel/lbr.c
> index fe1742c4ca49..30dcd18936d5 100644
> --- a/arch/x86/events/intel/lbr.c
> +++ b/arch/x86/events/intel/lbr.c
> @@ -1336,7 +1336,7 @@ static int branch_map[X86_BR_TYPE_MAP_MAX] = {
> PERF_BR_IND_CALL, /* X86_BR_IND_CALL */
> PERF_BR_UNKNOWN, /* X86_BR_ABORT */
> PERF_BR_UNKNOWN, /* X86_BR_IN_TX */
> - PERF_BR_UNKNOWN, /* X86_BR_NO_TX */
> + PERF_BR_NO_TX, /* X86_BR_NO_TX */
> PERF_BR_CALL, /* X86_BR_ZERO_CALL */
> PERF_BR_UNKNOWN, /* X86_BR_CALL_STACK */
> PERF_BR_IND, /* X86_BR_IND_JMP */
> diff --git a/include/uapi/linux/perf_event.h b/include/uapi/linux/perf_event.h
> index d37629dbad72..26d8f0b5ac0d 100644
> --- a/include/uapi/linux/perf_event.h
> +++ b/include/uapi/linux/perf_event.h
> @@ -253,6 +253,8 @@ enum {
> PERF_BR_COND_RET = 10, /* conditional function return */
> PERF_BR_ERET = 11, /* exception return */
> PERF_BR_IRQ = 12, /* irq */
> + PERF_BR_SERROR = 13, /* system error */
> + PERF_BR_NO_TX = 14, /* not in transaction */
> PERF_BR_MAX,
> };
>
next prev parent reply other threads:[~2022-04-19 13:57 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-04 4:50 [PATCH V5 0/8] perf: Expand perf_branch_entry Anshuman Khandual
2022-04-04 4:50 ` [PATCH V5 1/8] perf: Add system error and not in transaction branch types Anshuman Khandual
2022-04-19 13:55 ` James Clark [this message]
2022-04-04 4:50 ` [PATCH V5 2/8] perf: Extend branch type classification Anshuman Khandual
2022-04-19 13:56 ` James Clark
2022-04-04 4:50 ` [PATCH V5 3/8] perf: Capture branch privilege information Anshuman Khandual
2022-04-04 4:50 ` [PATCH V5 4/8] perf: Add PERF_BR_NEW_ARCH_[N] map for BRBE on arm64 platform Anshuman Khandual
2022-04-19 13:57 ` James Clark
2022-04-04 4:50 ` [PATCH V5 5/8] perf/tools: Add system error and not in transaction branch types Anshuman Khandual
2022-04-19 13:58 ` James Clark
2022-04-04 4:50 ` [PATCH V5 6/8] perf/tools: Extend branch type classification Anshuman Khandual
2022-04-19 14:01 ` James Clark
2022-04-04 4:50 ` [PATCH V5 7/8] perf/tools: Add branch privilege information request flag Anshuman Khandual
2022-04-04 4:50 ` [PATCH V5 8/8] perf/tools: Add PERF_BR_NEW_ARCH_[N] map for BRBE on arm64 platform Anshuman Khandual
2022-04-11 5:46 ` [PATCH V5 0/8] perf: Expand perf_branch_entry Anshuman Khandual
2022-04-18 6:47 ` Anshuman Khandual
2022-04-28 13:45 ` Arnaldo Carvalho de Melo
2022-05-11 3:49 ` Anshuman Khandual
2022-05-11 4:28 ` 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=d934c6a2-ecc3-48cb-a65f-99f7789af7bc@arm.com \
--to=james.clark@arm.com \
--cc=acme@kernel.org \
--cc=alexander.shishkin@linux.intel.com \
--cc=anshuman.khandual@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