[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date: Mon, 11 Nov 2013 15:53:51 +0800
From: Ming Lei <tom.leiming@...il.com>
To: Axel Lin <axel.lin@...ics.com>
Cc: Rusty Russell <rusty@...tcorp.com.au>,
Russell King <linux@....linux.org.uk>,
Michal Marek <mmarek@...e.cz>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
linux-arm-kernel <linux-arm-kernel@...ts.infradead.org>
Subject: Re: kernel BUG at kernel/kallsyms.c:222!
Hi,
On Mon, Nov 11, 2013 at 2:43 PM, Axel Lin <axel.lin@...ics.com> wrote:
> 2013/11/11 Rusty Russell <rusty@...tcorp.com.au>:
>
> Hi Rusty,
>
> I don't have other noMMU platform to test.
> But I think this issue impacts various !CONFIG_MMU platforms:
> We have CONFIG_PAGE_OFFSET=0xC0000000 in various default configs.
> For !CONFIG_MMU case, it just don't use the CONFIG_PAGE_OFFSET setting.
> So use CONFIG_PAGE_OFFSET to filter symbols looks wrong to me for all
> !CONFIG_MMU cases.
>
> Below is PAGE_OFFSET setting for !CONFIG_MMU case:
> (arch/arm/include/asm/memory.h)
>
> #ifndef PHYS_OFFSET
> #define PHYS_OFFSET UL(CONFIG_DRAM_BASE)
> #endif
>
> #ifndef END_MEM
> #define END_MEM (UL(CONFIG_DRAM_BASE) + CONFIG_DRAM_SIZE)
> #endif
>
> #ifndef PAGE_OFFSET
> #define PAGE_OFFSET (PHYS_OFFSET)
> #endif
>
> My patchs for gpl327xx SoC is still in very early stage.
> I think you should send your fix upstream because I think it impacts other
> noMMU platforms (for above reason).
I suggest to do it when we are clear behind the break.
As I mentioned, no matter what PAGE_OFFSET is, if you link vmlinux
from the address of PAGE_OFFSET(that is what arm's link script in tree
does), the filter won't break anything.
Thanks,
--
Ming Lei
--
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