From: Pratyush Yadav <pratyush@kernel.org>
To: Pasha Tatashin <pasha.tatashin@soleen.com>
Cc: Pratyush Yadav <pratyush@kernel.org>,
linux-mm@kvack.org, lsf-pc@lists.linux-foundation.org,
Mike Rapoport <rppt@kernel.org>,
David Rientjes <rientjes@google.com>,
Muchun Song <muchun.song@linux.dev>,
Oscar Salvador <osalvador@suse.de>,
David Hildenbrand <david@kernel.org>,
Jason Gunthorpe <jgg@ziepe.ca>, Alexander Graf <graf@amazon.com>,
David Matlack <dmatlack@google.com>
Subject: Re: [LSF/MM/BPF TOPIC] HugeTLB file preservation across live update
Date: Tue, 10 Feb 2026 14:47:44 +0100 [thread overview]
Message-ID: <2vxzms1gsoan.fsf@kernel.org> (raw)
In-Reply-To: <CA+CK2bCkLKrP6yvS=qpao1krfCbxUbj73bq8m8JnmKqtjp3tKQ@mail.gmail.com> (Pasha Tatashin's message of "Sat, 7 Feb 2026 11:21:45 -0500")
Hi Pasha,
On Sat, Feb 07 2026, Pasha Tatashin wrote:
> On Fri, Feb 6, 2026 at 12:48 PM Pratyush Yadav <pratyush@kernel.org> wrote:
>>
[...]
>> Goals of the discussion
>> -----------------------
>>
>> This session will aim to present the topic, explain why it is needed,
>> show how the support works, and most importantly, collect feedback on
>> how to proceed with this work.
>>
>> PS: if any HugeTLB developers or maintainers are reading this, it would
>> be great to have your initial thoughts on the RFC [4] so I can present a
>> more polished patchset at the conference and make the most of the
>> discussion.
>
> Thank you Pratyush for proposing this topic. A few more thoughts:
> While the discussion should be about memfd+hugetlb support, the long
> term goal is to make this work as an enabler for guestmemfd+hugetlb
> preservation support.
Yes, I plan to use the HugeTLB work here as the backend for
guest_memfd+hugetlb preservation. I can discuss some ideas for that in
my talk if time permits. Or do you think that should be a separate talk?
[...]
--
Regards,
Pratyush Yadav
prev parent reply other threads:[~2026-02-10 13:47 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-06 17:48 Pratyush Yadav
2026-02-07 16:21 ` Pasha Tatashin
2026-02-10 13:47 ` Pratyush Yadav [this message]
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=2vxzms1gsoan.fsf@kernel.org \
--to=pratyush@kernel.org \
--cc=david@kernel.org \
--cc=dmatlack@google.com \
--cc=graf@amazon.com \
--cc=jgg@ziepe.ca \
--cc=linux-mm@kvack.org \
--cc=lsf-pc@lists.linux-foundation.org \
--cc=muchun.song@linux.dev \
--cc=osalvador@suse.de \
--cc=pasha.tatashin@soleen.com \
--cc=rientjes@google.com \
--cc=rppt@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