[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <86802c440804281318o3a6019ddr3d452be53fc60e62@mail.gmail.com>
Date: Mon, 28 Apr 2008 13:18:33 -0700
From: "Yinghai Lu" <yhlu.kernel@...il.com>
To: "Ingo Molnar" <mingo@...e.hu>
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
On Mon, Apr 28, 2008 at 1:15 PM, Ingo Molnar <mingo@...e.hu> wrote:
>
> * 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.
use disable_mtrr_cleanup and CONFIG_MTRR_SANITIZER?
YH
--
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/
Powered by blists - more mailing lists