From: "Manwaring, Derek" <derekmn@amazon.com>
To: David Woodhouse <dwmw2@infradead.org>,
David Matlack <dmatlack@google.com>,
Brendan Jackman <jackmanb@google.com>,
"tabba@google.com" <tabba@google.com>,
"qperret@google.com" <qperret@google.com>,
"jason.cj.chen@intel.com" <jason.cj.chen@intel.com>
Cc: "Gowans, James" <jgowans@amazon.com>,
"seanjc@google.com" <seanjc@google.com>,
"akpm@linux-foundation.org" <akpm@linux-foundation.org>,
"Roy, Patrick" <roypat@amazon.co.uk>,
"chao.p.peng@linux.intel.com" <chao.p.peng@linux.intel.com>,
"rppt@kernel.org" <rppt@kernel.org>,
"pbonzini@redhat.com" <pbonzini@redhat.com>,
"Kalyazin, Nikita" <kalyazin@amazon.co.uk>,
"lstoakes@gmail.com" <lstoakes@gmail.com>,
"Liam.Howlett@oracle.com" <Liam.Howlett@oracle.com>,
"linux-mm@kvack.org" <linux-mm@kvack.org>,
"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>,
"kirill.shutemov@linux.intel.com"
<kirill.shutemov@linux.intel.com>,
"vbabka@suse.cz" <vbabka@suse.cz>,
"mst@redhat.com" <mst@redhat.com>,
"somlo@cmu.edu" <somlo@cmu.edu>, "Graf (AWS),
Alexander" <graf@amazon.de>,
"kvm@vger.kernel.org" <kvm@vger.kernel.org>,
"linux-coco@lists.linux.dev" <linux-coco@lists.linux.dev>,
"kvmarm@lists.linux.dev" <kvmarm@lists.linux.dev>,
"kvmarm@lists.cs.columbia.edu" <kvmarm@lists.cs.columbia.edu>
Subject: Re: Unmapping KVM Guest Memory from Host Kernel
Date: Fri, 8 Mar 2024 21:05:19 +0000 [thread overview]
Message-ID: <335E21FA-7F1E-4540-8A70-01A63D8C72FA@amazon.com> (raw)
On 2024-03-08 at 10:46-0700, David Woodhouse wrote:
> On Fri, 2024-03-08 at 09:35 -0800, David Matlack wrote:
> > I think what James is looking for (and what we are also interested
> > in), is _eliminating_ the ability to access guest memory from the
> > direct map entirely. And in general, eliminate the ability to access
> > guest memory in as many ways as possible.
>
> Well, pKVM does that...
Yes we've been looking at pKVM and it accomplishes a lot of what we're trying
to do. Our initial inclination is that we want to stick with VHE for the lower
overhead. We also want flexibility across server parts, so we would need to
get pKVM working on Intel & AMD if we went this route.
Certainly there are advantages of pKVM on the perf side like the in-place
memory sharing rather than copying as well as on the security side by simply
reducing the TCB. I'd be interested to hear others' thoughts on pKVM vs
memfd_secret or general ASI.
Derek
next reply other threads:[~2024-03-08 21:05 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-08 21:05 Manwaring, Derek [this message]
2024-03-11 9:26 ` Unmapping KVM Guest Memory from Host Kernel Fuad Tabba
2024-03-11 9:29 ` Fuad Tabba
[not found] <AQHacXBJeX10YUH0O0SiQBg1zQLaEw==>
2024-03-08 15:50 ` Gowans, James
2024-03-08 16:25 ` Brendan Jackman
2024-03-08 17:35 ` David Matlack
2024-03-08 17:45 ` David Woodhouse
2024-03-08 22:47 ` Sean Christopherson
2024-03-09 2:45 ` Manwaring, Derek
2024-03-18 14:11 ` Brendan Jackman
2024-03-08 23:22 ` Sean Christopherson
2024-03-09 11:14 ` Mike Rapoport
2024-05-13 10:31 ` Patrick Roy
2024-05-13 15:39 ` Sean Christopherson
2024-05-13 16:01 ` Gowans, James
2024-05-13 17:09 ` Sean Christopherson
2024-05-13 19:43 ` Gowans, James
2024-05-13 20:36 ` Sean Christopherson
2024-05-13 22:01 ` Manwaring, Derek
2024-03-14 21:45 ` Manwaring, Derek
2024-03-09 5:01 ` Matthew Wilcox
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=335E21FA-7F1E-4540-8A70-01A63D8C72FA@amazon.com \
--to=derekmn@amazon.com \
--cc=Liam.Howlett@oracle.com \
--cc=akpm@linux-foundation.org \
--cc=chao.p.peng@linux.intel.com \
--cc=dmatlack@google.com \
--cc=dwmw2@infradead.org \
--cc=graf@amazon.de \
--cc=jackmanb@google.com \
--cc=jason.cj.chen@intel.com \
--cc=jgowans@amazon.com \
--cc=kalyazin@amazon.co.uk \
--cc=kirill.shutemov@linux.intel.com \
--cc=kvm@vger.kernel.org \
--cc=kvmarm@lists.cs.columbia.edu \
--cc=kvmarm@lists.linux.dev \
--cc=linux-coco@lists.linux.dev \
--cc=linux-mm@kvack.org \
--cc=lstoakes@gmail.com \
--cc=mst@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=qperret@google.com \
--cc=roypat@amazon.co.uk \
--cc=rppt@kernel.org \
--cc=seanjc@google.com \
--cc=somlo@cmu.edu \
--cc=tabba@google.com \
--cc=vbabka@suse.cz \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).