On Thu, 30 Aug 2018, Michal Hocko wrote:
> On Thu 30-08-18 12:44:02, Peter Zijlstra wrote:
> > On Thu, Aug 30, 2018 at 05:03:19PM +0800, Feng Tang wrote:
> > > The root cause is that when CONFIG_NO_BOOTMEM=y, before
> > > e820__memblock_setup() is called there is no memory for bootmem
> > > to allocate,
> >
> > Which you bloody well asked for by using NO_BOOTMEM=y.
> >
> > Going down this route; adding hacks for every little thing that does
> > want bootmem, completely defeats the purpose.
> >
> > If anything, make the earlycon thing depend on NO_BOOTMEM=n. That also
> > solves your problem. No earlycon, no panic.
>
> Well, there is endeavor to remove bootmem allocator altogether. So
> making earlycon depend on NO_BOOTMEM=n doesn't sound like a good fit to
If we want to remove bootmem, then reintroducing it with a static bootmem
section doesn't make any sense at all.
Thanks,
tglx
