[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <alpine.DEB.2.00.0910281440580.32315@chino.kir.corp.google.com>
Date: Wed, 28 Oct 2009 14:46:44 -0700 (PDT)
From: David Rientjes <rientjes@...gle.com>
To: Mike Travis <travis@....com>
cc: Andi Kleen <andi@...stfloor.org>, Ingo Molnar <mingo@...e.hu>,
Thomas Gleixner <tglx@...utronix.de>,
Andrew Morton <akpm@...ux-foundation.org>,
Jack Steiner <steiner@....com>,
"H. Peter Anvin" <hpa@...or.com>, x86@...nel.org,
Yinghai Lu <yinghai@...nel.org>, Mel Gorman <mel@....ul.ie>,
linux-kernel@...r.kernel.org, linux-acpi@...r.kernel.org
Subject: Re: [patch] x86: reduce srat verbosity in the kernel log
On Wed, 28 Oct 2009, Mike Travis wrote:
> > Printing a list of apic ids longer than 128 characters would pollute the
> > kernel log and this upper bound will probably never be reached based on the
> > way apic ids are created for physical and logical processors: they are
> > normally reduced to ranges instead of comma seperated entities.
>
> Ahh, ok, thanks.
>
> Does that mean this 10,649 character line full of periods is illegal?
>
I'm not saying it would be illegal, merely that it would be harm
readability. Based on how apic id's are formed from processor ids,
though, I think we're really talking about an upper limit (128) that will
never be reached.
> [ 102.551570] Completing Region/Field/Buffer/Package initialization:
> ............... [long time later] .........
> <4>Clocksource tsc unstable (delta = 4396383657849 ns)
>
> I'm having trouble finding it. Does it look familiar to anyone?
>
It's debugging output from acpi_ns_initialize_objects() and each period is
from acpi_ns_init_one_device(). You can suppress it by disabing
CONFIG_ACPI_DEBUG.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists