>?????? int rseq(struct rseq * rseq, uint32_t rseq_len, int flags, uint32_t sig);
Really dumb question -- and one I'm sorry to bring up at the last minute. Should we consider making the syscall name something more generic "register_tls_abi"? I'm assuming that if we ever want to use a per-thread userspace/kernel ABI we'll want to use this field given the difficulty of getting adoption of registration, the need to involve glibc, etc. It seems like there could be future use cases of this TLS area that have nothing to do with rseq.
From 1584073814600987930@xxx Tue Nov 14 20:15:12 +0000 2017
X-GM-THRID: 1584073814600987930
X-Gmail-Labels: Inbox,Category Forums,HistoricalUnread