[valgrind] [Bug 405377] Handle new Linux kernel feature: Restartable Sequences ("rseq")

2022-01-26 Thread Tom Hughes
https://bugs.kde.org/show_bug.cgi?id=405377

Tom Hughes  changed:

   What|Removed |Added

 CC||m...@linux.ibm.com

--- Comment #6 from Tom Hughes  ---
*** Bug 449199 has been marked as a duplicate of this bug. ***

-- 
You are receiving this mail because:
You are watching all bug changes.

[valgrind] [Bug 405377] Handle new Linux kernel feature: Restartable Sequences ("rseq")

2021-12-15 Thread Mark Wielaard
https://bugs.kde.org/show_bug.cgi?id=405377

--- Comment #5 from Mark Wielaard  ---
For now I pushed the ENOSYS patch to make sure things just work with the new
glibc.

commit 1024237358f01009fe233cb1294f3b8211304eaa
Author: Mark Wielaard 
Date:   Fri Dec 10 17:41:59 2021 +0100

Implement linux rseq syscall as ENOSYS

This implements rseq for amd64, arm, arm64, ppc32, ppc64,
s390x and x86 linux as ENOSYS (without warning).

glibc will start using rseq to accelerate sched_getcpu, if
available. This would cause a warning from valgrind every
time a new thread is started.

Real rseq (restartable sequences) support is pretty hard, so
for now just explicitly return ENOSYS (just like we do for clone3).

https://sourceware.org/pipermail/libc-alpha/2021-December/133656.html

Leaving this bug open for a real implementation.

-- 
You are receiving this mail because:
You are watching all bug changes.

[valgrind] [Bug 405377] Handle new Linux kernel feature: Restartable Sequences ("rseq")

2021-12-10 Thread Derek Bruening
https://bugs.kde.org/show_bug.cgi?id=405377

--- Comment #4 from Derek Bruening  ---
Updated link for the stale wiki page from the first comment above detailing the
run-twice solution DynamoRIO has been using successfully for years now:
https://dynamorio.org/page_rseq.html

-- 
You are receiving this mail because:
You are watching all bug changes.

[valgrind] [Bug 405377] Handle new Linux kernel feature: Restartable Sequences ("rseq")

2021-12-10 Thread Mark Wielaard
https://bugs.kde.org/show_bug.cgi?id=405377

--- Comment #3 from Mark Wielaard  ---
Created attachment 144436
  --> https://bugs.kde.org/attachment.cgi?id=144436=edit
implement rseq as ENOSYS

-- 
You are receiving this mail because:
You are watching all bug changes.

[valgrind] [Bug 405377] Handle new Linux kernel feature: Restartable Sequences ("rseq")

2021-12-10 Thread Mark Wielaard
https://bugs.kde.org/show_bug.cgi?id=405377

Mark Wielaard  changed:

   What|Removed |Added

 CC||m...@klomp.org
 Status|REPORTED|CONFIRMED
 Ever confirmed|0   |1

--- Comment #2 from Mark Wielaard  ---
glibc will start using rseq:
https://sourceware.org/pipermail/libc-alpha/2021-December/133656.html

If they get an ENOSYS they will simply not use it.
So I propose that for now we "implement" rseq by just returning ENOSYS and not
produce an warning for now.

-- 
You are receiving this mail because:
You are watching all bug changes.

[valgrind] [Bug 405377] Handle new Linux kernel feature: Restartable Sequences ("rseq")

2019-09-17 Thread Derek Bruening
https://bugs.kde.org/show_bug.cgi?id=405377

--- Comment #1 from Derek Bruening  ---
Details on DynamoRIO's "run twice" solution and implementation for the rseq
feature which is now generally available in recent kernels are at
https://github.com/DynamoRIO/dynamorio/wiki/Restartable-Sequences

-- 
You are receiving this mail because:
You are watching all bug changes.

[valgrind] [Bug 405377] Handle new Linux kernel feature: Restartable Sequences ("rseq")

2019-03-12 Thread Hendrik Greving
https://bugs.kde.org/show_bug.cgi?id=405377

Hendrik Greving  changed:

   What|Removed |Added

 CC||hgrev...@google.com

-- 
You are receiving this mail because:
You are watching all bug changes.