lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  PHC 
Open Source and information security mailing list archives
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:	Mon, 15 Sep 2014 11:01:40 -0700
From:	Olof Johansson <>
To:	Grant Likely <>
Cc:	Hanjun Guo <>,
	Catalin Marinas <>,
	"Rafael J. Wysocki" <>,
	Mark Rutland <>,
	Will Deacon <>,
	Graeme Gregory <>,
	Arnd Bergmann <>,
	Sudeep Holla <>,
	Jon Masters <>,
	Jason Cooper <>,
	Marc Zyngier <>,
	Bjorn Helgaas <>,
	Daniel Lezcano <>,
	Mark Brown <>, Rob Herring <>,
	Robert Richter <>,
	Lv Zheng <>,
	Robert Moore <>,
	Lorenzo Pieralisi <>,
	Liviu Dudau <>,
	Randy Dunlap <>,
	Charles Garcia-Tobin <>,
	"" <>,
	"" <>,
	"" <>,
	Tomasz Nowicki <>
Subject: Re: [PATCH v4 10/18] ACPI / table: Print GIC information when MADT is parsed

On Mon, Sep 15, 2014 at 10:52 AM, Grant Likely <> wrote:
> On Sun, 14 Sep 2014 23:40:10 -0700, Olof Johansson <> wrote:
>> On Fri, Sep 12, 2014 at 10:00:08PM +0800, Hanjun Guo wrote:
>> > When MADT is parsed, print GIC information to make the boot
>> > log look pretty.
>> If you do this for prettiness, having an example output in the commit
>> message would be a nice touch.
> Agreed.
>> The question is why it's needed though? Do we really need all this verbose
>> information in dmesg when it could be found out in other ways instead?
>> x86 is notoriously verbose in some of these aspects, I'm not sure it's
>> something we need to mimic here?
> For consistency, it does make sense to have the common x86 and ARM64
> code outputing information in the same way, so I think the patch still
> makes sense. All of them could be moved to KERN_DEBUG as a separate
> patch if we want to cull early boot output. I would split that off and
> discuss it separately.

Yeah, pr_debug() makes sense here -- in particular if you're going to
have a potentially slow serial console to print all this to at info

I disagree on order though, there's no reason to hold off fixing this
and doing it as a separate patch.

To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

Powered by blists - more mailing lists