Messages in this thread | | | Date | Sun, 06 Jun 2004 12:24:11 -0400 | From | Jeff Garzik <> | Subject | Re: [PATCH] Disable scheduler debugging |
| |
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/
| |