Re: [PATCH] apci: dump slit

[Thomas Gleixner <tglx@linutronix.de>]

On Fri, 12 Sep 2008, Andi Kleen wrote:
> On the other hand there's quite some other information dumped
> at boot that could be cut out. e.g. It doesn't really make 
> much sense to dump the cache information of each CPU at boot
> when that information can easily be gotten from user space
> later.

You're assuming that you ever reach user space, which is a pretty dumb
assumption.

I prefer to have a detailed view of the machine when I have to look at
a bug report where the machine does _NOT_ reach user space.
 
> I personally was also always sceptical of some of the
> more detailed new memory map dumping, like those "nosave
> memory" or the early reservation/early node/add_active_range output.
> It's pretty much a direct function of the e820 map dumped earlier.
> Also node information has now the dubious distinction to be 
> the most redundantly dumped kernel information of all.

Bla, bla, bla. 

This code was reworked significantly and every information which is
given about the various decisions made are useful to debug problems. I
prefer a more noisy startup over some silent fuckup when a problem
hits.

We had enough trouble to decode silent "fixups" which failed
miserably.

Thanks,

	tglx