From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752860AbaIOOMc (ORCPT ); Mon, 15 Sep 2014 10:12:32 -0400 Received: from mx3-phx2.redhat.com ([209.132.183.24]:56097 "EHLO mx3-phx2.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751561AbaIOOMa (ORCPT ); Mon, 15 Sep 2014 10:12:30 -0400 Date: Mon, 15 Sep 2014 10:11:20 -0400 (EDT) Subject: Re: [PATCH v4 10/18] ACPI / table: Print GIC information when MADT is parsed From: Jon Masters To: Olof Johansson Cc: linux-acpi@vger.kernel.org, Randy Dunlap , Arnd Bergmann , Lv Zheng , Lorenzo Pieralisi , Sudeep Holla , "Rafael J. Wysocki" , Hanjun Guo , Graeme Gregory , Marc Zyngier , linaro-acpi@lists.linaro.org, Robert Richter , Charles.Garcia-Tobin@arm.com, Daniel Lezcano , Liviu Dudau , Bjorn Helgaas , Catalin Marinas , Tomasz Nowicki , Rob Herring , linux-kernel@vger.kernel.org, Mark Rutland , Mark Brown , linux-arm-kernel@lists.infradead.org, Will Deacon , Grant Likely , Robert Moore , Jason Cooper MIME-Version: 1.0 Message-ID: <110210623.13993550.1410790280170.JavaMail.zimbra@zmail15.collab.prod.int.phx2.redhat.com> Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit X-Mailer: Zimbra 8.0.6_GA_5922 (MobileSync - Android/4.4.4-EAS-2.0) In-Reply-To: <20140915064010.GD26649@localhost> References: <1410530416-30200-1-git-send-email-hanjun.guo@linaro.org> <1410530416-30200-11-git-send-email-hanjun.guo@linaro.org> <20140915064010.GD26649@localhost> Thread-Topic: ACPI / table: Print GIC information when MADT is parsed Thread-Index: EFjzTF77i+00kwVAU+3MZ5w/wtcVRA== Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hi Olof, How about having it verbose in the initial implementation (in case there are any fun times bringing up early systems) and then revisiting this? x86 is very verbose but it can be helpful. Jon. -- Computer Architect | Sent from my #ARM Powered Mobile device On Sep 15, 2014 12:34 AM, Olof Johansson wrote: > > On Fri, Sep 12, 2014 at 10:00:08PM +0800, Hanjun Guo wrote: > > When MADT is parsed, print GIC information to 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. 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? -Olof