Skip to content
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

[GR-18163] Call unblock functions using JNI in CExtInterrupter #3385

Merged
merged 2 commits into from
Jan 15, 2024

Conversation

graalvmbot
Copy link
Collaborator

@graalvmbot graalvmbot commented Jan 12, 2024

* We cannot enter TruffleContext on a system thread, so that leaves us with two options:
  * Calling the unblock function with JNI, and expect the unblock function does not call back to Ruby (not the case for all unblock functions I saw).
  * Calling the unblock function on a new Ruby Thread per context and communicate via a queue, but this seems very high overhead for every guest safepoint.
* Fixes #3013
@graalvmbot graalvmbot force-pushed the bd/system-thread-cext-interrupter-jni branch from dc18cb2 to 6bbd0de Compare January 12, 2024 16:16
@graalvmbot graalvmbot closed this Jan 15, 2024
@graalvmbot graalvmbot merged commit 44cf286 into master Jan 15, 2024
1 check passed
@graalvmbot graalvmbot deleted the bd/system-thread-cext-interrupter-jni branch January 15, 2024 20:09
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
OCA Verified All contributors have signed the Oracle Contributor Agreement.
Projects
None yet
2 participants