[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1458748164.6393.649.camel@hpe.com>
Date: Wed, 23 Mar 2016 09:49:24 -0600
From: Toshi Kani <toshi.kani@....com>
To: Borislav Petkov <bp@...e.de>
Cc: mingo@...nel.org, hpa@...or.com, tglx@...utronix.de,
mcgrof@...e.com, jgross@...e.com, paul.gortmaker@...driver.com,
konrad.wilk@...cle.com, elliott@....com, x86@...nel.org,
xen-devel@...ts.xenproject.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH v2 2/6] x86/mm/pat: Add pat_disable() interface
On Wed, 2016-03-23 at 09:51 +0100, Borislav Petkov wrote:
> On Tue, Mar 22, 2016 at 03:40:45PM -0600, Toshi Kani wrote:
> > Will change to "Prevent the OS from initializing the PAT MSR".
> >
> > I wanted to clarify that "disable" does not mean to disable PAT MSR.
>
> How do you "disable PAT MSR" ?
We can't, but I thought not everyone knows how it works...
> I think you're overdocumenting this. pat_disable() is as clear as day
> what it does. It doesn't need any commenting...
Right, maybe I am just paranoid. I will remove the comment as you
suggested.
> > I've run checkpatch.pl and thought it was OK to have this warning
> > (instead of a >80 warning) since the error message part was not split.
> > The "attempting" part is for debugging and its string is passed from
> > the caller.
>
> We always put the quoted strings on a single line for easier grepping.
> Forget the 80-cols rule.
OK.
Thanks,
-Toshi
Powered by blists - more mailing lists