From: Sean Christopherson <seanjc@google.com>
To: Ackerley Tng <ackerleytng@google.com>
Cc: kvm@vger.kernel.org, linux-kernel@vger.kernel.org,
roypat@amazon.co.uk, kalyazin@amazon.com,
Fuad Tabba <tabba@google.com>,
Vishal Annapurve <vannapurve@google.com>,
david@redhat.com
Subject: Re: [ANNOUNCE] PUCK Agenda - 2025.04.02 - No Topic
Date: Tue, 29 Apr 2025 09:47:06 -0700 [thread overview]
Message-ID: <aBECik9V2uAlFKGU@google.com> (raw)
In-Reply-To: <diqzplgvxbsm.fsf@ackerleytng-ctop.c.googlers.com>
On Tue, Apr 29, 2025, Ackerley Tng wrote:
>
> Would like to add an agenda item for 2025-04-30's PUCK meeting: KVM
> memory attributes vs guest_memfd shareability.
Does next week work for you? I.e. May 7th. I won't be able to make tomorrow's
PUCK (about to send a cancelation mail).
> guest_memfd tracks shareability to determine whether a page can be
> faulted by the host into userspace.
>
> pKVM does not use kvm->mem_attr_array for tracking private/shared status
> of a page, and for Coco VMs like TDX, there seems to be duplicate
> tracking of private/shared status in guest_memfd's shareability and in
> KVM's memory attributes.
>
> I would like to discuss a proposal for shared/private conversions to be
> performed through a guest_memfd (not KVM) ioctl instead of using
> KVM_SET_MEMORY_ATTRIBUTES, where Coco VMs using guest_memfd for both
> shared and private memory can be able to (with some other changes around
> KVM memory attributes) skip tracking private/shared in KVM's memory
> attributes.
Has the proposal been posted on-list anywhere? I haven't been following the
guest_memfd threads very closely (understatement).
next prev parent reply other threads:[~2025-04-29 16:47 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-02 0:29 [ANNOUNCE] PUCK Agenda - 2025.04.02 - No Topic Sean Christopherson
2025-04-29 14:49 ` Ackerley Tng
2025-04-29 16:47 ` Sean Christopherson [this message]
2025-05-01 18:07 ` Ackerley Tng
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=aBECik9V2uAlFKGU@google.com \
--to=seanjc@google.com \
--cc=ackerleytng@google.com \
--cc=david@redhat.com \
--cc=kalyazin@amazon.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=roypat@amazon.co.uk \
--cc=tabba@google.com \
--cc=vannapurve@google.com \
/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