On Wed, Jun 15, 2011 at 11:30 AM, David Laight <david.lai...@aculab.com>wrote:
> > > The PPC440X currently uses 256M TLB entries to pin the > > lowmem. When we go for a relocatable kernel we have to : > > > > 1) Restrict the kernel load address to be 256M aligned > > > > OR > > > > 2) Use 16M TLB(the next possible TLB page size supported) > > entries till the first > > 256M and then use the 256M TLB entries for the rest of lowmem. > > What is wrong with: > > 3) Use 256M TLB entries with the lowest one including > addresses below the kernel base. > > Clearly the kernel shouldn't be accessing the addresses > below its base address - but that is true of a lot of > address space mapped into the kernel. > It gets mucky since we will then need need to assess how much of that 256M mapping will be above the kernel base, determine if that is sufficient to boot the kernel, if not then setup additional 16MB mappings and so on. It might be cleaner to just use multiple 16MB mappings directly? By the way we have some patches to support a non-zero (but fixed) boot address for PPC440. They are against 2.6.31, it's pretty simple stuff except also requires changes in the simpleboot wrapper. We will post them shortly since they are relevant to this discussion. John -- John Williams, PhD, B. Eng, B. IT PetaLogix - Linux Solutions for a Reconfigurable World w: www.petalogix.com p: +61-7-30090663 f: +61-7-30090663
_______________________________________________ Linuxppc-dev mailing list Linuxppc-dev@lists.ozlabs.org https://lists.ozlabs.org/listinfo/linuxppc-dev
