Re: [PATCH v1 1/2] mm/memblock: expose only miminal interface to add/walk physmem

> Am 30.06.2020 um 18:58 schrieb David Hildenbrand : > >  >> >>> extern struct memblock memblock; >>> @@ -114,6 +110,19 @@ int memblock_remove(phys_addr_t base, phys_addr_t >>> size); >>> int memblock_free(phys_addr_t base, phys_addr_t size); >>> int memblock_reserve(phys_addr_t base, phys_a

Re: [PATCH v1 1/2] mm/memblock: expose only miminal interface to add/walk physmem

>> extern struct memblock memblock; >> @@ -114,6 +110,19 @@ int memblock_remove(phys_addr_t base, phys_addr_t size); >> int memblock_free(phys_addr_t base, phys_addr_t size); >> int memblock_reserve(phys_addr_t base, phys_addr_t size); >> #ifdef CONFIG_HAVE_MEMBLOCK_PHYS_MAP >> +/** >> + * for_

Re: [PATCH v1 1/2] mm/memblock: expose only miminal interface to add/walk physmem

On Tue, Jun 30, 2020 at 10:17:29AM +0200, David Hildenbrand wrote: > "physmem" in the memblock allocator is somewhat weird: it's not actually > used for allocation, it's simply information collected during boot, which > describes the unmodified physical memory map at boot time, without any > standb

Re: [PATCH v1 1/2] mm/memblock: expose only miminal interface to add/walk physmem

On 30.06.20 10:17, David Hildenbrand wrote: > "physmem" in the memblock allocator is somewhat weird: it's not actually > used for allocation, it's simply information collected during boot, which > describes the unmodified physical memory map at boot time, without any > standby/hotplugged memory. It

[PATCH v1 1/2] mm/memblock: expose only miminal interface to add/walk physmem

"physmem" in the memblock allocator is somewhat weird: it's not actually used for allocation, it's simply information collected during boot, which describes the unmodified physical memory map at boot time, without any standby/hotplugged memory. It's only used on s390x and is currently the only reas