Message-ID: <40C3452B.5010500@pobox.com>
Date: Sun, 06 Jun 2004 12:24:11 -0400
From: Jeff Garzik <jgarzik@pobox.com>
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.6) Gecko/20040510
MIME-Version: 1.0
To: Ingo Molnar <mingo@elte.hu>
CC: Andi Kleen <ak@suse.de>, akpm@osdl.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Disable scheduler debugging
References: <20040606033238.4e7d72fc.ak@suse.de> <20040606055336.GA15350@elte.hu>
In-Reply-To: <20040606055336.GA15350@elte.hu>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1079
Lines: 29

Ingo Molnar wrote:
> * Andi Kleen <ak@suse.de> wrote:
> 
> 
>>The domain scheduler spews out a lot of information at boot up, but it
>>looks mostly redundant because it's just a transformation of what is
>>in /proc/cpuinfo anyways. Also it is well tested now. Disable it.
> 
> 
> i'd rather keep it some more, there are still open issues and if there's
> a boot failure or early crash it makes it easier for us to see the
> actual domain setup. Also, the messages are KERN_DEBUG.


Unfortunately there are just, flat-out, way too many kernel messages at 
boot-up.  Making them KERN_DEBUG doesn't solve the fact that SMP boxes 
often overflow the printk buffer before you boot up to a useful userland 
that can record the dmesg.

The IO-APIC code is a _major_ offender in this area, but the CPU code is 
right up there as well.

	Jeff

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/