diff options
author | ed <ed@FreeBSD.org> | 2016-10-12 09:17:41 +0000 |
---|---|---|
committer | ed <ed@FreeBSD.org> | 2016-10-12 09:17:41 +0000 |
commit | 7c05d1bcc3ae1e7fdf6581cd249a5b0de28fd5c2 (patch) | |
tree | 7ab7108cb2dabd10dfe3a6fdea36e435803075d1 /contrib/libarchive/tar/test/test_option_U_upper.c | |
parent | 0febaaa5838430d3356cb105ed697d82bbb6397c (diff) | |
download | FreeBSD-src-7c05d1bcc3ae1e7fdf6581cd249a5b0de28fd5c2.zip FreeBSD-src-7c05d1bcc3ae1e7fdf6581cd249a5b0de28fd5c2.tar.gz |
MFC r306162:
Make it possible to safely use TPIDRURW from userspace.
On amd64, arm64 and i386, we have the possibility to switch between TLS
areas in userspace. The nice thing about this is that it makes it easier
to do light-weight threading, if we ever feel like doing that. On armv6,
let's go into the same direction by making it possible to safely use the
TPIDRURW register, which is intended for this purpose.
Clean up the ARMv6 code to remove md_tp entirely. Simply add a dedicated
field to the PCB to hold the value of TPIDRURW across context switches,
like we do for any other register. As userspace currently uses the
read-only TPIDRURO register, simply ensure that we keep both values in
sync where possible. The system calls for modifying the read-only
register will simply write the intended value into both registers, so
that it lazily ends up in the PCB during the next context switch.
Approved by: andrew
Reviewed by: imp
Differential Revision: https://reviews.freebsd.org/D7951
Diffstat (limited to 'contrib/libarchive/tar/test/test_option_U_upper.c')
0 files changed, 0 insertions, 0 deletions