Messages in this thread | | | From | Shahab Vahedi <> | Subject | Re: [PATCH 3/3] memblock: cleanup memblock_free interface | Date | Thu, 23 Sep 2021 12:44:18 +0000 |
| |
On 9/23/21 9:43 AM, Mike Rapoport wrote: > From: Mike Rapoport <rppt@linux.ibm.com> > > For ages memblock_free() interface dealt with physical addresses even > despite the existence of memblock_alloc_xx() functions that return a > virtual pointer. > > Introduce memblock_phys_free() for freeing physical ranges and repurpose > memblock_free() to free virtual pointers to make the following pairing > abundantly clear: > > int memblock_phys_free(phys_addr_t base, phys_addr_t size); > phys_addr_t memblock_phys_alloc(phys_addr_t base, phys_addr_t size); > > void *memblock_alloc(phys_addr_t size, phys_addr_t align); > void memblock_free(void *ptr, size_t size); > > Replace intermediate memblock_free_ptr() with memblock_free() and drop > unnecessary aliases memblock_free_early() and memblock_free_early_nid(). > > Suggested-by: Linus Torvalds <torvalds@linux-foundation.org> > Signed-off-by: Mike Rapoport <rppt@linux.ibm.com>
arch/arc part: Reviewed-by: Shahab Vahedi <shahab@synopsys.com>
Thanks, Shahab
| |