|
|
|
|
|
by senozhatsky
2925 days ago
|
|
> I am concerned about providing a librseq that handles rseq registration for early adopters though 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.