LKML Archive on
help / color / mirror / Atom feed
From: "tip-bot2 for Lee Jones" <>
Cc: Lee Jones <>,
	Thomas Gleixner <>,,,
Subject: [tip: irq/core] genirq/cpuhotplug: Demote debug printk to KERN_DEBUG
Date: Tue, 24 Aug 2021 07:20:29 -0000	[thread overview]
Message-ID: <162978962944.25758.8716579313615137898.tip-bot2@tip-bot2> (raw)
In-Reply-To: <>

The following commit has been merged into the irq/core branch of tip:

Commit-ID:     88ffe2d0a55a165e55cedad1693f239d47e3e17e
Author:        Lee Jones <>
AuthorDate:    Mon, 16 Aug 2021 14:48:17 +01:00
Committer:     Thomas Gleixner <>
CommitterDate: Tue, 24 Aug 2021 09:16:20 +02:00

genirq/cpuhotplug: Demote debug printk to KERN_DEBUG

This sort of information is only generally useful when debugging.
No need to have these sprinkled through the kernel log otherwise.

Real world problem:

  During pre-release testing these have an affect on performance on
  real products.  To the point where so much logging builds up, that
  it sets off the watchdog(s) on some high profile consumer devices.

Signed-off-by: Lee Jones <>
Signed-off-by: Thomas Gleixner <>
 kernel/irq/cpuhotplug.c | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/kernel/irq/cpuhotplug.c b/kernel/irq/cpuhotplug.c
index 02236b1..39a41c5 100644
--- a/kernel/irq/cpuhotplug.c
+++ b/kernel/irq/cpuhotplug.c
@@ -166,7 +166,7 @@ void irq_migrate_all_off_this_cpu(void)
 		if (affinity_broken) {
-			pr_warn_ratelimited("IRQ %u: no longer affine to CPU%u\n",
+			pr_debug_ratelimited("IRQ %u: no longer affine to CPU%u\n",
 					    irq, smp_processor_id());

      reply	other threads:[~2021-08-24  7:20 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-08-16 13:48 [PATCH v2 1/1] genirq/cpuhotplug: Bump debugging information print down " Lee Jones
2021-08-24  7:20 ` tip-bot2 for Lee Jones [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:

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

  git send-email \
    --in-reply-to=162978962944.25758.8716579313615137898.tip-bot2@tip-bot2 \ \ \ \ \ \ \ \
    --subject='Re: [tip: irq/core] genirq/cpuhotplug: Demote debug printk to KERN_DEBUG' \

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).