[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1495709703.5393.20.camel@synopsys.com>
Date: Thu, 25 May 2017 10:55:04 +0000
From: Alexey Brodkin <Alexey.Brodkin@...opsys.com>
To: "noamca@...lanox.com" <noamca@...lanox.com>
CC: "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"Vineet Gupta" <Vineet.Gupta1@...opsys.com>,
"linux-snps-arc@...ts.infradead.org"
<linux-snps-arc@...ts.infradead.org>
Subject: Re: [PATCH 01/10] ARC: set level of log per CPU during boot to be
debug level
Hi Noam,
On Thu, 2017-05-25 at 05:34 +0300, Noam Camus wrote:
> From: Noam Camus <noamca@...lanox.com>
>
> The reasons are:
> 1) speeding up boot time, becomes critical for many CPUs machine,
> e.g. NPS400 with 4K CPUs
> 2) shorten kernel log at boot time, again easy to scan for large
> scale machines such NPS400
>
> Signed-off-by: Noam Camus <noamca@...lanox.com>
I do understand your concern on getting 4k instances of pretty much the same
boiler plates for each core in NPS. But even in real life those headers
provide quite important information on what is user's HW and SW configuration.
That said for more generic use-cases especially when we have just a few cores
I'd say those messages really make sense.
What we may also do for example add "ccflags += -DDEBUG" in arch/arc/Makefile
so all pr_debug() instances again start to print messages in console. But do it say
only if !EzChip's platform is selected. So it keeps everything as it is for non-EzChip
cases and makes you guys happy as you no longer see those 4096 headers.
Let's see what Vineet says.
-Alexey
Powered by blists - more mailing lists