No description
7d02ecdbb4
It was always set, but not always cleared, when talking to asynchronous drivers. This could cause erratic behavior upon a driver crash. Normally, a worker thread's w_task field is set when it's about to communicate with a driver or FS. Then upon receiving a reply we can do sanity checks (that the thread we want to wake up was actually waiting for a reply). Also, when a driver/FS crashes, we can identify which worker threads were talking to the crashed endpoint and handle the error gracefully. Asynchronous drivers are a bit special, though. In most cases, the sender of the request is not interested in the reply (the sender was suspended and only wants to know whether the request was successfully caried out or not). However, the open request is special, as the reply carries information needed by the sender. This is the only request where a worker thread actually yields and waits for the result. This is also the only case where we're interested in setting w_task for asynchronous drivers. Change-Id: Ia1ce2747937df376122b5e13b6a069de27fcc379 |
||
---|---|---|
benchmarks | ||
bin | ||
commands | ||
common | ||
dist/nvi | ||
distrib | ||
docs | ||
drivers | ||
etc | ||
external | ||
gnu | ||
include | ||
kernel | ||
lib | ||
libexec | ||
man | ||
releasetools | ||
sbin | ||
servers | ||
share | ||
sys | ||
test | ||
tests | ||
tools | ||
usr.bin | ||
usr.sbin | ||
.gitignore | ||
.gitreview | ||
build.sh | ||
LICENSE | ||
Makefile |