All of lore.kernel.org
 help / color / mirror / Atom feed
From: Breno Leitao <leitao@debian.org>
To: Song Liu <song@kernel.org>
Cc: rcu@vger.kernel.org, paulmck@kernel.org,
	linux-kernel@vger.kernel.org,  kernel-team@meta.com,
	rostedt@goodmis.org, david.dai@linux.dev
Subject: Re: [PATCH] rcu-tasks: Use pr_debug() for callback contend/collapse messages
Date: Thu, 12 Nov 2026 01:39:08 -0800	[thread overview]
Message-ID: <avWJMVvAuUEdjmuu@gmail.com> (raw)
In-Reply-To: <20261111053551.3367903-1-song@kernel.org>

On Tue, Nov 10, 2026 at 09:35:51PM -0800, Song Liu wrote:
> Commit 5de907d24919 ("rcu-tasks: Disable callback contend/collapse
> messages by default") added the rcupdate.rcu_task_collapse_debug module
> parameter to gate the three pr_info() messages that report RCU Tasks
> switching between CPU-0 and per-CPU callback queuing.
> 
> The kernel already has a mechanism for debug-only messages that are off
> by default: pr_debug().  Use pr_debug() for these messages, and remove
> the rcu_task_collapse_debug module parameter, its documentation, and
> its boot-time announcement.
> 
> The messages stay off by default.  On CONFIG_DYNAMIC_DEBUG=y kernels,
> they can be enabled at boot with:
> 
>   dyndbg="file kernel/rcu/tasks.h +p"
> 
> or at runtime with:
> 
>   echo 'file kernel/rcu/tasks.h +p' > /proc/dynamic_debug/control
> 
> Assisted-by: Claude:claude-opus-5
> Signed-off-by: Song Liu <song@kernel.org>

Tested-by: Breno Leitao <leitao@debian.org>

      parent reply	other threads:[~2026-11-12  9:39 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-11-11  5:35 [PATCH] rcu-tasks: Use pr_debug() for callback contend/collapse messages Song Liu
2026-11-11 15:54 ` Joel Fernandes
2026-11-11 17:32   ` Song Liu
2026-11-11 18:22     ` Joel Fernandes
2026-11-11 18:52       ` Paul E. McKenney
2026-11-11 18:51 ` Paul E. McKenney
2026-11-12  9:39 ` Breno Leitao [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=avWJMVvAuUEdjmuu@gmail.com \
    --to=leitao@debian.org \
    --cc=david.dai@linux.dev \
    --cc=kernel-team@meta.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=paulmck@kernel.org \
    --cc=rcu@vger.kernel.org \
    --cc=rostedt@goodmis.org \
    --cc=song@kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.