[zircon][scheduler] Make yielding equivalent to running out timeslice

In pathological cases where threads were spin-yielding, bottoming out
the deboost at 0 meant that the yielding threads could be permanently
stuck at higher priority than another thread doing work (which would get
a deboost (below 0). In the right set of circumstances, this could
result in the work thread never getting to run again. See also
https://crbug.com/959245.

Test added to `k ut thread`.

ZX-4410 #done

Change-Id: I2306a9c94fd3d4fda88a79938b66527f9dd26cbd
2 files changed
tree: 4d08acbd104b9b026db3e0a2a07bf428eb850b11
  1. boards/
  2. build/
  3. buildtools/
  4. bundles/
  5. docs/
  6. examples/
  7. garnet/
  8. peridot/
  9. products/
  10. scripts/
  11. sdk/
  12. src/
  13. third_party/
  14. tools/
  15. zircon/
  16. .clang-format
  17. .clang-tidy
  18. .dir-locals.el
  19. .gitattributes
  20. .gitignore
  21. .gn
  22. AUTHORS
  23. BUILD.gn
  24. CODE_OF_CONDUCT.md
  25. CONTRIBUTING.md
  26. LICENSE
  27. OWNERS
  28. PATENTS
  29. README.md
  30. rustfmt.toml
README.md

Fuchsia

Pink + Purple == Fuchsia (a new operating system)

What is Fuchsia?

Fuchsia is a modular, capability-based operating system. Fuchsia runs on modern 64-bit Intel and ARM processors.

Fuchsia is an open source project with a code of conduct that we expect everyone who interacts with the project to respect.

How can I build and run Fuchsia?

See Getting Started.

Where can I learn more about Fuchsia?

See the documentation.