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, lukasz.daniluk@intel.com,
james.h.cownie@intel.com, jacob.jun.pan@intel.com,
Piotr.Luc@intel.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v6: 2/4] x86: Add enabling of the R3MWAIT during boot
Date: Thu, 27 Oct 2016 16:38:13 +0200 (CEST) [thread overview]
Message-ID: <alpine.DEB.2.20.1610271625410.4817@nanos> (raw)
In-Reply-To: <1477576923-3244-3-git-send-email-grzegorz.andrejczuk@intel.com>
On Thu, 27 Oct 2016, Grzegorz Andrejczuk wrote:
> +#ifdef CONFIG_X86_64
> +static int phi_r3mwait_disabled __read_mostly;
> +
> +static int __init phir3mwait_disable(char *__unused)
> +{
> + phi_r3mwait_disabled = 1;
> + pr_warn("x86/phir3mwait: Disabled ring 3 MWAIT for Xeon Phi");
Why would that be a warning? The sysadmin added the command line switch, so
why does he needs to be warned?
> + return 1;
> +}
> +__setup("phir3mwait=disable", phir3mwait_disable);
> +
> +static void probe_xeon_phi_r3mwait(struct cpuinfo_x86 *c)
> +{
> + u64 msr;
> +
> + rdmsrl(MSR_PHI_MISC_THD_FEATURE, msr);
> +
> + if (phi_r3mwait_disabled) {
> + msr &= ~MSR_PHI_MISC_THD_FEATURE_R3MWAIT;
> + wrmsrl(MSR_PHI_MISC_THD_FEATURE, msr);
> + } else {
> + msr |= MSR_PHI_MISC_THD_FEATURE_R3MWAIT;
> + wrmsrl(MSR_PHI_MISC_THD_FEATURE, msr);
> + }
if (phi_r3mwait_disabled)
msr &= ~MSR_PHI_MISC_THD_FEATURE_R3MWAIT;
else
msr |= MSR_PHI_MISC_THD_FEATURE_R3MWAIT;
wrmsrl(MSR_PHI_MISC_THD_FEATURE, msr);
Would be too simple and obvious, right? You still can add the extra bits of
setting the capability flag into the else path.
> init_intel_energy_perf(c);
> +
> + /*
> + * Setting ring 3 MONITOR/MWAIT for thread
> + * when CPU is Xeon Phi Family x200 (KnightsLanding).
> + */
> + if (c->x86 == 6 && c->x86_model == INTEL_FAM6_XEON_PHI_KNL)
Please move this conditional into the probe function.
> + probe_xeon_phi_r3mwait(c);
Can you please check with your hardware people, whether this function is
somewhere detectable. bit 0 of the MISC_*FEATURE* MSR (Ring 3 CPUID fault
enable) is detectable via the PLATFORM_INFO MSR. I would be surprised if
this thing is not detectable in some way.
I really prefer detectable things over hardcoded crap which depends on
model information.
Thanks,
tglx
next prev parent reply other threads:[~2016-10-27 14:40 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-27 14:01 [PATCH v6 0/4] Enabling Ring 3 MONITOR/MWAIT feature for Knights Landing Grzegorz Andrejczuk
2016-10-27 14:02 ` [PATCH v6: 1/4] x86/msr: Add R3MWAIT register and bit to msr-info.h Grzegorz Andrejczuk
2016-10-27 14:32 ` Thomas Gleixner
2016-10-27 14:02 ` [PATCH v6: 2/4] x86: Add enabling of the R3MWAIT during boot Grzegorz Andrejczuk
2016-10-27 14:38 ` Thomas Gleixner [this message]
2016-10-27 16:53 ` Andrejczuk, Grzegorz
2016-10-27 18:22 ` Thomas Gleixner
2016-11-26 13:15 ` Pavel Machek
2016-11-26 13:20 ` Thomas Gleixner
2016-12-09 12:49 ` Andrejczuk, Grzegorz
2017-02-03 10:47 ` Pavel Machek
2017-02-03 11:28 ` Andrejczuk, Grzegorz
2016-10-27 14:02 ` [PATCH v6: 3/4] x86: Use HWCAP2 to expose Xeon Phi ring 3 MWAIT Grzegorz Andrejczuk
2016-10-27 14:02 ` [PATCH v6: 4/4] x86/cpufeature: Add R3MWAIT to CPU features Grzegorz Andrejczuk
2016-10-27 14:30 ` Borislav Petkov
2016-10-27 16:46 ` Andrejczuk, Grzegorz
2016-10-27 17:01 ` Borislav Petkov
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.1610271625410.4817@nanos \
--to=tglx@linutronix.de \
--cc=Piotr.Luc@intel.com \
--cc=bp@suse.de \
--cc=dave.hansen@linux.intel.com \
--cc=grzegorz.andrejczuk@intel.com \
--cc=hpa@zytor.com \
--cc=jacob.jun.pan@intel.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