From: Jason Gunthorpe <jgg@nvidia.com>
To: David Rientjes <rientjes@google.com>
Cc: Alexander Graf <graf@amazon.com>,
Andrey Ryabinin <ryabinin.a.a@gmail.com>,
Anthony Yznaga <anthony.yznaga@oracle.com>,
Dave Hansen <dave.hansen@intel.com>,
David Hildenbrand <david@redhat.com>,
Frank van der Linden <fvdl@google.com>,
James Gowans <jgowans@amazon.com>,
Junaid Shahid <junaids@google.com>,
Matthew Wilcox <willy@infradead.org>,
Mike Rapoport <rppt@kernel.org>,
Pankaj Gupta <pankaj.gupta.linux@gmail.com>,
Pasha Tatashin <tatashin@google.com>,
Pratyush Yadav <pratyush@kernel.org>,
Vipin Sharma <vipinsh@google.com>,
Vishal Annapurve <vannapurve@google.com>,
"Woodhouse, David" <dwmw@amazon.co.uk>,
linux-mm@kvack.org, kexec@lists.infradead.org
Subject: Re: [Hypervisor Live Update] Notes from February 10, 2025
Date: Wed, 19 Feb 2025 09:31:35 -0400 [thread overview]
Message-ID: <20250219133135.GM4183890@nvidia.com> (raw)
In-Reply-To: <dc1ee0c3-d3e7-4284-6329-346b8cea68b5@google.com>
On Tue, Feb 18, 2025 at 08:04:47PM -0800, David Rientjes wrote:
> - the future of guestmemfs and what it becomes, including alignment so
> prototyping can be done
IMHO we need a generic FDBOX sort of filesystem and the ability to put
guestmemfd, memfd and hugetlbfs (fd) into it. This would completely
replace the need for a special memory-only filesystem.
Most of it should be doable with the folio preservation bitmap scheme
I showed in the v5 thread and is not particularly special.
Ie for a memfd you take all the folios under it, preserve them in the
bitmap, store the folio phys_addr_t's in a linked list of 4k chunks
and put the top of the linked list in the FDBOX for that memfd.
> - establishing an FSM for all of the various states that are agreed upon
> with common language (when memory mappings can happen, what is
> disallowed at certain stages)
I think this is very important, along with explanations where people
expect work to be performed.
Jason
prev parent reply other threads:[~2025-02-19 13:33 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-19 4:04 David Rientjes
2025-02-19 13:31 ` Jason Gunthorpe [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=20250219133135.GM4183890@nvidia.com \
--to=jgg@nvidia.com \
--cc=anthony.yznaga@oracle.com \
--cc=dave.hansen@intel.com \
--cc=david@redhat.com \
--cc=dwmw@amazon.co.uk \
--cc=fvdl@google.com \
--cc=graf@amazon.com \
--cc=jgowans@amazon.com \
--cc=junaids@google.com \
--cc=kexec@lists.infradead.org \
--cc=linux-mm@kvack.org \
--cc=pankaj.gupta.linux@gmail.com \
--cc=pratyush@kernel.org \
--cc=rientjes@google.com \
--cc=rppt@kernel.org \
--cc=ryabinin.a.a@gmail.com \
--cc=tatashin@google.com \
--cc=vannapurve@google.com \
--cc=vipinsh@google.com \
--cc=willy@infradead.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