From: Michael Ellerman <patch-notifications@ellerman.id.au>
To: jolsa@kernel.org, Athira Rajeev <atrajeev@linux.vnet.ibm.com>,
acme@kernel.org, mpe@ellerman.id.au
Cc: maddy@linux.vnet.ibm.com, rnsastry@linux.ibm.com,
kjain@linux.ibm.com, linux-perf-users@vger.kernel.org,
disgoel@linux.vnet.ibm.com, linuxppc-dev@lists.ozlabs.org
Subject: Re: (subset) [PATCH V2 1/3] powerpc/perf: Fix branch_filter support for multiple filters in powerpc
Date: Wed, 05 Oct 2022 00:25:45 +1100 [thread overview]
Message-ID: <166488994565.779920.440863414238574866.b4-ty@ellerman.id.au> (raw)
In-Reply-To: <20220921145255.20972-1-atrajeev@linux.vnet.ibm.com>
On Wed, 21 Sep 2022 20:22:53 +0530, Athira Rajeev wrote:
> For PERF_SAMPLE_BRANCH_STACK sample type, different branch_sample_type
> ie branch filters are supported. The branch filters are requested via
> event attribute "branch_sample_type". Multiple branch filters can be
> passed in event attribute.
>
> Example:
> perf record -b -o- -B --branch-filter any,ind_call true
>
> [...]
Patch 3 applied to powerpc/next.
[3/3] tools/testing/selftests/powerpc: Update the bhrb filter sampling test to test for multiple branch filters
https://git.kernel.org/powerpc/c/18213532de7156af689cb0511d2f95bcbe3c98a0
cheers
prev parent reply other threads:[~2022-10-04 13:39 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-21 14:52 [PATCH V2 1/3] powerpc/perf: Fix branch_filter support for multiple filters in powerpc Athira Rajeev
2022-09-21 14:52 ` [PATCH V2 2/3] tools/perf/tests: Fix branch stack sampling test to include sanity check for branch filter Athira Rajeev
2022-09-28 14:27 ` Athira Rajeev
2022-09-28 14:29 ` Arnaldo Carvalho de Melo
2022-09-29 5:35 ` Michael Ellerman
2022-09-21 14:52 ` [PATCH V2 3/3] tools/testing/selftests/powerpc: Update the bhrb filter sampling test to test for multiple branch filters Athira Rajeev
2022-10-04 13:25 ` Michael Ellerman [this message]
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=166488994565.779920.440863414238574866.b4-ty@ellerman.id.au \
--to=patch-notifications@ellerman.id.au \
--cc=acme@kernel.org \
--cc=atrajeev@linux.vnet.ibm.com \
--cc=disgoel@linux.vnet.ibm.com \
--cc=jolsa@kernel.org \
--cc=kjain@linux.ibm.com \
--cc=linux-perf-users@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=maddy@linux.vnet.ibm.com \
--cc=mpe@ellerman.id.au \
--cc=rnsastry@linux.ibm.com \
/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).