From 10ebd8556b7990499c896a550e3d416b444211e6 Mon Sep 17 00:00:00 2001 From: hc <hc@nodka.com> Date: Fri, 10 May 2024 02:23:07 +0000 Subject: [PATCH] add led --- kernel/Documentation/RCU/stallwarn.rst | 4 ++-- 1 files changed, 2 insertions(+), 2 deletions(-) diff --git a/kernel/Documentation/RCU/stallwarn.rst b/kernel/Documentation/RCU/stallwarn.rst index e97d1b4..c9ab6af 100644 --- a/kernel/Documentation/RCU/stallwarn.rst +++ b/kernel/Documentation/RCU/stallwarn.rst @@ -25,7 +25,7 @@ - A CPU looping with bottom halves disabled. -- For !CONFIG_PREEMPTION kernels, a CPU looping anywhere in the kernel +- For !CONFIG_PREEMPT kernels, a CPU looping anywhere in the kernel without invoking schedule(). If the looping in the kernel is really expected and desirable behavior, you might need to add some calls to cond_resched(). @@ -44,7 +44,7 @@ result in the ``rcu_.*kthread starved for`` console-log message, which will include additional debugging information. -- A CPU-bound real-time task in a CONFIG_PREEMPTION kernel, which might +- A CPU-bound real-time task in a CONFIG_PREEMPT kernel, which might happen to preempt a low-priority task in the middle of an RCU read-side critical section. This is especially damaging if that low-priority task is not permitted to run on any other CPU, -- Gitblit v1.6.2