Commit 0019a2d4 authored Apr 27, 2023 by Randy Dunlap Committed by Peter Zijlstra May 08, 2023

sched: fix cid_lock kernel-doc warnings

Fix kernel-doc warnings for cid_lock and use_cid_lock.
These comments are not in kernel-doc format.

kernel/sched/core.c:11496: warning: Cannot understand * @cid_lock: Guarantee forward-progress of cid allocation.
on line 11496 - I thought it was a doc line
kernel/sched/core.c:11505: warning: Cannot understand * @use_cid_lock: Select cid allocation behavior: lock-free vs spinlock.
on line 11505 - I thought it was a doc line

Fixes: 223baf9d ("sched: Fix performance regression introduced by mm_cid")
Signed-off-by: Randy Dunlap <rdunlap@infradead.org>
Signed-off-by: Peter Zijlstra (Intel) <peterz@infradead.org>
Link: https://lkml.kernel.org/r/20230428031111.322-1-rdunlap@infradead.org

parent ac9a7868

kernel/sched/core.c

+2 −2

Original line number	Diff line number	Diff line
		@@ -11492,7 +11492,7 @@ void call_trace_sched_update_nr_running(struct rq *rq, int count)

		#ifdef CONFIG_SCHED_MM_CID

		/**
		/*
		* @cid_lock: Guarantee forward-progress of cid allocation.
		*
		* Concurrency ID allocation within a bitmap is mostly lock-free. The cid_lock
		@@ -11501,7 +11501,7 @@ void call_trace_sched_update_nr_running(struct rq *rq, int count)
		*/
		DEFINE_RAW_SPINLOCK(cid_lock);

		/**
		/*
		* @use_cid_lock: Select cid allocation behavior: lock-free vs spinlock.
		*
		* When @use_cid_lock is 0, the cid allocation is lock-free. When contention is