On Sat, Dec 12, 2020 at 08:37:49PM +0100, Heiner Kallweit wrote:
> Since 950c37691925 ("mm: memblock: enforce overlap of memory.memblock
> and memory.reserved") I get the following warning (on x86).
>
> memblock: reserved range [0x0000000000000000-0x0000000000001000] is not in memory
> memblock: reserved range [0x000000000009f000-0x0000000000100000] is not in memory
>
> According to comment "Some architectures (e.g. x86) have reserved pages
> outside of memblock.memory." it seems there's nothing wrong with it,
> then why a warning? Wouldn't debug level be better suited?
I think that this is wrong to consider memory reserved by firmware as
"not memory", hence the warning.
Anyway, this patch needs an update as it breaks arm [1] and maybe other
machines. During the update I'll reconsider the printk level.
[1] https://lore.kernel.org/lkml/127999c4-7d56-0c36-7f88-8e1a5c934cae@xxxxxxxxxxxxx/
--
Sincerely yours,
Mike.
