We should defer it to 17.04 as new interface is queued in linux-next as
part of v4.9
** Description changed:
Memory Protection Keys for Userspace (PKU aka PKEYs) is a Skylake-SP server
feature that 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
protectionsfrom 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.
HW: Purley
Upstream status:
v4.6 kernel implement basic and execute-only support
- v4.8 kernel will have new interface
+ v4.9 kernel will have new interface
** Changed in: linux (Ubuntu)
Status: Fix Released => New
** Changed in: intel
Status: Fix Released => New
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1591804
Title:
[Feature] Purley: Memory Protection Keys
Status in intel:
New
Status in linux package in Ubuntu:
Incomplete
Bug description:
Memory Protection Keys for Userspace (PKU aka PKEYs) is a Skylake-SP server
feature that 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
protectionsfrom 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.
HW: Purley
Upstream status:
v4.6 kernel implement basic and execute-only support
v4.9 kernel will have new interface
To manage notifications about this bug go to:
https://bugs.launchpad.net/intel/+bug/1591804/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
