linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: "David Hildenbrand (Red Hat)" <david@kernel.org>
To: dan.j.williams@intel.com,
	"linux-coco@lists.linux.dev" <linux-coco@lists.linux.dev>,
	"linux-mm@kvack.org" <linux-mm@kvack.org>,
	KVM <kvm@vger.kernel.org>
Cc: Ackerley Tng <ackerleytng@google.com>
Subject: Re: [Invitation] bi-weekly guest_memfd upstream call on 2025-12-04
Date: Wed, 7 Jan 2026 22:52:32 +0100	[thread overview]
Message-ID: <7737563a-c2b8-4e9e-ac18-3551ed9d1a33@kernel.org> (raw)
In-Reply-To: <695ec54cf5c3_875d1009d@dwillia2-mobl4.notmuch>

On 1/7/26 21:42, dan.j.williams@intel.com wrote:
> David Hildenbrand (Red Hat) wrote:
> [..]
>> This might be the last meeting this year: I will be traveling for LPC on
>> December 11 and December 18. Then, Christmas is already around the
>> corner and we'll skip the one on December 25. So we'll probably have our
>> next meeting then on January 8.
> 
> Hi David,

Hi Dan!

> 
> Great seeing you at LPC! 

Absolutely :)

> Can I grab some time on the agenda to
> brainstorm the next level of detail on the topic I briefly ran by you in
> the hallway track? I.e. is there a path to decouple dependencies and
> land some of the low level huge page support upstream while the
> guest_memfd reworks for in place conversion and hugetlbfs backing
> continue to mature?

Yes, Ackerley already added that to the meeting agenda :)

> 
> As you said this at a minimum needs to be crippled / not production
> worthy to maintain focus and momentum on the guest_memfd rework
> completion. The observation that shifted my thinking is that, given the
> timelines and remaining work, there are solid steps that the low level
> implementations can be landing and maturing in advance of that
> integration. All net progress for upstream.

Right, I think we're good as long as we don't start splitting folios on 
partial truncation. That is: only allow truncation in THP granularity.

I might not be around tomorrow and Ackerley will likely lead the 
meeting. I'll send out a reminder mail now that I realize I haven't ...

-- 
Cheers

David


      reply	other threads:[~2026-01-07 21:52 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-12-02 10:22 David Hildenbrand (Red Hat)
2026-01-07 20:42 ` dan.j.williams
2026-01-07 21:52   ` David Hildenbrand (Red Hat) [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=7737563a-c2b8-4e9e-ac18-3551ed9d1a33@kernel.org \
    --to=david@kernel.org \
    --cc=ackerleytng@google.com \
    --cc=dan.j.williams@intel.com \
    --cc=kvm@vger.kernel.org \
    --cc=linux-coco@lists.linux.dev \
    --cc=linux-mm@kvack.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