linux-kernel - Re: [X86] Add a boot parameter to force-enable PAT

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Tue, 20 May 2008 16:41:13 +0200
From:	Mikael Pettersson <mikpe@...uu.se>
To:	Dave Jones <davej@...hat.com>
Cc:	Yinghai Lu <yhlu.kernel@...il.com>,
	Linux Kernel <linux-kernel@...r.kernel.org>,
	Ingo Molnar <mingo@...e.hu>,
	Thomas Gleixner <tglx@...utronix.de>, hpa@...or.com
Subject: Re: [X86] Add a boot parameter to force-enable PAT

Dave Jones writes:
 > On Mon, May 19, 2008 at 10:53:58PM -0700, Yinghai Lu wrote:
 >  
 >  > you don't need to set that bit again...
 >  > 
 >  > prevoious !test_cpu_cap(..) already get out.
 >  
 > 
 > * Add an enablepat boot parameter, useful for testing CPUs not yet
 >   added to the whitelist.
 > * Don't try to enable PAT if it was never enabled in the first place.
 > 
 > Signed-off-by: Dave Jones <davej@...hat.com>
 > 
 > diff --git a/Documentation/kernel-parameters.txt b/Documentation/kernel-parameters.txt
 > index 72c07a0..e179c22 100644
 > --- a/Documentation/kernel-parameters.txt
 > +++ b/Documentation/kernel-parameters.txt
 > @@ -236,6 +236,10 @@ and is between 256 and 4096 characters. It is defined in the file
 >  			try_unsupported: try to drive unsupported chipsets
 >  				(may crash computer or cause data corruption)
 >  
 > +	enablepat	[i386,x86-64]
 > +			Force the CPU's PAT feature to be used even if it
 > +			isn't in the kernels whitelist.

s/kernels/kernel's/
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/