mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
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 4/8] perf: Add PERF_BR_NEW_ARCH_[N] map for BRBE on arm64 platform
Date: Tue, 19 Apr 2022 14:57:14 +0100	[thread overview]
Message-ID: <35dfe8a7-c31a-3e28-7429-f81753d0089a@arm.com> (raw)
In-Reply-To: <20220404045046.634522-5-anshuman.khandual@arm.com>



On 04/04/2022 05:50, Anshuman Khandual wrote:
> BRBE captured branch types will overflow perf_branch_entry.type and generic
> branch types in perf_branch_entry.new_type. So override each available arch
> specific branch type in the following manner to comprehensively process all
> reported branch types in BRBE.
> 
> PERF_BR_ARM64_FIQ            PERF_BR_NEW_ARCH_1
> PERF_BR_ARM64_DEBUG_HALT     PERF_BR_NEW_ARCH_2
> PERF_BR_ARM64_DEBUG_EXIT     PERF_BR_NEW_ARCH_3
> PERF_BR_ARM64_DEBUG_INST     PERF_BR_NEW_ARCH_4
> PERF_BR_ARM64_DEBUG_DATA     PERF_BR_NEW_ARCH_5
> 
> Signed-off-by: Anshuman Khandual <anshuman.khandual@arm.com>

Reviewed-by: James Clark <james.clark@arm.com>

> ---
>  include/uapi/linux/perf_event.h | 6 ++++++
>  1 file changed, 6 insertions(+)
> 
> diff --git a/include/uapi/linux/perf_event.h b/include/uapi/linux/perf_event.h
> index 193dba2ecdc1..4cf1c8e22cab 100644
> --- a/include/uapi/linux/perf_event.h
> +++ b/include/uapi/linux/perf_event.h
> @@ -282,6 +282,12 @@ enum {
>  	PERF_BR_PRIV_HV		= 3,
>  };
>  
> +#define PERF_BR_ARM64_FIQ		PERF_BR_NEW_ARCH_1
> +#define PERF_BR_ARM64_DEBUG_HALT	PERF_BR_NEW_ARCH_2
> +#define PERF_BR_ARM64_DEBUG_EXIT	PERF_BR_NEW_ARCH_3
> +#define PERF_BR_ARM64_DEBUG_INST	PERF_BR_NEW_ARCH_4
> +#define PERF_BR_ARM64_DEBUG_DATA	PERF_BR_NEW_ARCH_5
> +
>  #define PERF_SAMPLE_BRANCH_PLM_ALL \
>  	(PERF_SAMPLE_BRANCH_USER|\
>  	 PERF_SAMPLE_BRANCH_KERNEL|\

  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
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 [this message]
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=35dfe8a7-c31a-3e28-7429-f81753d0089a@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

all inboxes | Powered by JetHome®