[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <20250903063018.3346652-1-rppt@kernel.org>
Date: Wed, 3 Sep 2025 09:30:16 +0300
From: Mike Rapoport <rppt@...nel.org>
To: Andrew Morton <akpm@...ux-foundation.org>
Cc: Alexander Graf <graf@...zon.com>,
Baoquan He <bhe@...hat.com>,
Changyuan Lyu <changyuanl@...gle.com>,
Chris Li <chrisl@...nel.org>,
Jason Gunthorpe <jgg@...dia.com>,
Mike Rapoport <rppt@...nel.org>,
Pasha Tatashin <pasha.tatashin@...een.com>,
Pratyush Yadav <pratyush@...nel.org>,
kexec@...ts.infradead.org,
linux-mm@...ck.org,
linux-kernel@...r.kernel.org
Subject: [PATCH 0/2] kho: add support for preserving vmalloc allocations
From: "Mike Rapoport (Microsoft)" <rppt@...nel.org>
Hi,
Following the discussion about preservation of memfd with LUO [1] these
patches add support for preserving vmalloc allocations.
Any KHO uses case presumes that there's a data structure that lists
physical addresses of preserved folios (and potentially some additional
metadata). Allowing vmalloc preservations with KHO allows scalable
preservation of such data structures.
For instance, instead of allocating array describing preserved folios in
the fdt, memfd preservation can use vmalloc:
preserved_folios = vmalloc_array(nr_folios, sizeof(*preserved_folios));
memfd_luo_preserve_folios(preserved_folios, folios, nr_folios);
kho_preserve_vmalloc(preserved_folios, &folios_info);
[1] https://lore.kernel.org/all/20250807014442.3829950-30-pasha.tatashin@soleen.com
Mike Rapoport (Microsoft) (2):
kho: add support for preserving vmalloc allocations
lib/test_kho: use kho_preserve_vmalloc instead of storing addresses in fdt
include/linux/kexec_handover.h | 12 +++
kernel/kexec_handover.c | 140 +++++++++++++++++++++++++++++++++
lib/test_kho.c | 30 +++++--
3 files changed, 175 insertions(+), 7 deletions(-)
base-commit: b320789d6883cc00ac78ce83bccbfe7ed58afcf0
--
2.50.1
Powered by blists - more mailing lists