From: Florian Fainelli <f.fainelli@gmail.com>
To: Mark Rutland <mark.rutland@arm.com>
Cc: linux-arm-kernel@lists.infradead.org, rmk+kernel@armlinux.org.uk,
Catalin Marinas <catalin.marinas@arm.com>,
Will Deacon <will.deacon@arm.com>,
Ard Biesheuvel <ard.biesheuvel@linaro.org>,
Marc Zyngier <marc.zyngier@arm.com>,
Julien Thierry <julien.thierry@arm.com>,
Suzuki K Poulose <Suzuki.Poulose@arm.com>,
Sudeep Holla <sudeep.holla@arm.com>,
Rob Herring <robh@kernel.org>,
Steve Capper <steve.capper@arm.com>,
Lorenzo Pieralisi <lorenzo.pieralisi@arm.com>,
Daniel Thompson <daniel.thompson@linaro.org>,
open list <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] arm64: Demote boot and shutdown messages to pr_debug
Date: Wed, 1 May 2019 09:07:32 -0700 [thread overview]
Message-ID: <7c31327c-0449-9ea1-baf8-5adcadd3b630@gmail.com> (raw)
In-Reply-To: <20190501104733.GB11740@lakrids.cambridge.arm.com>
On 5/1/19 3:47 AM, Mark Rutland wrote:
> On Tue, Apr 30, 2019 at 03:38:31PM -0700, Florian Fainelli wrote:
>> Similar to commits c68b0274fb3cf ("ARM: reduce "Booted secondary
>> processor" message to debug level") and 035e787543de7 ("ARM: 8644/1: Reduce "CPU:
>> shutdown" message to debug level"), demote the secondary_start_kernel()
>> and __cpu_die() messages from info, respectively notice to debug. While
>> we are at it, also do this for cpu_psci_cpu_kill() which is redundant
>> with __cpu_die().
>>
>> This helps improve the amount of possible hotplug cycles by around +50%
>> on ARCH_BRCMSTB.
>
> Could you elaborate on why that matters?
>
> e.g. is this just for testing, or does this matter in some shutdown or
> hibernate scenario?
It matters to both testing, e.g.: how many hotplug cycles you can go
through within a given time frame to help assess system stsability, and
during opportunistic suspend that e.g.: Android does.
>
>> Signed-off-by: Florian Fainelli <f.fainelli@gmail.com>
>> ---
>> arch/arm64/kernel/psci.c | 2 +-
>> arch/arm64/kernel/smp.c | 4 ++--
>> 2 files changed, 3 insertions(+), 3 deletions(-)
>>
>> diff --git a/arch/arm64/kernel/psci.c b/arch/arm64/kernel/psci.c
>> index 8cdaf25e99cd..a78581046c80 100644
>> --- a/arch/arm64/kernel/psci.c
>> +++ b/arch/arm64/kernel/psci.c
>> @@ -96,7 +96,7 @@ static int cpu_psci_cpu_kill(unsigned int cpu)
>> for (i = 0; i < 10; i++) {
>> err = psci_ops.affinity_info(cpu_logical_map(cpu), 0);
>> if (err == PSCI_0_2_AFFINITY_LEVEL_OFF) {
>> - pr_info("CPU%d killed.\n", cpu);
>> + pr_debug("CPU%d killed.\n", cpu);
>> return 0;
>> }
>>
>> diff --git a/arch/arm64/kernel/smp.c b/arch/arm64/kernel/smp.c
>> index 824de7038967..71fd2b5a3f0e 100644
>> --- a/arch/arm64/kernel/smp.c
>> +++ b/arch/arm64/kernel/smp.c
>> @@ -259,7 +259,7 @@ asmlinkage notrace void secondary_start_kernel(void)
>> * the CPU migration code to notice that the CPU is online
>> * before we continue.
>> */
>> - pr_info("CPU%u: Booted secondary processor 0x%010lx [0x%08x]\n",
>> + pr_debug("CPU%u: Booted secondary processor 0x%010lx [0x%08x]\n",
>> cpu, (unsigned long)mpidr,
>> read_cpuid_id());
>
> I generally agree that we don't need to be verbose, and demoting these
> to debug is fine, but it's a shame that these won't be accessible in
> defconfig.
>
> I wonder if we should enable DYNAMIC_DEBUG so that we can turn these on
> from the kernel command line, or if we should have something like a
> verbose_hotplug option specifically for these messages.
Based on Robin's answer (CONFIG_DYNAMIC_DEBUG already enabled in the
default configuration), would you prefer this to become a dynamic debug
message instead?
--
Florian
prev parent reply other threads:[~2019-05-01 16:07 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-30 22:38 Florian Fainelli
2019-05-01 10:47 ` Mark Rutland
2019-05-01 11:01 ` Marc Zyngier
2019-05-01 11:02 ` Robin Murphy
2019-05-01 16:43 ` Florian Fainelli
2019-05-01 16:07 ` Florian Fainelli [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=7c31327c-0449-9ea1-baf8-5adcadd3b630@gmail.com \
--to=f.fainelli@gmail.com \
--cc=Suzuki.Poulose@arm.com \
--cc=ard.biesheuvel@linaro.org \
--cc=catalin.marinas@arm.com \
--cc=daniel.thompson@linaro.org \
--cc=julien.thierry@arm.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lorenzo.pieralisi@arm.com \
--cc=marc.zyngier@arm.com \
--cc=mark.rutland@arm.com \
--cc=rmk+kernel@armlinux.org.uk \
--cc=robh@kernel.org \
--cc=steve.capper@arm.com \
--cc=sudeep.holla@arm.com \
--cc=will.deacon@arm.com \
/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®