[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20080429103150.GJ23198@elte.hu>
Date: Tue, 29 Apr 2008 12:31:50 +0200
From: Ingo Molnar <mingo@...e.hu>
To: "Eric W. Biederman" <ebiederm@...ssion.com>
Cc: Yinghai Lu <yhlu.kernel@...il.com>,
Gabriel C <nix.or.die@...glemail.com>,
Andi Kleen <andi@...stfloor.org>,
Andrew Morton <akpm@...ux-foundation.org>,
"H. Peter Anvin" <hpa@...or.com>,
LKML <linux-kernel@...r.kernel.org>,
Jesse Barnes <jesse.barnes@...el.com>,
Mika Fischer <mika.fischer@...pnet.de>, balajirrao@...il.com
Subject: Re: [PATCH] x86_32: trim memory by updating e820 v3
* Eric W. Biederman <ebiederm@...ssion.com> wrote:
> So lets concentrate on PAT to solve contiguous MTRR region problems.
>
> We can upgrade UC to WC with pat. As well as demote WB to UC or WC.
> So for those regions we know about we should be in good shape.
sure, but whatever we do now in the sysfs API space, it will hit distros
only in a year, relistically, because Xorg also has to adopt to it. The
workaround from Yinghai looks reasonably configurable - if we mess up
(say an SMM comes in while we fiddle with the MTRRs) we'll likely get a
lockup right then, during bootup, so it wont be hard to realize what
went wrong. In that sense it's in fact safer to do it during early init
than let the user do it via some script, because the window is smaller,
etc.
we still default to the safe mode of course and dont touch MTRRs, but
for note the various configuration options that are available to distros
and users.
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/
Powered by blists - more mailing lists