[PATCH 0/6] [RFCv4] add manpages for Memory Protection Keys · Dave Hansen <hidden> · 2016-06-08
[PATCH 1/6] pkey.7: New page with overview of Memory Protection Keys · Dave Hansen <hidden> · 2016-06-08
Re: [PATCH 1/6] pkey.7: New page with overview of Memory Protection Keys · Florian Weimer <hidden> · 2016-10-12
[PATCH 2/6] mprotect.2: add pkey_mprotect() syscall · Dave Hansen <hidden> · 2016-06-08
[PATCH 3/6] pkey_alloc.2: New page describing protection key allocation and free · Dave Hansen <hidden> · 2016-06-08
[PATCH 4/6] pkey_get.2: New page desribing pkey rights manipulation syscalls · Dave Hansen <hidden> · 2016-06-08
[PATCH 5/6] sigaction.2: describe siginfo changes from pkey-induced signals · Dave Hansen <hidden> · 2016-06-08
[PATCH 6/6] proc.5: describe new ProtectionKey smaps field · Dave Hansen <hidden> · 2016-06-08

Re: [PATCH 1/6] pkey.7: New page with overview of Memory Protection Keys

From: Florian Weimer <hidden>
Date: 2016-10-12 08:41:17
Also in: linux-man

On 06/08/2016 07:34 PM, Dave Hansen wrote:

+To use this feature, the processor must support it, and Linux
+must contain support for the feature on a given processor.
+As of early 2016 only future Intel x86 processors are supported,
+and this hardware supports 16 protection keys in each process.
+However, pkey 0 is used as the default key, so a maximum of 15
+are available for actual application use.

How can we reserve pkeys for use in system libraries?

Thanks,
Florian
--
To unsubscribe from this list: send the line "unsubscribe linux-man" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

`h`	back out one level
`j`	next message in thread
`k`	previous message in thread
`l`	drill in
`Esc`	close help / fold thread tree
`?`	toggle this help