From: Anshuman Khandual <khandual@linux.vnet.ibm.com>
To: linuxppc-dev@lists.ozlabs.org
Subject: [PATCH V11_RESEND 03/10] powerpc/perf: Restore privilege level filter support for BHRB
Date: Tue, 16 Feb 2016 12:07:03 +0530 [thread overview]
Message-ID: <1455604630-16214-4-git-send-email-khandual@linux.vnet.ibm.com> (raw)
In-Reply-To: <1455604630-16214-1-git-send-email-khandual@linux.vnet.ibm.com>
'commit 9de5cb0f6df8 ("powerpc/perf: Add per-event excludes on Power8")'
broke the PMU based BHRB privilege level filter. BHRB depends on the
same MMCR0 bits for privilege level filter which was used to freeze all
the PMCs as a group. Once we moved to individual event based privilege
filters through MMCR2 register on POWER8, event associated privilege
filters are no longer applicable to the BHRB captured branches.
This patch solves the problem by restoring to the previous method of
privilege level filters for the event in case BHRB based branch stack
sampling is requested. This patch also changes 'check_excludes' for
the same reason.
Signed-off-by: Anshuman Khandual <khandual@linux.vnet.ibm.com>
---
arch/powerpc/perf/core-book3s.c | 20 +++++++++++---------
1 file changed, 11 insertions(+), 9 deletions(-)
diff --git a/arch/powerpc/perf/core-book3s.c b/arch/powerpc/perf/core-book3s.c
index a158923..0930a07 100644
--- a/arch/powerpc/perf/core-book3s.c
+++ b/arch/powerpc/perf/core-book3s.c
@@ -941,7 +941,7 @@ static int power_check_constraints(struct cpu_hw_events *cpuhw,
* added events.
*/
static int check_excludes(struct perf_event **ctrs, unsigned int cflags[],
- int n_prev, int n_new)
+ int n_prev, int n_new, unsigned int bhrb_users)
{
int eu = 0, ek = 0, eh = 0;
int i, n, first;
@@ -950,9 +950,10 @@ static int check_excludes(struct perf_event **ctrs, unsigned int cflags[],
/*
* If the PMU we're on supports per event exclude settings then we
* don't need to do any of this logic. NB. This assumes no PMU has both
- * per event exclude and limited PMCs.
+ * per event exclude and limited PMCs. But again if the event has also
+ * requested for branch stack sampling, then process the logic here.
*/
- if (ppmu->flags & PPMU_ARCH_207S)
+ if ((ppmu->flags & PPMU_ARCH_207S) && !bhrb_users)
return 0;
n = n_prev + n_new;
@@ -1270,7 +1271,7 @@ static void power_pmu_enable(struct pmu *pmu)
goto out;
}
- if (!(ppmu->flags & PPMU_ARCH_207S)) {
+ if (!(ppmu->flags & PPMU_ARCH_207S) || cpuhw->bhrb_users) {
/*
* Add in MMCR0 freeze bits corresponding to the attr.exclude_*
* bits for the first event. We have already checked that all
@@ -1295,7 +1296,7 @@ static void power_pmu_enable(struct pmu *pmu)
mtspr(SPRN_MMCR1, cpuhw->mmcr[1]);
mtspr(SPRN_MMCR0, (cpuhw->mmcr[0] & ~(MMCR0_PMC1CE | MMCR0_PMCjCE))
| MMCR0_FC);
- if (ppmu->flags & PPMU_ARCH_207S)
+ if ((ppmu->flags & PPMU_ARCH_207S) && !cpuhw->bhrb_users)
mtspr(SPRN_MMCR2, cpuhw->mmcr[3]);
/*
@@ -1447,7 +1448,8 @@ static int power_pmu_add(struct perf_event *event, int ef_flags)
if (cpuhw->txn_flags & PERF_PMU_TXN_ADD)
goto nocheck;
- if (check_excludes(cpuhw->event, cpuhw->flags, n0, 1))
+ if (check_excludes(cpuhw->event, cpuhw->flags,
+ n0, 1, cpuhw->bhrb_users))
goto out;
if (power_check_constraints(cpuhw, cpuhw->events, cpuhw->flags, n0 + 1))
goto out;
@@ -1650,7 +1652,7 @@ static int power_pmu_commit_txn(struct pmu *pmu)
}
n = cpuhw->n_events;
- if (check_excludes(cpuhw->event, cpuhw->flags, 0, n))
+ if (check_excludes(cpuhw->event, cpuhw->flags, 0, n, cpuhw->bhrb_users))
return -EAGAIN;
i = power_check_constraints(cpuhw, cpuhw->events, cpuhw->flags, n);
if (i < 0)
@@ -1863,10 +1865,10 @@ static int power_pmu_event_init(struct perf_event *event)
events[n] = ev;
ctrs[n] = event;
cflags[n] = flags;
- if (check_excludes(ctrs, cflags, n, 1))
+ cpuhw = &get_cpu_var(cpu_hw_events);
+ if (check_excludes(ctrs, cflags, n, 1, cpuhw->bhrb_users))
return -EINVAL;
- cpuhw = &get_cpu_var(cpu_hw_events);
err = power_check_constraints(cpuhw, events, cflags, n + 1);
if (has_branch_stack(event)) {
--
2.1.0
next prev parent reply other threads:[~2016-02-16 6:37 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-16 6:37 [PATCH V11_RESEND 00/10] powerpc/perf: Enable SW branch filters Anshuman Khandual
2016-02-16 6:37 ` [PATCH V11_RESEND 01/10] powerpc/perf: Change name & type of 'pred' in power_pmu_bhrb_read Anshuman Khandual
2016-02-16 6:37 ` [PATCH V11_RESEND 02/10] powerpc/perf: Re organize PMU branch filter processing on POWER8 Anshuman Khandual
2016-02-16 6:37 ` Anshuman Khandual [this message]
2016-02-16 6:37 ` [PATCH V11_RESEND 04/10] powerpc/perf: Re organize BHRB processing Anshuman Khandual
2016-02-16 6:37 ` [PATCH V11_RESEND 05/10] powerpc/perf: Change the name of HW PMU branch filter tracking variable Anshuman Khandual
2016-02-16 6:37 ` [PATCH V11_RESEND 06/10] powerpc/lib: Add new branch analysis support functions Anshuman Khandual
2016-02-16 6:37 ` [PATCH V11_RESEND 07/10] powerpc/perf: Enable SW filtering in branch stack sampling framework Anshuman Khandual
2016-02-16 6:37 ` [PATCH V11_RESEND 08/10] powerpc/perf: Change POWER8 PMU configuration to work with SW filters Anshuman Khandual
2016-02-16 6:37 ` [PATCH V11_RESEND 09/10] powerpc/perf: Enable privilege mode SW branch filters Anshuman Khandual
2016-02-16 6:37 ` [PATCH V11_RESEND 10/10] selftests/powerpc: Add test for BHRB branch filters (HW & SW) Anshuman Khandual
2016-02-16 13:08 ` [PATCH V11_RESEND 00/10] powerpc/perf: Enable SW branch filters Christophe Leroy
2016-02-17 3:49 ` Anshuman Khandual
2016-02-17 4:23 ` 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=1455604630-16214-4-git-send-email-khandual@linux.vnet.ibm.com \
--to=khandual@linux.vnet.ibm.com \
--cc=linuxppc-dev@lists.ozlabs.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;
as well as URLs for NNTP newsgroup(s).