public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Liang, Kan" <kan.liang@linux.intel.com>
To: Peter Zijlstra <peterz@infradead.org>
Cc: tglx@linutronix.de, mingo@redhat.com,
	linux-kernel@vger.kernel.org, acme@redhat.com,
	eranian@google.com, ak@linux.intel.com
Subject: Re: [PATCH] perf/x86/intel: Don't enable freeze-on-smi for PerfMon V1
Date: Wed, 25 Apr 2018 11:11:19 -0400	[thread overview]
Message-ID: <61647ffe-4975-9b78-c7af-a77cbbbb2d35@linux.intel.com> (raw)
In-Reply-To: <20180425145746.GX4082@hirez.programming.kicks-ass.net>



On 4/25/2018 10:57 AM, Peter Zijlstra wrote:
> On Tue, Apr 24, 2018 at 03:56:23PM -0400, kan.liang@linux.intel.com wrote:
>> From: Kan Liang <kan.liang@linux.intel.com>
>>
>> The SMM freeze feature was introduced since PerfMon V2. But the current
>> code unconditionally enables the feature for all platforms. It can
>> generate #GP exception, if the related FREEZE_WHILE_SMM bit is set for
>> the machine with PerfMon V1.
>>
>> Checking the PerfMon version. Only enable the feature for PerfMon V2 and
>> later.
> 
> That's fine..
> 
>>
>> Fixes: 6089327f5424 ("perf/x86: Add sysfs entry to freeze counters on SMI")
>> Signed-off-by: Kan Liang <kan.liang@linux.intel.com>
>> ---
>>   arch/x86/events/intel/core.c | 9 ++++++---
>>   1 file changed, 6 insertions(+), 3 deletions(-)
>>
>> diff --git a/arch/x86/events/intel/core.c b/arch/x86/events/intel/core.c
>> index 4f2a5c7..08be8ed 100644
>> --- a/arch/x86/events/intel/core.c
>> +++ b/arch/x86/events/intel/core.c
>> @@ -3346,7 +3346,8 @@ static void intel_pmu_cpu_starting(int cpu)
>>   
>>   	cpuc->lbr_sel = NULL;
>>   
>> -	flip_smm_bit(&x86_pmu.attr_freeze_on_smi);
>> +	if (x86_pmu.version > 1)
>> +		flip_smm_bit(&x86_pmu.attr_freeze_on_smi);
>>   
>>   	if (!cpuc->shared_regs)
>>   		return;
> 
> And the above chunk does as advertised.
> 
>> @@ -3509,6 +3510,8 @@ static __initconst const struct x86_pmu core_pmu = {
>>   	.cpu_dying		= intel_pmu_cpu_dying,
>>   };
>>   
>> +static struct attribute *intel_pmu_attrs[];
>> +
>>   static __initconst const struct x86_pmu intel_pmu = {
>>   	.name			= "Intel",
>>   	.handle_irq		= intel_pmu_handle_irq,
>> @@ -3540,6 +3543,8 @@ static __initconst const struct x86_pmu intel_pmu = {
>>   	.format_attrs		= intel_arch3_formats_attr,
>>   	.events_sysfs_show	= intel_event_sysfs_show,
>>   
>> +	.attrs			= intel_pmu_attrs,
>> +
>>   	.cpu_prepare		= intel_pmu_cpu_prepare,
>>   	.cpu_starting		= intel_pmu_cpu_starting,
>>   	.cpu_dying		= intel_pmu_cpu_dying,
>> @@ -3918,8 +3923,6 @@ __init int intel_pmu_init(void)
>>   
>>   	x86_pmu.max_pebs_events		= min_t(unsigned, MAX_PEBS_EVENTS, x86_pmu.num_counters);
>>   
>> -
>> -	x86_pmu.attrs			= intel_pmu_attrs;
>>   	/*
>>   	 * Quirk: v2 perfmon does not report fixed-purpose events, so
>>   	 * assume at least 3 events, when not running in a hypervisor:
> 
> But what is all this about? The Changelog doesn't mention anything about
> this. Looks like an unrelated cleanup that really should've been a
> separate patch or something.

Only if the PerfMon version >= V2, the intel_pmu can be applied.
Moving intel_pmu_attrs to intel_pmu, which guarantees the feature can 
only be enabled for V2 and later.

I will modify the change log to explicitly mention it.

Thanks,
Kan

      reply	other threads:[~2018-04-25 15:11 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-04-24 19:56 [PATCH] perf/x86/intel: Don't enable freeze-on-smi for PerfMon V1 kan.liang
2018-04-25 14:57 ` Peter Zijlstra
2018-04-25 15:11   ` Liang, Kan [this message]

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=61647ffe-4975-9b78-c7af-a77cbbbb2d35@linux.intel.com \
    --to=kan.liang@linux.intel.com \
    --cc=acme@redhat.com \
    --cc=ak@linux.intel.com \
    --cc=eranian@google.com \
    --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