From mboxrd@z Thu Jan 1 00:00:00 1970 From: Mike Travis Subject: Re: [patch] x86: reduce srat verbosity in the kernel log Date: Wed, 28 Oct 2009 14:35:47 -0700 Message-ID: <4AE8B933.5020103@sgi.com> References: <20091023233743.439628000@alcatraz.americas.sgi.com> <20091023233750.702443000@alcatraz.americas.sgi.com> <87pr8ay6tc.fsf@basil.nowhere.org> <4AE710C9.2070307@sgi.com> <4AE75162.7080903@sgi.com> <20091028033219.GE7744@basil.fritz.box> <20091028041159.GI7744@basil.fritz.box> <4AE8792F.8070200@sgi.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Return-path: Received: from relay3.sgi.com ([192.48.152.1]:59098 "EHLO relay.sgi.com" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1755281AbZJ1Vfr (ORCPT ); Wed, 28 Oct 2009 17:35:47 -0400 In-Reply-To: Sender: linux-acpi-owner@vger.kernel.org List-Id: linux-acpi@vger.kernel.org To: David Rientjes Cc: Andi Kleen , Ingo Molnar , Thomas Gleixner , Andrew Morton , Jack Steiner , "H. Peter Anvin" , x86@kernel.org, Yinghai Lu , Mel Gorman , linux-kernel@vger.kernel.org, linux-acpi@vger.kernel.org David Rientjes wrote: > On Wed, 28 Oct 2009, Mike Travis wrote: > >> I don't understand the importance of this when the memory is given back >> after the system starts up anyway...? >> > > 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? [ 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? Thanks, Mike