Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.kernel > #1340120

[RFC][PATCH 1/7] x86, pkeys: Documentation

Show all headers | View raw

From: Dave Hansen <dave.hansen@linux.intel.com>

Give a high-level overview of Protection Keys from a hardware
perspective, as well as some description since we referred to
this from the Kconfig text.

Signed-off-by: Dave Hansen <dave.hansen@linux.intel.com>
---

 b/Documentation/x86/protection-keys.txt |   28 ++++++++++++++++++++++++++++
 1 file changed, 28 insertions(+)

diff -puN /dev/null Documentation/x86/protection-keys.txt
--- /dev/null	2015-12-10 15:28:13.322405854 -0800
+++ b/Documentation/x86/protection-keys.txt	2016-02-22 17:09:22.811272277 -0800
@@ -0,0 +1,28 @@
+Memory Protection Keys for User pages is a CPU feature which will
+first appear on Skylake Servers, but will also be supported on
+future non-server parts.
+
+Memory Protection Keys provides a mechanism for enforcing page-based
+protections, but without requiring modification of the page tables
+when an application changes protection domains.  It works by
+dedicating 4 previously ignored bits in each page table entry to a
+"protection key", giving 16 possible keys.
+
+There is also a new user-accessible register (PKRU) with two separate
+bits (Access Disable and Write Disable) for each key.  Being a CPU
+register, PKRU is inherently thread-local, potentially giving each
+thread a different set of protections from every other thread.
+
+There are two new instructions (RDPKRU/WRPKRU) for reading and writing
+to the new register.  The feature is only available in 64-bit mode,
+even though there is theoretically space in the PAE PTEs.  These
+permissions are enforced on data access only and have no effect on
+instruction fetches.
+
+=========================== Config Option ===========================
+
+This config option adds approximately 1.5kb of text. and 50 bytes of
+data to the executable.  A workload which does large O_DIRECT reads
+of holes in XFS files was run to exercise get_user_pages_fast().  No
+performance delta was observed with the config option
+enabled or disabled.
_

Back to linux.kernel | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread

Thread

[RFC][PATCH 0/7] System Calls for Memory Protection Keys Dave Hansen <dave@sr71.net> - 2016-02-23 02:20 +0100
  [RFC][PATCH 3/7] x86, pkeys: make mprotect_key() mask off additional vm_flags Dave Hansen <dave@sr71.net> - 2016-02-23 02:20 +0100
  [RFC][PATCH 1/7] x86, pkeys: Documentation Dave Hansen <dave@sr71.net> - 2016-02-23 02:20 +0100
  [RFC][PATCH 6/7] x86, pkeys: add pkey set/get syscalls Dave Hansen <dave@sr71.net> - 2016-02-23 02:20 +0100
    Re: [RFC][PATCH 6/7] x86, pkeys: add pkey set/get syscalls Ingo Molnar <mingo@kernel.org> - 2016-02-23 07:50 +0100
  [RFC][PATCH 4/7] x86: wire up mprotect_key() system call Dave Hansen <dave@sr71.net> - 2016-02-23 02:20 +0100
  [RFC][PATCH 7/7] pkeys: add details of system call use to Documentation/ Dave Hansen <dave@sr71.net> - 2016-02-23 02:20 +0100
    Re: [RFC][PATCH 7/7] pkeys: add details of system call use to  Documentation/ Ingo Molnar <mingo@kernel.org> - 2016-02-23 07:40 +0100
  [RFC][PATCH 2/7] mm: implement new pkey_mprotect() system call Dave Hansen <dave@sr71.net> - 2016-02-23 02:20 +0100
  [RFC][PATCH 5/7] x86, pkeys: allocation/free syscalls Dave Hansen <dave@sr71.net> - 2016-02-23 02:20 +0100
  Re: [RFC][PATCH 0/7] System Calls for Memory Protection Keys "Michael Kerrisk (man-pages)" <mtk.manpages@gmail.com> - 2016-03-03 09:20 +0100
    Re: [RFC][PATCH 0/7] System Calls for Memory Protection Keys Dave Hansen <dave@sr71.net> - 2016-03-04 00:50 +0100

csiph-web