GitHub-Mirror/Star64_linux
2
0
Fork 0
mirror of https://github.com/Fishwaldo/Star64_linux.git synced 2025-07-08 07:21:27 +00:00
Code Issues Projects Releases Packages Wiki Activity Actions

rcu: Fix bogus CONFIG_PROVE_LOCKING in comments to reflect reality.

Browse source 
It is CONFIG_DEBUG_LOCK_ALLOC rather than CONFIG_PROVE_LOCKING, so fix it.

Signed-off-by: Paul E. McKenney <paulmck@linux.vnet.ibm.com>
This commit is contained in:
Paul E. McKenney 2010-03-30 10:52:21 -07:00
parent 5db356736a
commit d20200b591
2 changed files with 10 additions and 9 deletions
Download patch file Download diff file Expand all files Collapse all files

15
include/linux/rcupdate.h
View file

@ -106,8 +106,8 @@ extern int debug_lockdep_rcu_enabled(void);
/** /**
* rcu_read_lock_held - might we be in RCU read-side critical section? * rcu_read_lock_held - might we be in RCU read-side critical section?
* *
* If CONFIG_PROVE_LOCKING is selected and enabled, returns nonzero iff in * If CONFIG_DEBUG_LOCK_ALLOC is selected, returns nonzero iff in an RCU
* an RCU read-side critical section. In absence of CONFIG_PROVE_LOCKING, * read-side critical section. In absence of CONFIG_DEBUG_LOCK_ALLOC,
* this assumes we are in an RCU read-side critical section unless it can * this assumes we are in an RCU read-side critical section unless it can
* prove otherwise. * prove otherwise.
* *
@ -129,11 +129,12 @@ extern int rcu_read_lock_bh_held(void);
/** /**
* rcu_read_lock_sched_held - might we be in RCU-sched read-side critical section? * rcu_read_lock_sched_held - might we be in RCU-sched read-side critical section?
* *
* If CONFIG_PROVE_LOCKING is selected and enabled, returns nonzero iff in an * If CONFIG_DEBUG_LOCK_ALLOC is selected, returns nonzero iff in an
* RCU-sched read-side critical section. In absence of CONFIG_PROVE_LOCKING, * RCU-sched read-side critical section. In absence of
* this assumes we are in an RCU-sched read-side critical section unless it * CONFIG_DEBUG_LOCK_ALLOC, this assumes we are in an RCU-sched read-side
* can prove otherwise. Note that disabling of preemption (including * critical section unless it can prove otherwise. Note that disabling
* disabling irqs) counts as an RCU-sched read-side critical section. * of preemption (including disabling irqs) counts as an RCU-sched
* read-side critical section.
* *
* Check rcu_scheduler_active to prevent false positives during boot. * Check rcu_scheduler_active to prevent false positives during boot.
*/ */

4
include/linux/srcu.h
View file

@ -84,8 +84,8 @@ long srcu_batches_completed(struct srcu_struct *sp);
/** /**
* srcu_read_lock_held - might we be in SRCU read-side critical section? * srcu_read_lock_held - might we be in SRCU read-side critical section?
* *
* If CONFIG_PROVE_LOCKING is selected and enabled, returns nonzero iff in * If CONFIG_DEBUG_LOCK_ALLOC is selected, returns nonzero iff in an SRCU
* an SRCU read-side critical section. In absence of CONFIG_PROVE_LOCKING, * read-side critical section. In absence of CONFIG_DEBUG_LOCK_ALLOC,
* this assumes we are in an SRCU read-side critical section unless it can * this assumes we are in an SRCU read-side critical section unless it can
* prove otherwise. * prove otherwise.
*/ */