From: Anshuman Khandual <khandual@linux.vnet.ibm.com>
To: Michael Ellerman <mpe@ellerman.id.au>
Cc: mikey@neuling.org, ak@linux.intel.com,
linux-kernel@vger.kernel.org, eranian@google.com,
linuxppc-dev@ozlabs.org, acme@ghostprotocols.net,
sukadev@linux.vnet.ibm.com, mingo@kernel.org
Subject: Re: [PATCH V4 09/10] power8, perf: Change BHRB branch filter configuration
Date: Wed, 18 Dec 2013 09:25:36 +0530 [thread overview]
Message-ID: <52B11CB8.6070609@linux.vnet.ibm.com> (raw)
In-Reply-To: <1387325285.19507.1.camel@concordia>
On 12/18/2013 05:38 AM, Michael Ellerman wrote:
> On Fri, 2013-12-13 at 13:50 +0530, Anshuman Khandual wrote:
>> On 12/09/2013 11:51 AM, Michael Ellerman wrote:
>>>
>>> As I said in my comments on version 3 which you ignored:
>>>
>>> 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;
>>>
>>
>> Hey Michael,
>>
>> This patch only adds support for the PERF_SAMPLE_BRANCH_COND filter, if the
>> over all code flow does not clearly suggest that all combinations of any of
>> these HW filters are invalid, then we can go with one more patch to clean
>> that up before or after this patch but not here in this patch. Finally the
>> code section here will look something like this. Does it sound good ?
>
> Better, but not quite.
>
>> static u64 power8_bhrb_filter_map(u64 branch_sample_type)
>> {
>> u64 pmu_bhrb_filter = 0;
>>
>> /* BHRB and regular PMU events share the same privilege state
>> * filter configuration. BHRB is always recorded along with a
>> * regular PMU event. As the privilege state filter is handled
>> * in the basic PMC configuration of the accompanying regular
>> * PMU event, we ignore any separate BHRB specific request.
>> */
>>
>> /* Ignore user, kernel, hv bits */
>> branch_sample_type &= ~PERF_SAMPLE_BRANCH_PLM_ALL;
>>
>> if (branch_sample_type == PERF_SAMPLE_BRANCH_ANY)
>> return pmu_bhrb_filter;
>
> return 0;
>
>>
>>
>> if (branch_sample_type == PERF_SAMPLE_BRANCH_ANY_CALL) {
>> pmu_bhrb_filter |= POWER8_MMCRA_IFM1;
>> return pmu_bhrb_filter;
>
> return POWER8_MMCRA_IFM1;
>
>> }
>>
>> if (branch_sample_type == PERF_SAMPLE_BRANCH_COND) {
>> pmu_bhrb_filter |= POWER8_MMCRA_IFM3;
>> return pmu_bhrb_filter;
>
> return POWER8_MMCRA_IFM3;
>
>> }
>>
>> /* Every thing else is unsupported */
>> return -1;
>> }
>
Okay, will take these changes into another patch before adding conditional branch
filter here.
next prev parent reply other threads:[~2013-12-18 3:56 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-04 10:32 [PATCH V4 00/10] perf: New conditional branch filter Anshuman Khandual
2013-12-04 10:32 ` [PATCH V4 01/10] perf: Add PERF_SAMPLE_BRANCH_COND Anshuman Khandual
2013-12-04 10:32 ` [PATCH V4 02/10] powerpc, perf: Enable conditional branch filter for POWER8 Anshuman Khandual
2013-12-04 10:32 ` [PATCH V4 03/10] perf, tool: Conditional branch filter 'cond' added to perf record Anshuman Khandual
2013-12-04 10:32 ` [PATCH V4 04/10] x86, perf: Add conditional branch filtering support Anshuman Khandual
2013-12-06 16:46 ` Andi Kleen
2013-12-04 10:32 ` [PATCH V4 05/10] perf, documentation: Description for conditional branch filter Anshuman Khandual
2013-12-04 10:32 ` [PATCH V4 06/10] powerpc, perf: Change the name of HW PMU branch filter tracking variable Anshuman Khandual
2013-12-04 10:32 ` [PATCH V4 07/10] powerpc, lib: Add new branch instruction analysis support functions Anshuman Khandual
2013-12-09 6:21 ` Michael Ellerman
2013-12-10 6:09 ` Anshuman Khandual
2013-12-20 10:06 ` Anshuman Khandual
2013-12-04 10:32 ` [PATCH V4 08/10] powerpc, perf: Enable SW filtering in branch stack sampling framework Anshuman Khandual
2013-12-09 6:21 ` Michael Ellerman
2013-12-10 5:57 ` Anshuman Khandual
2013-12-12 8:45 ` Anshuman Khandual
2013-12-13 2:47 ` Michael Ellerman
2013-12-20 11:01 ` Anshuman Khandual
2013-12-24 3:29 ` Michael Ellerman
2013-12-24 3:50 ` Anshuman Khandual
2013-12-24 4:35 ` Michael Ellerman
2013-12-04 10:32 ` [PATCH V4 09/10] power8, perf: Change BHRB branch filter configuration Anshuman Khandual
2013-12-09 6:21 ` Michael Ellerman
2013-12-13 8:20 ` Anshuman Khandual
2013-12-18 0:08 ` Michael Ellerman
2013-12-18 3:55 ` Anshuman Khandual [this message]
2013-12-04 10:32 ` [PATCH V4 10/10] powerpc, perf: Cleanup SW branch filter list look up Anshuman Khandual
2013-12-09 6:21 ` Michael Ellerman
2013-12-20 11:06 ` Anshuman Khandual
2013-12-05 4:47 ` [PATCH V4 00/10] perf: New conditional branch filter Michael Ellerman
2013-12-06 13:18 ` Arnaldo Carvalho de Melo
2013-12-09 0:41 ` 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=52B11CB8.6070609@linux.vnet.ibm.com \
--to=khandual@linux.vnet.ibm.com \
--cc=acme@ghostprotocols.net \
--cc=ak@linux.intel.com \
--cc=eranian@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=mikey@neuling.org \
--cc=mingo@kernel.org \
--cc=mpe@ellerman.id.au \
--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).