| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Message-ID: <535AF2E9.1000005@redhat.com> Date: Sat, 26 Apr 2014 00:42:33 +0100 From: Pedro Alves <palves@...hat.com> To: Anshuman Khandual <khandual@...ux.vnet.ibm.com> CC: linuxppc-dev@...abs.org, linux-kernel@...r.kernel.org, avagin@...nvz.org, oleg@...hat.com, mikey@...ling.org, benh@...nel.crashing.org Subject: Re: [PATCH 2/3] powerpc, ptrace: Add new ptrace request macros for transactional memory On 04/02/2014 08:02 AM, Anshuman Khandual wrote: > This patch adds following new sets of ptrace request macros for transactional > memory expanding the existing ptrace ABI on PowerPC. > > /* TM special purpose registers */ > PTRACE_GETTM_SPRREGS > PTRACE_SETTM_SPRREGS > > /* TM checkpointed GPR registers */ > PTRACE_GETTM_CGPRREGS > PTRACE_SETTM_CGPRREGS > > /* TM checkpointed FPR registers */ > PTRACE_GETTM_CFPRREGS > PTRACE_SETTM_CFPRREGS > > /* TM checkpointed VMX registers */ > PTRACE_GETTM_CVMXREGS > PTRACE_SETTM_CVMXREGS Urgh, we're _still_ adding specialized register specific calls? Why aren't these exported as new register sets, accessible through PTRACE_GETREGSET / PTRACE_SETREGSET? That's supposed to be the Modern Way to do things. -- Pedro Alves -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists