ruby.git/thread_none.c, branch v3_2_11 The Ruby Programming Language [wasm] Scan machine stack based on `ec->machine.stack_{start,end}` 2022-11-05T20:03:21+00:00 Yuta Saito kateinoigakukun@gmail.com 2022-11-05T16:10:35+00:00 3a6cdeda89280ade714f158830acee88fb36306d fiber machine stack is placed outside of C stack allocated by wasm-ld, so highest stack address recorded by `rb_wasm_record_stack_base` is invalid when running on non-main fiber. Therefore, we should scan `stack_{start,end}` which always point a valid stack range in any context. 
fiber machine stack is placed outside of C stack allocated by wasm-ld,
so highest stack address recorded by `rb_wasm_record_stack_base` is
invalid when running on non-main fiber.
Therefore, we should scan `stack_{start,end}` which always point a valid
stack range in any context.
GVL Instrumentation: remove the EXITED count assertion 2022-07-13T17:39:31+00:00 Jean Boussier jean.boussier@gmail.com 2022-07-13T16:49:27+00:00 664c23db79dd0d500a834ef0ec8da443d95ddfd6 It's very flaky for some unknown reason. Something we have an extra EXITED event. I suspect some other test is causing this. 
It's very flaky for some unknown reason. Something we have
an extra EXITED event. I suspect some other test is causing this.
GVL Instrumentation API: add STARTED and EXITED events 2022-06-17T07:08:26+00:00 Jean Boussier jean.boussier@gmail.com 2022-06-15T12:37:41+00:00 b6c1e1158d71b533b255ae7a2731598455918071 [Feature #18339] After experimenting with the initial version of the API I figured there is a need for an exit event to cleanup instrumentation data. e.g. if you record data in a {thread_id -> data} table, you need to free associated data when a thread goes away. 
[Feature #18339]

After experimenting with the initial version of the API I figured there is a need
for an exit event to cleanup instrumentation data. e.g. if you record data in a
{thread_id -> data} table, you need to free associated data when a thread goes away.
remove `DEBUG_OUT()` macro 2022-05-24T07:28:07+00:00 Koichi Sasada ko1@atdot.net 2022-05-24T06:06:30+00:00 62e08d4b844a3f4f7a6dadc6083cd0585485931b This macro is no longer used ([GH-5933]). 
This macro is no longer used ([GH-5933]).
remove `NON_SCALAR_THREAD_ID` support 2022-05-24T01:06:51+00:00 Koichi Sasada ko1@atdot.net 2022-05-23T17:56:59+00:00 d9984f39d32f4cd692a35f4d803f7754ea262805 `NON_SCALAR_THREAD_ID` shows `pthread_t` is non-scalar (non-pointer) and only s390x is known platform. However, the supporting code is very complex and it is only used for deubg print information. So this patch removes the support of `NON_SCALAR_THREAD_ID` and make the code simple. 
`NON_SCALAR_THREAD_ID` shows `pthread_t` is non-scalar (non-pointer)
and only s390x is known platform. However, the supporting code is
very complex and it is only used for deubg print information.

So this patch removes the support of `NON_SCALAR_THREAD_ID`
and make the code simple.
introduce struct `rb_native_thread` 2022-04-22T18:08:27+00:00 Koichi Sasada ko1@atdot.net 2022-04-22T12:19:03+00:00 03d21a4fb099da7c52e6591e17704c297871b7db `rb_thread_t` contained `native_thread_data_t` to represent thread implementation dependent data. This patch separates them and rename it `rb_native_thread` and point it from `rb_thraed_t`. Now, 1 Ruby thread (`rb_thread_t`) has 1 native thread (`rb_native_thread`). 
`rb_thread_t` contained `native_thread_data_t` to represent
thread implementation dependent data. This patch separates
them and rename it `rb_native_thread` and point it from
`rb_thraed_t`.

Now, 1 Ruby thread (`rb_thread_t`) has 1 native thread (`rb_native_thread`).
rename thread internal naming 2022-04-21T22:54:09+00:00 Koichi Sasada ko1@atdot.net 2022-04-16T18:40:23+00:00 1c4fc0241d125879e1e5169f267f26637772f3a7 Now GVL is not process *Global* so this patch try to use another words. * `rb_global_vm_lock_t` -> `struct rb_thread_sched` * `gvl->owner` -> `sched->running` * `gvl->waitq` -> `sched->readyq` * `rb_gvl_init` -> `rb_thread_sched_init` * `gvl_destroy` -> `rb_thread_sched_destroy` * `gvl_acquire` -> `thread_sched_to_running` # waiting -> ready -> running * `gvl_release` -> `thread_sched_to_waiting` # running -> waiting * `gvl_yield` -> `thread_sched_yield` * `GVL_UNLOCK_BEGIN` -> `THREAD_BLOCKING_BEGIN` * `GVL_UNLOCK_END` -> `THREAD_BLOCKING_END` * removed * `rb_ractor_gvl` * `rb_vm_gvl_destroy` (not used) There are GVL functions such as `rb_thread_call_without_gvl()` yet but I don't have good name to replace them. Maybe GVL stands for "Greate Valuable Lock" or something like that. 
Now GVL is not process *Global* so this patch try to use
another words.

* `rb_global_vm_lock_t` -> `struct rb_thread_sched`
  * `gvl->owner` -> `sched->running`
  * `gvl->waitq` -> `sched->readyq`
* `rb_gvl_init` -> `rb_thread_sched_init`
* `gvl_destroy` -> `rb_thread_sched_destroy`
* `gvl_acquire` -> `thread_sched_to_running` # waiting -> ready -> running
* `gvl_release` -> `thread_sched_to_waiting` # running -> waiting
* `gvl_yield`   -> `thread_sched_yield`
* `GVL_UNLOCK_BEGIN` -> `THREAD_BLOCKING_BEGIN`
* `GVL_UNLOCK_END` -> `THREAD_BLOCKING_END`

* removed
  * `rb_ractor_gvl`
  * `rb_vm_gvl_destroy` (not used)

There are GVL functions such as `rb_thread_call_without_gvl()` yet
but I don't have good name to replace them. Maybe GVL stands for
"Greate Valuable Lock" or something like that.
[wasm] add no thread variant for freestanding environment 2022-01-19T02:19:06+00:00 Yuta Saito kateinoigakukun@gmail.com 2022-01-15T15:37:54+00:00 420622b5a793186dfa533e7702913fd5e4764e0f This implementation does nothing around preemptive context switching because there is no native thread. 
This implementation does nothing around preemptive context switching
because there is no native thread.