public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Anshuman Khandual <anshuman.khandual@arm.com>
To: 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>,
	James Clark <james.clark@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 0/8] perf: Expand perf_branch_entry
Date: Mon, 11 Apr 2022 11:16:02 +0530	[thread overview]
Message-ID: <f469f253-9ccc-d55b-731d-3ecc8d685104@arm.com> (raw)
In-Reply-To: <20220404045046.634522-1-anshuman.khandual@arm.com>



On 4/4/22 10:20, Anshuman Khandual wrote:
> Branch Record Buffer Extension (BRBE) implementation on arm64 captures more
> branch type classification which cannot be accommodated in the current perf
> branch record format via perf_branch_entry.type element (4 bit field). Also
> it captures privilege information which does not have a corresponding slot
> in perf_branch_entry. This series expands struct perf_branch_entry, to meet
> both these requirements without breaking the existing user space ABI for
> perf tools.
> 
> All architecture specific branch types added via perf_branch_entry.new_type
> field in [PATCH 3/4] will be used in BRBE implementation on arm64 platform
> later on with the following map.
> 
> #ifdef CONFIG_ARM64
> #define PERF_BR_FIQ		PERF_BR_NEW_ARCH_1
> #define PERF_BR_DEBUG_HALT	PERF_BR_NEW_ARCH_2
> #define PERF_BR_DEBUG_EXIT	PERF_BR_NEW_ARCH_3
> #define PERF_BR_DEBUG_INST	PERF_BR_NEW_ARCH_4
> #define PERF_BR_DEBUG_DATA	PERF_BR_NEW_ARCH_5
> #endif
> 
> This actually combines following patches and series into a single series.
> 
> - https://lore.kernel.org/all/1642998653-21377-12-git-send-email-anshuman.khandual@arm.com/
> - https://lore.kernel.org/all/1643348653-24367-1-git-send-email-anshuman.khandual@arm.com/
> - https://lore.kernel.org/all/1645681014-3346-1-git-send-email-anshuman.khandual@arm.com/
> 
> This series applies on v5.18-rc1
> 
> perf API
> 
> The series being applied
> 
> - Clean : tools/perf/check-headers.sh
> - Clean : diff -u tools/include/uapi/linux/perf_event.h include/uapi/linux/perf_event.h
> 
> Todo
> 
> - Update perf report tool to process PERF_BR_EXTEND_ABI (when available),
>   then fetch and report branch types from perf_branch_entry.new_type field.
> 
> References
> 
> - BRBE captured branch record information
> 
> https://developer.arm.com/documentation/ddi0601/2021-12/AArch64-Registers/BRBINF-n--EL1--Branch-Record-Buffer-Information-Register--n-?lang=en
> 
> - BRBE based perf branch stack implementation on arm64 platform
> 
> https://lore.kernel.org/all/1642998653-21377-1-git-send-email-anshuman.khandual@arm.com/
> 
> Changes in V5:
> 
> - Dropped patches [PATCH 1/10] and [PATCH 6/10] related to PERF_BR_[RET|IRQ] - merged
>   via the commit cedd3614e5d9c809 ("perf: Add irq and exception return branch types")
> 
> - Rebased series on v5.18-rc1

Gentle ping, any updates on this series ?

  parent reply	other threads:[~2022-04-11  5:45 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
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 ` Anshuman Khandual [this message]
2022-04-18  6:47   ` [PATCH V5 0/8] perf: Expand perf_branch_entry 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=f469f253-9ccc-d55b-731d-3ecc8d685104@arm.com \
    --to=anshuman.khandual@arm.com \
    --cc=acme@kernel.org \
    --cc=alexander.shishkin@linux.intel.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