From: David Hildenbrand <david@redhat.com>
To: Elliot Berman <quic_eberman@quicinc.com>,
Paolo Bonzini <pbonzini@redhat.com>,
Andrew Morton <akpm@linux-foundation.org>,
Sean Christopherson <seanjc@google.com>,
Fuad Tabba <tabba@google.com>,
Ackerley Tng <ackerleytng@google.com>,
Mike Rapoport <rppt@kernel.org>, "H. Peter Anvin" <hpa@zytor.com>
Cc: James Gowans <jgowans@amazon.com>,
linux-fsdevel@vger.kernel.org, kvm@vger.kernel.org,
linux-coco@lists.linux.dev, linux-arm-msm@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-mm@kvack.org
Subject: Re: [PATCH RFC v3 0/2] mm: Refactor KVM guest_memfd to introduce guestmem library
Date: Fri, 15 Nov 2024 11:31:19 +0100 [thread overview]
Message-ID: <1c524181-5518-44bb-9985-d9d12bb92073@redhat.com> (raw)
In-Reply-To: <20241113-guestmem-library-v3-0-71fdee85676b@quicinc.com>
On 13.11.24 23:34, Elliot Berman wrote:
> In preparation for adding more features to KVM's guest_memfd, refactor
> and introduce a library which abtracts some of the core-mm decisions
> about managing folios associated with guest memory. The goal of the
> refactor serves two purposes:
>
> 1. Provide an easier way to reason about memory in guest_memfd. KVM
> needs to support multiple confidentiality models (TDX, SEV, pKVM, Arm
> CCA). These models support different semantics for when the host
> can(not) access guest memory. An abstraction for the allocator and
> managing the state of pages will make it eaiser to reason about the
> state of folios within the guest_memfd.
>
> 2. Provide a common implementation for other users such as Gunyah [1] and
> guestmemfs [2].
>
> In this initial series, I'm seeking comments for the line I'm drawing
> between library and user (KVM). I've not introduced new functionality in
> this series; the first new feature will probably be Fuad's mappability
> patches [3].
Right, or the dummy mmap + vma->set_policy patches for NUMA handling.
--
Cheers,
David / dhildenb
prev parent reply other threads:[~2024-11-15 10:31 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-13 22:34 Elliot Berman
2024-11-13 22:34 ` [PATCH RFC v3 1/2] KVM: guest_memfd: Convert .free_folio() to .release_folio() Elliot Berman
2024-11-15 10:58 ` David Hildenbrand
2024-11-15 10:58 ` David Hildenbrand
2024-11-15 20:13 ` Elliot Berman
2024-11-18 9:38 ` David Hildenbrand
2024-11-13 22:34 ` [PATCH RFC v3 2/2] mm: guestmem: Convert address_space operations to guestmem library Elliot Berman
2024-11-15 10:31 ` David Hildenbrand [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=1c524181-5518-44bb-9985-d9d12bb92073@redhat.com \
--to=david@redhat.com \
--cc=ackerleytng@google.com \
--cc=akpm@linux-foundation.org \
--cc=hpa@zytor.com \
--cc=jgowans@amazon.com \
--cc=kvm@vger.kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-coco@lists.linux.dev \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=pbonzini@redhat.com \
--cc=quic_eberman@quicinc.com \
--cc=rppt@kernel.org \
--cc=seanjc@google.com \
--cc=tabba@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