Re: [RFC PATCH v4 1/5] glibc: Perform rseq(2) registration at nptl init and thread creation

From: Rich Felker
Date: Thu Nov 22 2018 - 09:36:56 EST

Next message: Phil Edworthy: "RE: [PATCH] pinctrl: rzn1: Fix check for used MDIO bus"
Previous message: Frank Lee: "Re: [PATCH] clocksource/drivers/integrator-ap: add of_node_put()"
In reply to: Mathieu Desnoyers: "[RFC PATCH v4 2/5] glibc: sched_getcpu(): use rseq cpu_id TLS on Linux"
Next in thread: Mathieu Desnoyers: "Re: [RFC PATCH v4 1/5] glibc: Perform rseq(2) registration at nptl init and thread creation"
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

On Wed, Nov 21, 2018 at 01:39:32PM -0500, Mathieu Desnoyers wrote:
> Register rseq(2) TLS for each thread (including main), and unregister
> for each thread (excluding main). "rseq" stands for Restartable
> Sequences.

Maybe I'm missing something obvious, but "unregister" does not seem to
be a meaningful operation. Can you clarify what it's for?

Rich

Next message: Phil Edworthy: "RE: [PATCH] pinctrl: rzn1: Fix check for used MDIO bus"
Previous message: Frank Lee: "Re: [PATCH] clocksource/drivers/integrator-ap: add of_node_put()"
In reply to: Mathieu Desnoyers: "[RFC PATCH v4 2/5] glibc: sched_getcpu(): use rseq cpu_id TLS on Linux"
Next in thread: Mathieu Desnoyers: "Re: [RFC PATCH v4 1/5] glibc: Perform rseq(2) registration at nptl init and thread creation"
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]