kexec.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: Pratyush Yadav <pratyush@kernel.org>
To: David Rientjes <rientjes@google.com>
Cc: Alexander Graf <graf@amazon.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>,
	 Jason Gunthorpe <jgg@nvidia.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 24, 2025
Date: Fri, 07 Mar 2025 01:09:45 +0000	[thread overview]
Message-ID: <mafs01pv9k5nq.fsf@kernel.org> (raw)
In-Reply-To: <7154b857-01cf-a8c6-ea02-51d095bafabf@google.com>

Hi all,

On Sun, Mar 02 2025, David Rientjes wrote:

> Hi everybody,
>
> Here are the notes from the last Hypervisor Live Update call that happened 
> on Monday, February 24.  Thanks for everybody who was involved!
>
[...]
>
> Pratyush took the AI to look at implementation on memfd.  Mike took the
> AI to look at memory reservation.
>
> ----->o-----
> I pivoted the discussion toward fdbox which ended up never being posted
> upstream.  Pratyush provided the link to the most recent code:
> https://github.com/agraf/linux-2.6/blob/kvm-kho-gmem-test/drivers/misc/fdbox.c
> This work likely would need to be picked up to pursue upstream because
> the current code has several TODO's.  (A struct miscdevice was called out
> as curious.)
>
> It was noted that it would be difficult to support memfd without
> something like fdbox, so whether the fdbox code itself were upstreamed or
> it becomes more generic from the work on memfd, the base support would
> need to be provided somehow.
>
> Mike and Jason suggested designing fdbox and then starting to use it for
> memfd.  This would need to be aligned by stakeholders, including the UAPI
> for fdbox.  Pratyush will be looking into fdbox or inventing something
> similar while working on memfd.
>
> We need to propose the fdbox design and UAPI.

As promised, I have taken the last couple weeks in coming up with a
basic FDBox design, along with having memfd use it (currently via shmem,
since I am more familiar with that than with hugetlbfs). The patches can
be found at [0].

I am travelling next week so I am not sure if I will be able to attend
the next session. If I do, I would like to talk more about the patches
and FDBox if time permits. Anyway, looking forward to getting some
feedback on the patches :-)

[0] https://lore.kernel.org/linux-mm/20250307005830.65293-1-ptyadav@amazon.de/T/#u

[...]

-- 
Regards,
Pratyush Yadav


      reply	other threads:[~2025-03-07  1:29 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-03-03  4:21 [Hypervisor Live Update] Notes from February 24, 2025 David Rientjes
2025-03-07  1:09 ` 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=mafs01pv9k5nq.fsf@kernel.org \
    --to=pratyush@kernel.org \
    --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=jgg@nvidia.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=rientjes@google.com \
    --cc=rppt@kernel.org \
    --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;
as well as URLs for NNTP newsgroup(s).