linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Anshuman Khandual <khandual@linux.vnet.ibm.com>
To: linux-kernel@vger.kernel.org, linuxppc-dev@ozlabs.org
Cc: eranian@google.com, acme@redhat.com, ellerman@au1.ibm.com,
	sukadev@linux.vnet.ibm.com, michael.neuling@au1.ibm.com
Subject: [PATCH V2 2/6] powerpc, perf: Enable conditional branch filter for POWER8
Date: Fri, 30 Aug 2013 09:54:46 +0530	[thread overview]
Message-ID: <1377836690-32710-3-git-send-email-khandual@linux.vnet.ibm.com> (raw)
In-Reply-To: <1377836690-32710-1-git-send-email-khandual@linux.vnet.ibm.com>

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;
+
 	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;
 }
-- 
1.7.11.7

  parent reply	other threads:[~2013-08-30  4:25 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-08-30  4:24 [PATCH V2 0/6] perf: New conditional branch filter Anshuman Khandual
2013-08-30  4:24 ` [PATCH V2 1/6] perf: New conditional branch filter criteria in branch stack sampling Anshuman Khandual
2013-08-30  4:24 ` Anshuman Khandual [this message]
2013-08-30  4:24 ` [PATCH V2 3/6] perf, tool: Conditional branch filter 'cond' added to perf record Anshuman Khandual
2013-08-30  4:24 ` [PATCH V2 4/6] x86, perf: Add conditional branch filtering support Anshuman Khandual
2013-08-30  4:24 ` [PATCH V2 5/6] perf, documentation: Description for conditional branch filter Anshuman Khandual
2013-08-30  4:24 ` [PATCH V2 6/6] powerpc, perf: Enable SW filtering in branch stack sampling framework Anshuman Khandual
2013-08-30 11:48 ` [PATCH V2 0/6] perf: New conditional branch filter Stephane Eranian
2013-09-02  3:37   ` Anshuman Khandual
2013-09-21  6:41   ` Anshuman Khandual
2013-09-21  6:45     ` Anshuman Khandual
2013-09-10  2:06 ` Michael Ellerman
2013-09-10  3:52   ` Anshuman Khandual
2013-09-21  6:55   ` Stephane Eranian
2013-09-23  9:15     ` Anshuman Khandual
2013-09-25  2:19       ` Michael Ellerman
2013-09-25  6:15         ` Anshuman Khandual
2013-09-26 11:14       ` Stephane Eranian
2013-10-10  5:04         ` 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=1377836690-32710-3-git-send-email-khandual@linux.vnet.ibm.com \
    --to=khandual@linux.vnet.ibm.com \
    --cc=acme@redhat.com \
    --cc=ellerman@au1.ibm.com \
    --cc=eranian@google.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linuxppc-dev@ozlabs.org \
    --cc=michael.neuling@au1.ibm.com \
    --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).