diff options
author | Jonathan Corbet <corbet@lwn.net> | 2008-05-18 14:27:41 -0600 |
---|---|---|
committer | Jonathan Corbet <corbet@lwn.net> | 2008-06-20 14:05:53 -0600 |
commit | 0b2806768899dba5967bcd4a3b93eaed9a1dc4f3 (patch) | |
tree | c9e7762d9b236883f4a23a170919317a6e7c93c7 /arch | |
parent | 6606470dd1d628878383c96d10b52a77986ddac7 (diff) | |
download | op-kernel-dev-0b2806768899dba5967bcd4a3b93eaed9a1dc4f3.zip op-kernel-dev-0b2806768899dba5967bcd4a3b93eaed9a1dc4f3.tar.gz |
Add cycle_kernel_lock()
A number of driver functions are so obviously trivial that they do not need
the big kernel lock - at least not overtly. It turns out that the
acquisition of the BKL in driver open() functions can perform a sort of
poor-hacker's serialization function, delaying the open operation until the
driver is certain to have completed its initialization. Add a simple
cycle_kernel_lock() function for these cases to make it clear that there is
no need to *hold* the BKL, just to be sure that we can acquire it.
Signed-off-by: Jonathan Corbet <corbet@lwn.net>
Diffstat (limited to 'arch')
0 files changed, 0 insertions, 0 deletions