Large physical address support on e500 platform

Kumar Gala galak at kernel.crashing.org
Wed Jan 20 06:13:57 EST 2010


On Jan 19, 2010, at 12:54 AM, Alex Dubov wrote:

> I'm working on an mpc8548 based board and recently I've encountered a
> problem, whereupon kernel crashed each time module loading is attempted. I
> traced the problem to the fact, that vmalloc_exec was setting incorrect
> page attributes on allocated pages. This, in turn, happened because I
> specified "Large physical address support" in the Kconfig, leading to
> CONFIG_PHYS_64BIT and friends being set.
> 
> It appears that having this option set on e500 pulls in incorrect headers
> and otherwise not working. CPU, however, has support for 36b physical
> addressing, which qualifies as "Large physical address".
> 
> So, the obvious question is, what is the current status of large physical
> address support on e500? Is it a problem in current git version or is it
> not ready yet?
> 
> Thanks.

Its possible that we've broken module/vmalloc support with "Large physical addressing".  Its not something I've tried in a while.  What kernel/git SHA are you using.

- k


More information about the Linuxppc-dev mailing list