From: "Edgecombe, Rick P" <rick.p.edgecombe@intel.com>
To: "rppt@kernel.org" <rppt@kernel.org>,
"Hansen, Dave" <dave.hansen@intel.com>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"peterz@infradead.org" <peterz@infradead.org>,
"jejb@linux.ibm.com" <jejb@linux.ibm.com>,
"alan@linux.intel.com" <alan@linux.intel.com>,
"tglx@linutronix.de" <tglx@linutronix.de>,
"dave.hansen@linux.intel.com" <dave.hansen@linux.intel.com>,
"linux-api@vger.kernel.org" <linux-api@vger.kernel.org>,
"willy@infradead.org" <willy@infradead.org>,
"linux-mm@kvack.org" <linux-mm@kvack.org>,
"cl@linux.com" <cl@linux.com>,
"akpm@linux-foundation.org" <akpm@linux-foundation.org>,
"Reshetova, Elena" <elena.reshetova@intel.com>,
"tycho@tycho.ws" <tycho@tycho.ws>,
"luto@kernel.org" <luto@kernel.org>,
"kirill@shutemov.name" <kirill@shutemov.name>
Subject: Re: [RFC PATCH] mm: extend memfd with ability to create "secret" memory areas
Date: Tue, 11 Feb 2020 19:52:47 +0000 [thread overview]
Message-ID: <ab0a11ad5fde0cc71a725aac3ea81cc996e35bf1.camel@intel.com> (raw)
In-Reply-To: <20200208173922.GA15879@hump>
On Sat, 2020-02-08 at 19:39 +0200, Mike Rapoport wrote:
> > Do we need to make kmap() work on these?
>
> I don't think we need to make kmap() work on these. The idea is to prevent
> kernel from accessing such memory areas.
For the VM use case, KVM does kmap() guest memory when emulating page table
operations in some cases:
arch/x86/kvm/paging_tmpl.h:FNAME(cmpxchg_gpte).
next prev parent reply other threads:[~2020-02-11 19:52 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-30 16:23 [RFC PATCH] mm: extend memfd with ability to create "secret" memory areas Mike Rapoport
2020-02-06 18:51 ` Dave Hansen
2020-02-08 17:39 ` Mike Rapoport
2020-02-10 8:06 ` Reshetova, Elena
2020-02-11 19:52 ` Edgecombe, Rick P [this message]
2020-02-12 21:10 ` Jonathan Corbet
2020-02-16 6:46 ` Mike Rapoport
2020-08-14 17:46 ` Andy Lutomirski
2020-08-14 18:09 ` Dave Hansen
2020-08-26 16:54 ` Andy Lutomirski
2020-08-26 19:01 ` Florian Weimer
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=ab0a11ad5fde0cc71a725aac3ea81cc996e35bf1.camel@intel.com \
--to=rick.p.edgecombe@intel.com \
--cc=akpm@linux-foundation.org \
--cc=alan@linux.intel.com \
--cc=cl@linux.com \
--cc=dave.hansen@intel.com \
--cc=dave.hansen@linux.intel.com \
--cc=elena.reshetova@intel.com \
--cc=jejb@linux.ibm.com \
--cc=kirill@shutemov.name \
--cc=linux-api@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=luto@kernel.org \
--cc=peterz@infradead.org \
--cc=rppt@kernel.org \
--cc=tglx@linutronix.de \
--cc=tycho@tycho.ws \
--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).