From: Mike Rapoport <rppt@kernel.org>
To: lsf-pc@lists.linux-foundation.org,
Alexander Graf <graf@amazon.com>,
"Gowans, James" <jgowans@amazon.com>
Cc: linux-mm@kvack.org, David Rientjes <rientjes@google.com>,
Pasha Tatashin <pasha.tatashin@soleen.com>
Subject: [LSF/MM/BPF TOPIC] memory persistence over kexec
Date: Mon, 20 Jan 2025 09:54:15 +0200 [thread overview]
Message-ID: <Z44BJw_t8gDgUnLv@kernel.org> (raw)
Hi,
I'd like to discuss memory persistence across kexec.
Currently there is ongoing work on Kexec HandOver (KHO) [1] that allows
serialization and deserialization of kernel data as well as preserving
arbitrary memory ranges across kexec.
In addition, KHO keeps a physically contiguous memory regions that are
guaranteed to not have any memory that KHO would preserve, but still can be
used by the system. The kexeced kernel bootstraps itself using those
regions and sets all handed over memory as in use. KHO users then can
recover their state from the preserved data. This includes memory
reservations, where the user can either discard or claim reservations.
KHO can be used as the base layer for implementation of persistence-aware
memory allocator and persistent in-memory filesystem.
Aside from status update on KHO progress there are a few topics that I would
like to discuss:
* Is it feasible and desirable to enable KHO support in tmpfs and hugetlbfs?
* Or is it better to implement yet another in-memory filesystem dedicated
for persistence?
* What is the best way to ensure that the memory we want to persist is not
scattered all over the place?
[1] https://lore.kernel.org/all/20240117144704.602-1-graf@amazon.com/
--
Sincerely yours,
Mike.
next reply other threads:[~2025-01-20 7:54 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-20 7:54 Mike Rapoport [this message]
2025-01-20 14:14 ` Jason Gunthorpe
2025-01-20 19:42 ` David Rientjes
2025-01-22 23:30 ` Pasha Tatashin
2025-01-25 9:53 ` Mike Rapoport
2025-01-25 15:19 ` Pasha Tatashin
2025-01-26 20:04 ` Jason Gunthorpe
2025-01-26 20:41 ` Pasha Tatashin
2025-01-27 0:21 ` Alexander Graf
2025-01-27 13:15 ` Jason Gunthorpe
2025-01-27 16:12 ` Alexander Graf
2025-01-28 14:04 ` Jason Gunthorpe
2025-01-27 13:05 ` Jason Gunthorpe
2025-01-24 21:03 ` Zhu Yanjun
2025-01-24 11:30 ` Mike Rapoport
2025-01-24 14:56 ` Jason Gunthorpe
2025-01-24 18:23 ` Andrey Ryabinin
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=Z44BJw_t8gDgUnLv@kernel.org \
--to=rppt@kernel.org \
--cc=graf@amazon.com \
--cc=jgowans@amazon.com \
--cc=linux-mm@kvack.org \
--cc=lsf-pc@lists.linux-foundation.org \
--cc=pasha.tatashin@soleen.com \
--cc=rientjes@google.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox