Re: [Suggestion] Latest randconfig build errors for CONFIG_MMU=no

From: Will Deacon
Date: Sun Mar 17 2013 - 10:41:03 EST


On Thu, Mar 14, 2013 at 01:25:56PM +0000, Jonathan Austin wrote:
> On 14/03/13 03:44, Chen Gang wrote:
> > Hello Maintainers:
> >
> > when use randconfig:
> > make V=1 EXTRA_CFLAGS=-W ARCH=arm randconfig
> > (and "grep CONFIG_MMU .config" outputs "# CONFIG_MMU is not set")
> >
> > the error information:
> > arch/arm/kernel/suspend.c: ååæâcpu_suspendâä:
> > arch/arm/kernel/suspend.c:56:32: éèïæéæåäååçåçæé
> > arch/arm/kernel/suspend.c:70:3: éèïéååæåæâcpu_switch_mmâ [-Werror=implicit-function-declaration]
> > arch/arm/kernel/suspend.c:71:3: éèïéååæåæâlocal_flush_bp_allâ [-Werror=implicit-function-declaration]
> > arch/arm/kernel/suspend.c:72:3: éèïéååæåæâlocal_flush_tlb_allâ [-Werror=implicit-function-declaration]
> >
> > I want to be sure whether we can bear it ?
> >
>
> You're right that at the moment that suspend code is broken for NOMMU.
>
> However, Will Deacon has a patch to fix it in his nommu branch on
> kernel.org:
>
> https://git.kernel.org/cgit/linux/kernel/git/will/linux.git/commit/?h=nommu
>
> I'll let Will comment on how/when he might look at proposing that code
> to be merged.

I can probably bring that up to speed with -rc2 if people are interested.
The tricky part is testing -- I used a software model that had a magic
control block for killing off CPUs when I wrote this originally.

Will
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/