From: Borislav Petkov <bp@alien8.de>
To: Leon Romanovsky <leon@kernel.org>
Cc: Joe Perches <joe@perches.com>,
"Rafael J . Wysocki" <rafael@kernel.org>,
Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>, x86 <x86@kernel.org>,
"H. Peter Anvin" <hpa@zytor.com>,
linux-pm <linux-pm@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH -next v1] x86/apic: Reduce print level of CPU limit announcement
Date: Wed, 27 Mar 2019 12:14:52 +0100 [thread overview]
Message-ID: <20190327111452.GC32571@zn.tnic> (raw)
In-Reply-To: <20190327105024.GR22899@mtr-leonro.mtl.com>
On Wed, Mar 27, 2019 at 12:50:24PM +0200, Leon Romanovsky wrote:
> It is how we are internally running verification and development,
> with KERN_DEBUG level, we need it to catch bugs.
And what is the big deal with seeing those messages? Why are *exactly*
those two such a big problem and the gazillion other debug messages are
fine?
> This "some config option" is dynamic debug prints and most probably it
> is enabled in your or any kernel developer in the world.
I personally don't use it because it only gets in the way.
--
Regards/Gruss,
Boris.
Good mailing practices for 400: avoid top-posting and trim the reply.
next prev parent reply other threads:[~2019-03-27 11:14 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-27 9:09 [PATCH -next v1] x86/apic: Reduce print level of CPU limit announcement Leon Romanovsky
2019-03-27 9:17 ` Joe Perches
2019-03-27 9:38 ` Leon Romanovsky
2019-03-27 9:49 ` Joe Perches
2019-03-27 9:53 ` Leon Romanovsky
2019-03-27 10:11 ` Leon Romanovsky
2019-03-27 10:17 ` Joe Perches
2019-03-27 10:18 ` Borislav Petkov
2019-03-27 10:50 ` Leon Romanovsky
2019-03-27 11:14 ` Borislav Petkov [this message]
2019-03-27 11:36 ` Leon Romanovsky
2019-03-27 11:49 ` Borislav Petkov
2019-03-27 11:58 ` Leon Romanovsky
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=20190327111452.GC32571@zn.tnic \
--to=bp@alien8.de \
--cc=hpa@zytor.com \
--cc=joe@perches.com \
--cc=leon@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=rafael@kernel.org \
--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