[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <alpine.DEB.2.21.1910301205001.14416@www.lameter.com>
Date: Wed, 30 Oct 2019 12:09:23 +0000 (UTC)
From: Christopher Lameter <cl@...ux.com>
To: Mike Rapoport <rppt@...nel.org>
cc: "Kirill A. Shutemov" <kirill@...temov.name>,
linux-kernel@...r.kernel.org,
Alexey Dobriyan <adobriyan@...il.com>,
Andrew Morton <akpm@...ux-foundation.org>,
Andy Lutomirski <luto@...nel.org>,
Arnd Bergmann <arnd@...db.de>, Borislav Petkov <bp@...en8.de>,
Dave Hansen <dave.hansen@...ux.intel.com>,
James Bottomley <jejb@...ux.ibm.com>,
Peter Zijlstra <peterz@...radead.org>,
Steven Rostedt <rostedt@...dmis.org>,
Thomas Gleixner <tglx@...utronix.de>,
Ingo Molnar <mingo@...hat.com>,
"H. Peter Anvin" <hpa@...or.com>, linux-api@...r.kernel.org,
linux-mm@...ck.org, x86@...nel.org,
Mike Rapoport <rppt@...ux.ibm.com>
Subject: Re: [PATCH RFC] mm: add MAP_EXCLUSIVE to create exclusive user
mappings
On Wed, 30 Oct 2019, Mike Rapoport wrote:
> > /dev/securemem or so?
>
> A device driver will need to remove the secure area from the direct map and
> then we back to square one.
We have avoided the need for modifications to kernel core code. And its a
natural thing to treat this like special memory provided by a device
driver.
Powered by blists - more mailing lists