From: "Liang, Kan" <kan.liang@linux.intel.com>
To: Peter Zijlstra <peterz@infradead.org>
Cc: mingo@redhat.com, linux-kernel@vger.kernel.org,
tglx@linutronix.de, acme@kernel.org, jolsa@kernel.org,
eranian@google.com, alexander.shishkin@linux.intel.com,
ak@linux.intel.com
Subject: Re: [PATCH 1/2] perf/x86/intel: Support adaptive PEBS for fixed counters
Date: Wed, 10 Apr 2019 09:57:50 -0400 [thread overview]
Message-ID: <d23c9f80-b73e-693a-f4ab-507e4108c46b@linux.intel.com> (raw)
In-Reply-To: <20190410074139.GW11158@hirez.programming.kicks-ass.net>
On 4/10/2019 3:41 AM, Peter Zijlstra wrote:
> On Tue, Apr 09, 2019 at 06:09:59PM -0700, kan.liang@linux.intel.com wrote:
>> From: Kan Liang <kan.liang@linux.intel.com>
>>
>> Fixed counters can also generate adaptive PEBS record, if the
>> corresponding bit in IA32_FIXED_CTR_CTRL is set.
>> Otherwise, only basic record is generated.
>>
>> Unconditionally set the bit when PEBS is enabled on fixed counters.
>> Let MSR_PEBS_CFG decide which format of PEBS record should be generated.
>> There is no harmful to leave the bit set.
>
> I'll merge this back into:
>
> Subject: perf/x86/intel: Support adaptive PEBSv4
>
> such that this bug never existed, ok?
Yes, please.
Thanks,
Kan
>
>>
>> Signed-off-by: Kan Liang <kan.liang@linux.intel.com>
>> ---
>> arch/x86/events/intel/core.c | 5 +++++
>> arch/x86/include/asm/perf_event.h | 1 +
>> 2 files changed, 6 insertions(+)
>>
>> diff --git a/arch/x86/events/intel/core.c b/arch/x86/events/intel/core.c
>> index 56df0f6..f34d92b 100644
>> --- a/arch/x86/events/intel/core.c
>> +++ b/arch/x86/events/intel/core.c
>> @@ -2174,6 +2174,11 @@ static void intel_pmu_enable_fixed(struct perf_event *event)
>> bits <<= (idx * 4);
>> mask = 0xfULL << (idx * 4);
>>
>> + if (x86_pmu.intel_cap.pebs_baseline && event->attr.precise_ip) {
>> + bits |= ICL_FIXED_0_ADAPTIVE << (idx * 4);
>> + mask |= ICL_FIXED_0_ADAPTIVE << (idx * 4);
>> + }
>> +
>> rdmsrl(hwc->config_base, ctrl_val);
>> ctrl_val &= ~mask;
>> ctrl_val |= bits;
>> diff --git a/arch/x86/include/asm/perf_event.h b/arch/x86/include/asm/perf_event.h
>> index dcb8bac..ce0dc88 100644
>> --- a/arch/x86/include/asm/perf_event.h
>> +++ b/arch/x86/include/asm/perf_event.h
>> @@ -33,6 +33,7 @@
>> #define HSW_IN_TX (1ULL << 32)
>> #define HSW_IN_TX_CHECKPOINTED (1ULL << 33)
>> #define ICL_EVENTSEL_ADAPTIVE (1ULL << 34)
>> +#define ICL_FIXED_0_ADAPTIVE (1ULL << 32)
>>
>> #define AMD64_EVENTSEL_INT_CORE_ENABLE (1ULL << 36)
>> #define AMD64_EVENTSEL_GUESTONLY (1ULL << 40)
>> --
>> 2.7.4
>>
next prev parent reply other threads:[~2019-04-10 13:57 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-10 1:09 [PATCH 0/2] perf: Add Tremont support kan.liang
2019-04-10 1:09 ` [PATCH 1/2] perf/x86/intel: Support adaptive PEBS for fixed counters kan.liang
2019-04-10 7:41 ` Peter Zijlstra
2019-04-10 13:57 ` Liang, Kan [this message]
2019-04-10 1:10 ` [PATCH 2/2] perf/x86/intel: Add Tremont core PMU support kan.liang
2019-04-10 7:51 ` Peter Zijlstra
2019-04-10 13:58 ` Liang, Kan
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=d23c9f80-b73e-693a-f4ab-507e4108c46b@linux.intel.com \
--to=kan.liang@linux.intel.com \
--cc=acme@kernel.org \
--cc=ak@linux.intel.com \
--cc=alexander.shishkin@linux.intel.com \
--cc=eranian@google.com \
--cc=jolsa@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=tglx@linutronix.de \
/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
all inboxes | Powered by JetHome®