summaryrefslogtreecommitdiffstats
path: root/security
diff options
context:
space:
mode:
authorSam bobroff <sam.bobroff@au1.ibm.com>2015-06-12 11:06:32 +1000
committerMichael Ellerman <mpe@ellerman.id.au>2015-06-19 17:10:28 +1000
commitb4b56f9ecab40f3b4ef53e130c9f6663be491894 (patch)
treefb469b542c15a246790eca454d405bef3dc2c227 /security
parentb5926430dfa07d17e5d768c16b0d81c13a793f7c (diff)
downloadlinux-b4b56f9ecab40f3b4ef53e130c9f6663be491894.tar.gz
linux-b4b56f9ecab40f3b4ef53e130c9f6663be491894.tar.bz2
linux-b4b56f9ecab40f3b4ef53e130c9f6663be491894.zip
powerpc/tm: Abort syscalls in active transactions
This patch changes the syscall handler to doom (tabort) active transactions when a syscall is made and return very early without performing the syscall and keeping side effects to a minimum (no CPU accounting or system call tracing is performed). Also included is a new HWCAP2 bit, PPC_FEATURE2_HTM_NOSC, to indicate this behaviour to userspace. Currently, the system call instruction automatically suspends an active transaction which causes side effects to persist when an active transaction fails. This does change the kernel's behaviour, but in a way that was documented as unsupported. It doesn't reduce functionality as syscalls will still be performed after tsuspend; it just requires that the transaction be explicitly suspended. It also provides a consistent interface and makes the behaviour of user code substantially the same across powerpc and platforms that do not support suspended transactions (e.g. x86 and s390). Performance measurements using http://ozlabs.org/~anton/junkcode/null_syscall.c indicate the cost of a normal (non-aborted) system call increases by about 0.25%. Signed-off-by: Sam Bobroff <sam.bobroff@au1.ibm.com> Signed-off-by: Michael Ellerman <mpe@ellerman.id.au>
Diffstat (limited to 'security')
0 files changed, 0 insertions, 0 deletions