| #
99387274 |
|
23-Jul-2018 |
George Kulakowski <kulakowski@google.com> |
[docs][syscalls] Add TODOs about documenting system call rights
ZX-2399 #comment
Test: no functional change
Change-Id: I1f285c677e2444fcf1d720d7ecbd9f490c303962
|
| #
adffbe82 |
|
23-Oct-2017 |
George Kulakowski <kulakowski@google.com> |
[futex] Mark futex paramaters as IN only
Change-Id: I37a626cbd467eeccb4872b39d02d2b5e50289e45
|
| #
f3e2126c |
|
12-Sep-2017 |
Roland McGrath <mcgrathr@google.com> |
[zx] Magenta -> Zircon
The Great Renaming is here!
Change-Id: I3229bdeb2a3d0e40fb4db6fec8ca7d971fbffb94
|
| #
869aa6a1 |
|
14-Jun-2017 |
Todd Eisenberger <teisenbe@google.com> |
[runtime][threads] Rewrite mxr_thread_t join/exit logic
There were previously races when a thread would exit while another
thread was trying to join it. The primary fix is to add an additional
family of states indicating exiting is in progress.
The two big cases that need to be considered are:
- Unjoined thread is exiting while another is joining it.
- Unjoined thread is exiting while another is detaching it.
MG-846 #done
Change-Id: Ib6296d81de76c4d8f10c5a6d88e7159aee04e224
|
| #
52a93d36 |
|
24-Feb-2017 |
Roland McGrath <mcgrathr@google.com> |
[ulib][magenta][runtime][musl] Don't use kernel resources for dead threads
A joinable thread that has exited does not need to keep a kernel
thread object alive via its thread handle. Only the memory for
the thread descriptor needs to stick around. By using a futex
rather than an object signal, joins of threads that have already
exited can complete with no system calls.
Change-Id: I2e3eec95e2cf6897ecd3ce31205bc6b018ad40c9
|