From: michael@ozlabs.org (mpe@ellerman.id.au)
To: linuxppc-dev@ozlabs.org, linux-kernel@vger.kernel.org
Cc: mikey@neuling.org, sukadev@linux.vnet.ibm.com,
eranian@google.com, michaele@au1.ibm.com
Subject: RE: [V3 02/10] powerpc, perf: Enable conditional branch filter for POWER8
Date: Tue, 26 Nov 2013 17:06:19 +1100 (EST) [thread overview]
Message-ID: <20131126060619.48B5D2C00BC@ozlabs.org> (raw)
In-Reply-To: <1381906617-11392-3-git-send-email-khandual@linux.vnet.ibm.com>
On Wed, 2013-16-10 at 06:56:49 UTC, Anshuman Khandual wrote:
> Enables conditional branch filter support for POWER8
> utilizing MMCRA register based filter and also invalidates
> a BHRB branch filter combination involving conditional
> branches.
>
> Signed-off-by: Anshuman Khandual <khandual@linux.vnet.ibm.com>
> ---
> arch/powerpc/perf/power8-pmu.c | 10 ++++++++++
> 1 file changed, 10 insertions(+)
>
> diff --git a/arch/powerpc/perf/power8-pmu.c b/arch/powerpc/perf/power8-pmu.c
> index 2ee4a70..6e28587 100644
> --- a/arch/powerpc/perf/power8-pmu.c
> +++ b/arch/powerpc/perf/power8-pmu.c
> @@ -580,11 +580,21 @@ static u64 power8_bhrb_filter_map(u64 branch_sample_type)
> if (branch_sample_type & PERF_SAMPLE_BRANCH_IND_CALL)
> return -1;
>
> + /* Invalid branch filter combination - HW does not support */
> + if ((branch_sample_type & PERF_SAMPLE_BRANCH_ANY_CALL) &&
> + (branch_sample_type & PERF_SAMPLE_BRANCH_COND))
> + return -1;
What this doesn't make obvious is that the hardware doesn't support any
combinations. It just happens that these are the only two possibilities we
allow, and so this is the only combination we have to disallow.
>
> if (branch_sample_type & PERF_SAMPLE_BRANCH_ANY_CALL) {
> pmu_bhrb_filter |= POWER8_MMCRA_IFM1;
> return pmu_bhrb_filter;
> }
>
> + if (branch_sample_type & PERF_SAMPLE_BRANCH_COND) {
> + pmu_bhrb_filter |= POWER8_MMCRA_IFM3;
> + return pmu_bhrb_filter;
> + }
> +
> /* Every thing else is unsupported */
> return -1;
> }
I think it would be clearer if we actually checked for the possibilities we
allow and let everything else fall through, eg:
/* Ignore user/kernel/hv bits */
branch_sample_type &= ~PERF_SAMPLE_BRANCH_PLM_ALL;
if (branch_sample_type == PERF_SAMPLE_BRANCH_ANY)
return 0;
if (branch_sample_type == PERF_SAMPLE_BRANCH_ANY_CALL)
return POWER8_MMCRA_IFM1;
if (branch_sample_type == PERF_SAMPLE_BRANCH_COND)
return POWER8_MMCRA_IFM3;
return -1;
cheers
next prev parent reply other threads:[~2013-11-26 6:06 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-16 6:56 [V3 00/10] perf: New conditional branch filter Anshuman Khandual
2013-10-16 6:56 ` [V3 01/10] perf: New conditional branch filter criteria in branch stack sampling Anshuman Khandual
2013-11-26 6:06 ` mpe@ellerman.id.au
2013-11-26 10:15 ` Anshuman Khandual
2013-12-03 10:21 ` Anshuman Khandual
2013-10-16 6:56 ` [V3 02/10] powerpc, perf: Enable conditional branch filter for POWER8 Anshuman Khandual
2013-11-26 6:06 ` mpe@ellerman.id.au [this message]
2013-11-26 10:40 ` Anshuman Khandual
2013-10-16 6:56 ` [V3 03/10] perf, tool: Conditional branch filter 'cond' added to perf record Anshuman Khandual
2013-10-16 6:56 ` [V3 04/10] x86, perf: Add conditional branch filtering support Anshuman Khandual
2013-10-16 6:56 ` [V3 05/10] perf, documentation: Description for conditional branch filter Anshuman Khandual
2013-10-16 6:56 ` [V3 06/10] powerpc, perf: Change the name of HW PMU branch filter tracking variable Anshuman Khandual
2013-10-16 6:56 ` [V3 07/10] powerpc, lib: Add new branch instruction analysis support functions Anshuman Khandual
2013-10-16 6:56 ` [V3 08/10] powerpc, perf: Enable SW filtering in branch stack sampling framework Anshuman Khandual
2013-10-16 6:56 ` [V3 09/10] power8, perf: Change BHRB branch filter configuration Anshuman Khandual
2013-10-16 6:56 ` [V3 10/10] powerpc, perf: Cleanup SW branch filter list look up Anshuman Khandual
2013-12-04 2:50 ` [V3 00/10] perf: New conditional branch filter Michael Ellerman
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=20131126060619.48B5D2C00BC@ozlabs.org \
--to=michael@ozlabs.org \
--cc=eranian@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=michaele@au1.ibm.com \
--cc=mikey@neuling.org \
--cc=sukadev@linux.vnet.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).