linux-kernel - Re: [PATCH] x86: mtrr cleanup for converting continuous to discrete layout v3

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]

Message-ID: <20080428201506.GE15840@elte.hu>
Date:	Mon, 28 Apr 2008 22:15:06 +0200
From:	Ingo Molnar <mingo@...e.hu>
To:	yhlu.kernel@...il.com
Cc:	Andrew Morton <akpm@...ux-foundation.org>,
	"H. Peter Anvin" <hpa@...or.com>,
	Thomas Gleixner <tglx@...utronix.de>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	Gabriel C <nix.or.die@...glemail.com>,
	Mika Fischer <mika.fischer@...pnet.de>
Subject: Re: [PATCH] x86: mtrr cleanup for converting continuous to
	discrete layout v3


* Yinghai Lu <yhlu.kernel.send@...il.com> wrote:

> some BIOS like to use continus MTRR layout, and some X driver can not 
> add WB entries for graphical cards when 4g or more RAM installed.
> 
> the patch will change MTRR to discrete.
> 
> mtrr_chunk_size= could be used to have smaller continuous block to 
> hold holes. default is 256m, could be set according to size of 
> graphics card memory.
> 
> v2: fix -1 for UC checking

> v3: default to disable, and need use enable_mtrr_cleanup to enable 
>     this feature
>     skip the var state change warning.
>     remove next_basek in range_to_mtrr()

a boot option is often inconvenient though - could you perhaps also make 
this a Kconfig option, with it defaulting to off? Something like 
CONFIG_MTRR_SANITIZE=y or so? That way distros can make a conscious 
decision as well whether they want this feature (for the Xorg they pick) 
or not.

	Ingo
--
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/