| commit | 6f1f67989268ca9df9bdf0322734a77f60183304 | [log] [tgz] |
|---|---|---|
| author | Scott Haseley <shaseley@chromium.org> | Fri Mar 17 20:54:36 2023 |
| committer | Chromium LUCI CQ <chromium-scoped@luci-project-accounts.iam.gserviceaccount.com> | Fri Mar 17 20:54:36 2023 |
| tree | 6bac1c7c5473bf7ae9a2fd8983d738dbbd468edd | |
| parent | db817ff8f2372543b52dc0e10d29b5f52c3bfbf0 [diff] |
Scheduling APIs: Implement scheduler.yield() prototype (part 2: inherit)
This CL implements the scheduler.yield() "inherit" option:
- Signal selection: GetTaskSignalFromOptions() is updated to take
inheritance into account. If either the signal or priority options
are to inherit, the inherited signal is retrieved from V8 and used
in the computation:
- signal: "inherit", priority: unset - use the inherited signal
if there is one, otherwise default priority.
- signal: "inherit", priority: fixed - create a composite signal
from the inherited signal and fixed priority. If the inherited
signal is null, just use a fixed priority signal.
- signal: unset, priority: "inherit" - if there's nothing to
inherit use the default priority; if the inherited signal has
fixed priority and can't abort, use that; otherwise create a
new composite signal.
- DOMTask is updated to support continuation, passing its signal
when creating a task scope (main thread). For workers, DOMTask
will set the continuation preserved embedder data manually before
running the task.
- WPT tests are added and modified to cover the "inherit" option.
Bug: 979020
Change-Id: Ia9776b9292d70636e2b1eea191e9c09b1809fa84
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4326152
Commit-Queue: Scott Haseley <shaseley@chromium.org>
Reviewed-by: Nate Chapin <japhet@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1118868}
Chromium is an open-source browser project that aims to build a safer, faster, and more stable way for all users to experience the web.
The project's web site is https://www.chromium.org.
To check out the source code locally, don't use git clone! Instead, follow the instructions on how to get the code.
Documentation in the source is rooted in docs/README.md.
Learn how to Get Around the Chromium Source Code Directory Structure .
For historical reasons, there are some small top level directories. Now the guidance is that new top level directories are for product (e.g. Chrome, Android WebView, Ash). Even if these products have multiple executables, the code should be in subdirectories of the product.
If you found a bug, please file it at https://crbug.com/new.