Re: [PATCH v3 04/21] kho: return virtual address of mem_map

Next message: Mike Rapoport: "Re: [PATCH v3 17/21] mm/mm_init: don't rely on memblock to get KHO scratch migratetype"
Previous message: David Hildenbrand (Arm): "Re: [PATCH mm-unstable v1 2/3] mm/migrate.c: Prevent folio splitting from interacting with KSM"
In reply to: Pratyush Yadav: "[PATCH v3 04/21] kho: return virtual address of mem_map"
Next in thread: Pratyush Yadav: "[PATCH v3 09/21] kho: add data argument to radix walk callback"
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

From: Mike Rapoport

Date: Wed Jul 15 2026 - 05:35:48 EST

> kho: return virtual address of mem_map

It's not really clear from where ...

> Currently it is only used by kho_populate(), which doesn't care whether

... and where it is used ;-)

--
Sincerely yours,
Mike.