[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20080321184430.GL2346@one.firstfloor.org>
Date: Fri, 21 Mar 2008 19:44:30 +0100
From: Andi Kleen <andi@...stfloor.org>
To: Thomas Gleixner <tglx@...utronix.de>
Cc: Andi Kleen <andi@...stfloor.org>, andreas.herrmann3@....com,
mingo@...e.hu, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] [4/7] Don't use large pages to map the first 2/4MB of memory
On Fri, Mar 21, 2008 at 07:03:19PM +0100, Thomas Gleixner wrote:
> On Fri, 21 Mar 2008, Andi Kleen wrote:
> > > Also we split the first GB mapping anyway due to the various regions
> > > (NX, RO, UC) in there.
> >
> > I didn't think so unless you have DEBUG_RODATA enabled?
>
> NX is independent of DEBUG_RODATA
Sure, but it is still not split by default. At least I don't see any code
for that anywhere except in my own patchkit.
> and the RODATA protection should be
> made unconditional on anyway.
Requiring hundreds instead of two TLB entries for the kernel text?
I must say I personally cannot ever remember any bug caught by RODATA
anyways, so I am a bit dubious on its value.
> > Also there
> > should be no UC region there as known by the kernel. There might
> > be a WC region there from the frame buffer code, but that is an MTRR,
> > not a pageattr.
>
> The first ioremap of the PCI space splits the GB page as well.
PCI space is normally in the fourth or sometimes third GB page,
not in the first. I am not aware of any system that has the PCI hole
in the first GB.
-Andi
--
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