public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jeff Garzik <jgarzik@pobox.com>
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
Date: Sun, 06 Jun 2004 12:24:11 -0400	[thread overview]
Message-ID: <40C3452B.5010500@pobox.com> (raw)
In-Reply-To: <20040606055336.GA15350@elte.hu>

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


  reply	other threads:[~2004-06-06 16:24 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-06-06  1:32 [PATCH] Disable scheduler debugging Andi Kleen
2004-06-06  5:53 ` Ingo Molnar
2004-06-06 16:24   ` Jeff Garzik [this message]
2004-06-06 21:46     ` Zwane Mwaikambo
2004-06-06 21:55       ` Jeff Garzik
2004-06-06 21:55         ` Randy.Dunlap
2004-06-06 22:57     ` David Lang

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=40C3452B.5010500@pobox.com \
    --to=jgarzik@pobox.com \
    --cc=ak@suse.de \
    --cc=akpm@osdl.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox