On Sat, Jan 30, 2021 at 2:10 PM Mike Rapoport <r...@kernel.org> wrote:
>
> In either case, e820__memblock_setup() won't add the range 0x0000 - 0x1000
> to memblock.memory and later during memory map initialization this range is
> left outside any zone.
Honestly, this just sounds like memblock being stupid in the first place.
Why aren't these zones padded to sane alignments?
This patch smells like working around the memblock code being fragile
rather than a real fix.
That's *particularly* true when the very line above it did a
"memblock_reserve()" of the exact same range that the memblock_add()
"adds".
Linus
