summaryrefslogtreecommitdiffstats
path: root/README
diff options
context:
space:
mode:
authorjhb <jhb@FreeBSD.org>2008-08-07 21:00:13 +0000
committerjhb <jhb@FreeBSD.org>2008-08-07 21:00:13 +0000
commite306c86e1b6376905ae8d21091509cbe1f61fba8 (patch)
tree5341583d2eecb5e89baa3cba762d2f3739e4856a /README
parent9f16e510b9a765d8caed7f31ebaf16b600540db4 (diff)
downloadFreeBSD-src-e306c86e1b6376905ae8d21091509cbe1f61fba8.zip
FreeBSD-src-e306c86e1b6376905ae8d21091509cbe1f61fba8.tar.gz
Permit Giant to be passed as the explicit interlock either to
msleep/mtx_sleep or the various cv_*wait*() routines. Currently, the "unlock" behavior of PDROP and cv_wait_unlock() with Giant is not permitted as it is will be confusing since Giant is fully unrecursed and unlocked during a thread sleep. This is handy for subsystems which wish to allow unlocked drivers to continue to use Giant such as CAM, the new TTY layer, and the new USB stack. CAM currently uses a hack that I told Scott to use because I really didn't want to permit this behavior, and the TTY and USB patches both have various patches to permit this. MFC after: 2 weeks
Diffstat (limited to 'README')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud