kexec.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: Mike Rapoport <rppt@kernel.org>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Alexander Graf <graf@amazon.com>, Baoquan He <bhe@redhat.com>,
	Changyuan Lyu <changyuanl@google.com>,
	Chris Li <chrisl@kernel.org>, Jason Gunthorpe <jgg@nvidia.com>,
	Pasha Tatashin <pasha.tatashin@soleen.com>,
	Pratyush Yadav <pratyush@kernel.org>,
	kexec@lists.infradead.org, linux-mm@kvack.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 0/2] kho: add support for preserving vmalloc allocations
Date: Mon, 8 Sep 2025 13:34:56 +0300	[thread overview]
Message-ID: <aL6xUMlRFSYm41uS@kernel.org> (raw)
In-Reply-To: <20250907070022.2177974-1-rppt@kernel.org>

Argh, I've messed up the posting :(
Sorry for the noise.

On Sun, Sep 07, 2025 at 10:00:17AM +0300, Mike Rapoport wrote:
> From: "Mike Rapoport (Microsoft)" <rppt@kernel.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
> 
> v2 changes:
> * support preservation of vmalloc backed by large pages
> * add check for supported vmalloc flags and preserve the flags to be
>   able to identify incompatible preservations
> * don't use kho_preserve_phys()
> * add kernel-doc
> 
> v1: https://lore.kernel.org/all/20250903063018.3346652-1-rppt@kernel.org
> 
> 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        | 200 +++++++++++++++++++++++++++++++++
>  lib/test_kho.c                 |  30 +++--
>  3 files changed, 235 insertions(+), 7 deletions(-)
> 
> 
> base-commit: b320789d6883cc00ac78ce83bccbfe7ed58afcf0
> -- 
> 2.50.1
> 

-- 
Sincerely yours,
Mike.


  parent reply	other threads:[~2025-09-08 12:05 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-09-07  7:00 [PATCH v2 0/2] kho: add support for preserving vmalloc allocations Mike Rapoport
2025-09-07  7:00 ` [PATCH v2 1/2] " Mike Rapoport
2025-09-07  7:00 ` [PATCH v2 2/2] lib/test_kho: use kho_preserve_vmalloc instead of storing addresses in fdt Mike Rapoport
2025-09-07  7:00 ` [PATCH v3 0/2] kho: add support for preserving vmalloc allocations Mike Rapoport
2025-09-07  7:00 ` [PATCH v3 1/2] " Mike Rapoport
2025-09-07  7:00 ` [PATCH v3 2/2] lib/test_kho: use kho_preserve_vmalloc instead of storing addresses in fdt Mike Rapoport
2025-09-08 10:34 ` Mike Rapoport [this message]
  -- strict thread matches above, loose matches on Subject: below --
2025-09-05 13:13 [PATCH v2 0/2] kho: add support for preserving vmalloc allocations Mike Rapoport

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=aL6xUMlRFSYm41uS@kernel.org \
    --to=rppt@kernel.org \
    --cc=akpm@linux-foundation.org \
    --cc=bhe@redhat.com \
    --cc=changyuanl@google.com \
    --cc=chrisl@kernel.org \
    --cc=graf@amazon.com \
    --cc=jgg@nvidia.com \
    --cc=kexec@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=pasha.tatashin@soleen.com \
    --cc=pratyush@kernel.org \
    /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;
as well as URLs for NNTP newsgroup(s).