Hi Mathieu,
Yep, was going to say, that the patch set has evolved rather
notably. Good job.
Did you manage to push the required changes to glibc or do you maintain your own user space rseq lib?
-ss
Did you manage to push the required changes to glibc or do you maintain your own user space rseq lib?
-ss
I am concerned about providing a librseq that handles rseq registration for early adopters though, because I don't want projects to eventually end up conflicting with future glibc versions. Once we settled how glibc will expose the symbol and register it, I will try to provide a helper library which exposes this symbol and allow performing explicit rseq registration in a way that won't conflict with future glibc versions.
Sounds very reasonable.
So at this point, as far as I understand it, FB and Google carry in-house rseq kernel and user space patches. Right? Are they on board with the mainline rseq? Will FB support rseq in jemalloc any time soon?
-ss
I don't know whether Google will ever want to swap from their in house rseq implementation to the upstream Linux rseq, use both ABIs for a transition period, or simply keep using their own in-house rseq.