mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Heiner Kallweit <hkallweit1@gmail.com>
To: Jason Baron <jbaron@akamai.com>,
	Thomas Gleixner <tglx@linutronix.de>,
	Ingo Molnar <mingo@redhat.com>, Borislav Petkov <bp@alien8.de>,
	x86@kernel.org, "H. Peter Anvin" <hpa@zytor.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: [PATCH 0/2] x86/e820: Use pr_debug to avoid spamming dmesg log with debug messages
Date: Mon, 3 May 2021 21:38:10 +0200	[thread overview]
Message-ID: <f527618e-54f2-c2fb-e267-8065ac34e462@gmail.com> (raw)

e820 emits quite some debug messages to the dmesg log. Let's restrict
this to cases where the debug output is actually requested. Switch to
pr_debug() for this purpose and make sure by checking the return code
that pr_cont() is only called if applicable. This would currently fail
if dynamic debugging is enabled because dynamic_pr_debug() has no
return value. So let's change this first.

Heiner Kallweit (2):
  dyndbg: add pr_debug return value if dynamic debugging is enabled
  x86/e820: Use pr_debug to avoid spamming dmesg log with debug messages

 arch/x86/kernel/e820.c        | 27 ++++++++++++++++-----------
 include/linux/dynamic_debug.h | 14 +++++++++++---
 lib/dynamic_debug.c           |  7 +++++--
 3 files changed, 32 insertions(+), 16 deletions(-)

-- 
2.31.1


             reply	other threads:[~2021-05-03 19:38 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-03 19:38 Heiner Kallweit [this message]
2021-05-03 19:39 ` [PATCH 1/2] dyndbg: add pr_debug return value if dynamic debugging is enabled Heiner Kallweit
2021-05-03 19:40 ` [PATCH 2/2] x86/e820: Use pr_debug to avoid spamming dmesg log with debug messages Heiner Kallweit
2021-05-05 16:58   ` Jason Baron
2021-05-05 18:40     ` Heiner Kallweit
2021-05-11  3:21       ` Jason Baron
2021-05-11 20:36         ` Heiner Kallweit
2021-05-11 21:31           ` Jason Baron
2021-05-14 17:38             ` Joe Perches
2021-05-14 19:56               ` Jason Baron
2021-05-14 20:22                 ` Joe Perches
2021-05-14 20:32                   ` Jason Baron
2021-05-14 21:15                     ` Heiner Kallweit

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=f527618e-54f2-c2fb-e267-8065ac34e462@gmail.com \
    --to=hkallweit1@gmail.com \
    --cc=bp@alien8.de \
    --cc=hpa@zytor.com \
    --cc=jbaron@akamai.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=tglx@linutronix.de \
    --cc=x86@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

Powered by JetHome