|
Revision tags: dev, v36.0.9, v44.0.1, v43.0.2, v36.0.8, v24.0.8, v44.0.0, v43.0.1, v42.0.2, v36.0.7, v24.0.7, v43.0.0, v42.0.1, v41.0.4, v42.0.0, v40.0.4, v36.0.6, v24.0.6, v41.0.3, v41.0.2, v41.0.1, v36.0.5, v40.0.3, v41.0.0, v36.0.4, v39.0.2, v40.0.2 |
|
| #
fae9e6af |
| 08-Jan-2026 |
Joel Dice <[email protected]> |
add missing may-block checks for sync-to-sync guest-to-guest calls (#12282)
* add missing may-block checks for sync-to-sync guest-to-guest calls
Previously, we weren't updating or checking the may-
add missing may-block checks for sync-to-sync guest-to-guest calls (#12282)
* add missing may-block checks for sync-to-sync guest-to-guest calls
Previously, we weren't updating or checking the may-block status of a task
across sync-to-sync, guest-to-guest calls, meaning we were allowing blocking in
cases we shouldn't have.
This fixes that by adding a new `task_may_block` field to `VMComponentContext`,
plus code to update it every time we switch threads or do a sync-to-sync,
guest-to-guest call. We use that field as the source of truth about whether a
blocking operation is permitted.
I've updated various tests to match, and Luke has an item on his to-do list to
add sad-path coverage for various cases to the upstream `component-model` test
suite.
* address review feedback and fix component_instance_size_limit test
* remove `TaskMayBlock` type per review feedback
* bless disas tests
show more ...
|
|
Revision tags: v40.0.1, v40.0.0, v39.0.1, v39.0.0, v38.0.4, v37.0.3, v36.0.3, v24.0.5, v38.0.3, v38.0.2, v38.0.1 |
|
| #
b242f5a6 |
| 15-Oct-2025 |
Alex Crichton <[email protected]> |
Reorganize component model wast testing (#11818)
* Move all `*.wast` tests under `tests/misc_testsuite/component-model`,
e.g. move` component-model-async` to `component-model/async`.
* Split testi
Reorganize component model wast testing (#11818)
* Move all `*.wast` tests under `tests/misc_testsuite/component-model`,
e.g. move` component-model-async` to `component-model/async`.
* Split testing of `component-model-{stackful,async-builtins}` into
separate tests instead of intermingling it with all other tests.
This is done to in theory make this easier to upstream into the
component model repository itself by having a cleaner split by feature
rather than being a pure reflection of historical development.
show more ...
|