rcu-tasks miscellaneous fixes
v2 cover rcu-tasks miscellaneous fixes
Minor typos in comments and fixes for rcu-tasks.
V1 -> V2:
- Update comment in patch 4/5, as suggested by Paul.
Neeraj Upadhyay (5):
rcu-tasks: Fix s/rcu_add_holdout/trc_add_holdout/ typo in comment
rcu-tasks: Correct firstreport usage in check_all_holdout_tasks_trace
rcu-tasks: Correct check for no_hz_full cpu in show_stalled_task_trace
rcu-tasks: Fix read-side primitives comment for call_rcu_tasks_trace
rcu-tasks: Clarify read side section info for rcu_tasks_rude GP
primitives
kernel/rcu/tasks.h | 36 ++++++++++++++++-------------------- 1 file changed, 16 insertions(+), 20 deletions(-)
Signature · 2 lines
QUALCOMM INDIA, on behalf of Qualcomm Innovation Center, Inc. is a member of the Code Aurora Forum, hosted by The Linux Foundation
PATCH v2 1/5 rcu-tasks: Fix s/rcu_add_holdout/trc_add_holdout/ typo in comment
--- kernel/rcu/tasks.h | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
kernel/rcu/tasks.h +1 -1
@@ -996,7 +996,7 @@ static void trc_wait_for_one_reader(struct task_struct *t,// If this task is not yet on the holdout list, then we are in // an RCU read-side critical section. Otherwise, the invocation of -// rcu_add_holdout() that added it to the list did the necessary +// trc_add_holdout() that added it to the list did the necessary // get_task_struct(). Either way, the task cannot be freed out // from under this code.
Signature · 2 lines
QUALCOMM INDIA, on behalf of Qualcomm Innovation Center, Inc. is a member of the Code Aurora Forum, hosted by The Linux Foundation
PATCH v2 2/5 rcu-tasks: Correct firstreport usage in check_all_holdout_tasks_trace
In reply to Neeraj UpadhyayIn check_all_holdout_tasks_trace(), firstreport is a pointer argument; so, check the dereferenced value, instead of checking the pointer.
--- kernel/rcu/tasks.h | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
kernel/rcu/tasks.h +1 -1
@@ -1134,7 +1134,7 @@ static void check_all_holdout_tasks_trace(struct list_head *hop,cpus_read_unlock ();if (needreport) { -if (firstreport) +if (*firstreport)pr_err ("INFO: rcu_tasks_trace detected stalls? (Late IPI?)\n" );show_stalled_ipi_trace (); }
Signature · 2 lines
QUALCOMM INDIA, on behalf of Qualcomm Innovation Center, Inc. is a member of the Code Aurora Forum, hosted by The Linux Foundation
PATCH v2 3/5 rcu-tasks: Correct check for no_hz_full cpu in show_stalled_task_trace
In reply to Neeraj UpadhyayCorrect the check for no_hz_full cpu in show_stalled_task_trace(), to include cpu 0.
--- kernel/rcu/tasks.h | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
kernel/rcu/tasks.h +1 -1
@@ -1091,7 +1091,7 @@ static void show_stalled_task_trace(struct task_struct *t, bool *firstreport) t->pid,".I" [READ_ONCE (t->trc_ipi_to_cpu) >0 ],".i" [is_idle_task (t)], -".N" [cpu >0 &&tick_nohz_full_cpu (cpu)], +".N" [cpu >=0 &&tick_nohz_full_cpu (cpu)],READ_ONCE (t->trc_reader_nesting)," N" [!!READ_ONCE (t->trc_reader_special.b.need_qs)], cpu);
Signature · 2 lines
QUALCOMM INDIA, on behalf of Qualcomm Innovation Center, Inc. is a member of the Code Aurora Forum, hosted by The Linux Foundation
PATCH v2 4/5 rcu-tasks: Fix read-side primitives comment for call_rcu_tasks_trace
In reply to Neeraj Upadhyaycall_rcu_tasks_trace() does have read-side primitives - rcu_read_lock_trace() and rcu_read_unlock_trace(). Fix this information in the comments.
--- kernel/rcu/tasks.h | 16 ++++++---------- 1 file changed, 6 insertions(+), 10 deletions(-)
kernel/rcu/tasks.h +6 -10
@@ -1212,15 +1212,11 @@ static void exit_tasks_rcu_finish_trace(struct task_struct *t)* @rhp: structure to be used for queueing the RCU updates. * @func: actual callback function to be invoked after the grace period * -* The callback function will be invoked some time after a full grace -* period elapses, in other words after all currently executing RCU -* read-side critical sections have completed. call_rcu_tasks_trace() -* assumes that the read-side critical sections end at context switch, -* cond_resched_rcu_qs(), or transition to usermode execution. As such, -* there are no read-side primitives analogous to rcu_read_lock() and -* rcu_read_unlock() because this primitive is intended to determine -* that all tasks have passed through a safe state, not so much for -* data-structure synchronization. +* The callback function will be invoked some time after a trace rcu-tasks +* grace period elapses, in other words after all currently executing +* trace rcu-tasks read-side critical sections have completed. These +* read-side critical sections are delimited by calls to rcu_read_lock_trace() +* and rcu_read_unlock_trace(). * * See the description of call_rcu() for more detailed information on * memory ordering guarantees.
@@ -1236,7 +1232,7 @@ EXPORT_SYMBOL_GPL(call_rcu_tasks_trace);* * Control will return to the caller some time after a trace rcu-tasks * grace period has elapsed, in other words after all currently executing -* rcu-tasks read-side critical sections have elapsed. These read-side +* trace rcu-tasks read-side critical sections have elapsed. These read-side * critical sections are delimited by calls to rcu_read_lock_trace() * and rcu_read_unlock_trace(). *
Signature · 2 lines
QUALCOMM INDIA, on behalf of Qualcomm Innovation Center, Inc. is a member of the Code Aurora Forum, hosted by The Linux Foundation
Re: [PATCH v2 4/5] rcu-tasks: Fix read-side primitives comment for call_rcu_tasks_trace
Quoted 4 lines · Neeraj Upadhyay
call_rcu_tasks_trace()does have read-side primitives -rcu_read_lock_trace()andrcu_read_unlock_trace(). Fix this information in the comments.Signed-off-by Neeraj Upadhyay <[email protected]>
Queued for v5.16, thank you very much!
(The other four patches are already queued.)
Thanx, Paul
Quoted 42 lines
--- kernel/rcu/tasks.h | 16 ++++++---------- 1 file changed, 6 insertions(+), 10 deletions(-)kernel/rcu/tasks.h +6
-10@@ -1212,15 +1212,11 @@ static void exit_tasks_rcu_finish_trace(struct task_struct *t)* @rhp: structure to be used for queueing the RCU updates. * @func: actual callback function to be invoked after the grace period * -* The callback function will be invoked some time after a full grace -* period elapses, in other words after all currently executing RCU -* read-side critical sections have completed. call_rcu_tasks_trace() -* assumes that the read-side critical sections end at context switch, -* cond_resched_rcu_qs(), or transition to usermode execution. As such, -* there are no read-side primitives analogous to rcu_read_lock() and -* rcu_read_unlock() because this primitive is intended to determine -* that all tasks have passed through a safe state, not so much for -* data-structure synchronization. +* The callback function will be invoked some time after a trace rcu-tasks +* grace period elapses, in other words after all currently executing +* trace rcu-tasks read-side critical sections have completed. These +* read-side critical sections are delimited by calls to rcu_read_lock_trace() +* and rcu_read_unlock_trace(). * * See the description of call_rcu() for more detailed information on * memory ordering guarantees. @@ -1236,7 +1232,7 @@ EXPORT_SYMBOL_GPL(call_rcu_tasks_trace);* * Control will return to the caller some time after a trace rcu-tasks * grace period has elapsed, in other words after all currently executing -* rcu-tasks read-side critical sections have elapsed. These read-side +* trace rcu-tasks read-side critical sections have elapsed. These read-side * critical sections are delimited by calls to rcu_read_lock_trace() * and rcu_read_unlock_trace(). * Signature · 2 lines
QUALCOMM INDIA, on behalf of Qualcomm Innovation Center, Inc. is a member of the Code Aurora Forum, hosted by The Linux Foundation
PATCH v2 5/5 rcu-tasks: Clarify read side section info for rcu_tasks_rude GP primitives
In reply to Neeraj UpadhyayRCU tasks rude variant does not maintain or check whether the current running context on a CPU is usermode. Read side critical section ends on transition to usermode execution, by the virtue of usermode execution being schedulable. Clarify this in comments for call_rcu_tasks_rude() and synchronize_rcu_tasks_rude().
--- kernel/rcu/tasks.h | 14 +++++++------- 1 file changed, 7 insertions(+), 7 deletions(-)
kernel/rcu/tasks.h +7 -7
@@ -677,11 +677,11 @@ DEFINE_RCU_TASKS(rcu_tasks_rude, rcu_tasks_rude_wait_gp, call_rcu_tasks_rude,* period elapses, in other words after all currently executing RCU * read-side critical sections have completed. call_rcu_tasks_rude() * assumes that the read-side critical sections end at context switch, -* cond_resched_rcu_qs(), or transition to usermode execution. As such, -* there are no read-side primitives analogous to rcu_read_lock() and -* rcu_read_unlock() because this primitive is intended to determine -* that all tasks have passed through a safe state, not so much for -* data-structure synchronization. +* cond_resched_rcu_qs(), or transition to usermode execution (as +* usermode execution is schedulable). As such, there are no read-side +* primitives analogous to rcu_read_lock() and rcu_read_unlock() because +* this primitive is intended to determine that all tasks have passed +* through a safe state, not so much for data-structure synchronization. * * See the description of call_rcu() for more detailed information on * memory ordering guarantees.
@@ -699,8 +699,8 @@ EXPORT_SYMBOL_GPL(call_rcu_tasks_rude);* grace period has elapsed, in other words after all currently * executing rcu-tasks read-side critical sections have elapsed. These * read-side critical sections are delimited by calls to schedule(), -* cond_resched_tasks_rcu_qs(), userspace execution, and (in theory, -* anyway) cond_resched(). +* cond_resched_tasks_rcu_qs(), userspace execution (which is a schedulable +* context), and (in theory, anyway) cond_resched(). * * This is a very specialized primitive, intended only for a few uses in * tracing and other situations requiring manipulation of function preambles
Signature · 2 lines
QUALCOMM INDIA, on behalf of Qualcomm Innovation Center, Inc. is a member of the Code Aurora Forum, hosted by The Linux Foundation