From: Joe Perches <joe@perches.com>
To: Leon Romanovsky <leon@kernel.org>,
"Rafael J . Wysocki" <rafael@kernel.org>,
Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>, Borislav Petkov <bp@alien8.de>,
x86 <x86@kernel.org>
Cc: Leon Romanovsky <leonro@mellanox.com>,
"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 02:17:40 -0700 [thread overview]
Message-ID: <fef570d91276280f055a0b1c2561b3dd8e20a0c3.camel@perches.com> (raw)
In-Reply-To: <20190327090905.5588-1-leon@kernel.org>
On Wed, 2019-03-27 at 11:09 +0200, Leon Romanovsky wrote:
> Kernel is booted with less possible CPUs (possible_cpus kernel boot
> option) than available CPUs will have prints like this:
[]
> diff --git a/arch/x86/kernel/apic/apic.c b/arch/x86/kernel/apic/apic.c
[]
> @@ -2305,9 +2305,9 @@ int generic_processor_info(int apicid, int version)
> if (num_processors >= nr_cpu_ids) {
> int thiscpu = max + disabled_cpus;
>
> - pr_warning("APIC: NR_CPUS/possible_cpus limit of %i "
> - "reached. Processor %d/0x%x ignored.\n",
> - max, thiscpu, apicid);
> + pr_debug(
> + "APIC: NR_CPUS/possible_cpus limit of %i reached. Processor %d/0x%x ignored.\n",
> + max, thiscpu, apicid);
2 lines please
pr_debug("APIC: etc...",
max, thiscpu, ...);
And this would probably be better as
printk(KERN_DEBUG "APIC: etc...",
...)
to avoid the need to compile with DEBUG or enable
with CONFIG_DYNAMIC_DEBUG
next prev parent reply other threads:[~2019-03-27 9:17 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-27 9:09 Leon Romanovsky
2019-03-27 9:17 ` Joe Perches [this message]
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
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=fef570d91276280f055a0b1c2561b3dd8e20a0c3.camel@perches.com \
--to=joe@perches.com \
--cc=bp@alien8.de \
--cc=hpa@zytor.com \
--cc=leon@kernel.org \
--cc=leonro@mellanox.com \
--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
all inboxes | Powered by JetHome®