Re: [PATCH v6: 2/4] x86: Add enabling of the R3MWAIT during boot

From	Pavel Machek <pavel@ucw.cz>
Newsgroups	linux.kernel
Subject	Re: [PATCH v6: 2/4] x86: Add enabling of the R3MWAIT during boot
Date	2017-02-03 11:50 +0100
Message-ID	<t6JBf-ru-5@gated-at.bofh.it> (permalink)
References	(1 earlier) <swTxx-2VB-55@gated-at.bofh.it> <swUad-3cE-1@gated-at.bofh.it> <sHL3z-74K-5@gated-at.bofh.it> <sHLdf-77O-3@gated-at.bofh.it> <sMsMF-3hS-1@gated-at.bofh.it>
Organization	linux.* mail to news gateway

Show all headers | View raw

[Multipart message — attachments visible in raw view] - view raw

On Fri 2016-12-09 12:49:33, Andrejczuk, Grzegorz wrote:
> > > On Thu 2016-10-27 16:38:13, Thomas Gleixner wrote:
> > > > 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?
> > > 
> > > Its telling admin he did not make a typo on the command line. We often do that....
> >
> > Definitely not at the warning level.
> 
> Is info level OK for that message?

I'd say so.
									Pavel
-- 
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html

Back to linux.kernel | Previous | Next — Next in thread | Find similar | Unroll thread

Thread

Re: [PATCH v6: 2/4] x86: Add enabling of the R3MWAIT during boot Pavel Machek <pavel@ucw.cz> - 2017-02-03 11:50 +0100
  RE: [PATCH v6: 2/4] x86: Add enabling of the R3MWAIT during boot "Andrejczuk, Grzegorz" <grzegorz.andrejczuk@intel.com> - 2017-02-03 12:30 +0100

csiph-web