-
Notifications
You must be signed in to change notification settings - Fork 396
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Only unblock an asynchronous signal if it is used #4554
Conversation
cb244e7
to
872a968
Compare
872a968
to
ce1511f
Compare
Performance ResultsCompile the micro-benchmark
Run the micro-benchmark
Elapsed time
Currently, Each iteration of the micro-benchmark invokes Micro-benchmark (benchmark_pthread_sigmask.c):
|
Initial testing looks good. Awaiting for test results from customer's nightly build. Code is ready-to-be-reviewed. But it should not be merged until test results from customer's nightly build are received. |
The failures have been resolved in the customer's nightly build. So, this pull request can be merged after the code-review. |
@genie-omr build all |
1 similar comment
@genie-omr build all |
FYI: I'm manually stopping some tests for this PR that look like they're hanging. |
ce1511f
to
792edef
Compare
@rwy0717 Unrelated errors were happening in the CI build jobs. I have rebased my branch. Can you please retry the builds? |
@genie-omr build all |
Currently, all supported asynchronous signals are unblocked during startup. A signal is unblocked even when a signal handler is not installed for it. This conflicts with an OMR consumer, who wants to block a set of signals. The OMR consumer blocks a set of signals but the OMR signal library unblocks those signals at startup. OMR signal library should only unblock a signal if a signal handler is registered for it. In other words, a signal should not be unblocked if it is not used i.e. a signal handler is not registered for it. Fixes: eclipse-openj9/openj9#7749 Signed-off-by: Babneet Singh <sbabneet@ca.ibm.com>
792edef
to
717082e
Compare
@genie-omr build all |
@genie-omr build x32linux |
Currently, all supported asynchronous signals are unblocked during
startup. A signal is unblocked even when a signal handler is not
installed for it. This conflicts with an OMR consumer, who wants to
block a set of signals. The OMR consumer blocks a set of signals but the
OMR signal library unblocks those signals at startup. OMR signal library
should only unblock a signal if a signal handler is registered for it.
In other words, a signal should not be unblocked if it is not used i.e.
a signal handler is not registered for it.
Related:
Signed-off-by: Babneet Singh sbabneet@ca.ibm.com