From: Thomas Gleixner <tglx@linutronix.de>
To: Grzegorz Andrejczuk <grzegorz.andrejczuk@intel.com>
Cc: mingo@redhat.com, hpa@zytor.com, x86@kernel.org, bp@suse.de,
dave.hansen@linux.intel.com, linux-kernel@vger.kernel.org,
lukasz.daniluk@intel.com, james.h.cownie@intel.com
Subject: Re: [PATCH v2 4/4] Add R3MWAIT to CPU features
Date: Wed, 12 Oct 2016 15:22:16 +0200 (CEST) [thread overview]
Message-ID: <alpine.DEB.2.20.1610121518550.8572@nanos> (raw)
In-Reply-To: <1476274585-21679-5-git-send-email-grzegorz.andrejczuk@intel.com>
On Wed, 12 Oct 2016, Grzegorz Andrejczuk wrote:
> diff --git a/arch/x86/kernel/cpu/scattered.c b/arch/x86/kernel/cpu/scattered.c
> index 8cb57df..e4ff3d0 100644
> --- a/arch/x86/kernel/cpu/scattered.c
> +++ b/arch/x86/kernel/cpu/scattered.c
> @@ -29,6 +29,7 @@ void init_scattered_cpuid_features(struct cpuinfo_x86 *c)
> u32 max_level;
> u32 regs[4];
> const struct cpuid_bit *cb;
> + u64 misc_thd_enable;
>
> static const struct cpuid_bit cpuid_bits[] = {
> { X86_FEATURE_INTEL_PT, CR_EBX,25, 0x00000007, 0 },
> @@ -54,4 +55,8 @@ void init_scattered_cpuid_features(struct cpuinfo_x86 *c)
> if (regs[cb->reg] & (1 << cb->bit))
> set_cpu_cap(c, cb->feature);
> }
> +
> + rdmsrl(MSR_PHI_MISC_THD_FEATURE, misc_thd_enable);
And what makes you sure that you can just use rdmsrl() unconditionally and
assume that the MSR is actually there? This breaks the world and some
more. Either make sure that this is only ran on PHI or simply use
rdmsrl_safe() which is safe everywhere,
> + if ((misc_thd_enable & MSR_PHI_MISC_THD_FEATURE_R3MWAIT) != 0)
if (misc_thd_enable & MSR_PHI_MISC_THD_FEATURE_R3MWAIT)
is entirely sufficient.
> + set_cpu_cap(c, X86_FEATURE_PHIR3MWAIT);
Thanks,
tglx
prev parent reply other threads:[~2016-10-12 13:25 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-12 12:16 [PATCH v2 0/4] Enabling Ring 3 MONITOR/MWAIT feature for Knights Landing Grzegorz Andrejczuk
2016-10-12 12:16 ` [PATCH v2 1/4] Add R3MWAIT register and bit to msr-info.h Grzegorz Andrejczuk
2016-10-12 12:16 ` [PATCH v2 2/4] Add enabling of the R3 MWAIT during boot for KNL Grzegorz Andrejczuk
2016-10-12 13:34 ` Thomas Gleixner
2016-10-12 16:28 ` Dave Hansen
2016-10-13 15:18 ` Thomas Gleixner
2016-10-12 13:35 ` Thomas Gleixner
2016-10-12 14:32 ` Dave Hansen
2016-10-12 17:21 ` Dave Hansen
2016-10-12 12:16 ` [PATCH v2 3/4] Add hwcap2 for x86 Grzegorz Andrejczuk
2016-10-12 13:38 ` Thomas Gleixner
2016-10-12 13:48 ` Thomas Gleixner
2016-10-12 12:16 ` [PATCH v2 4/4] Add R3MWAIT to CPU features Grzegorz Andrejczuk
2016-10-12 12:51 ` Borislav Petkov
2016-10-12 13:22 ` Thomas Gleixner [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=alpine.DEB.2.20.1610121518550.8572@nanos \
--to=tglx@linutronix.de \
--cc=bp@suse.de \
--cc=dave.hansen@linux.intel.com \
--cc=grzegorz.andrejczuk@intel.com \
--cc=hpa@zytor.com \
--cc=james.h.cownie@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lukasz.daniluk@intel.com \
--cc=mingo@redhat.com \
--cc=x86@kernel.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
all inboxes | Powered by JetHome®