From: Andi Kleen <andi@firstfloor.org>
To: "H. Peter Anvin" <hpa@zytor.com>
Cc: Yinghai Lu <yhlu.kernel@gmail.com>,
Andrew Morton <akpm@linux-foundation.org>,
mingo@elte.hu, tglx@linutronix.de, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] apci: dump slit
Date: Fri, 12 Sep 2008 23:17:30 +0200 [thread overview]
Message-ID: <87y71xqd1x.fsf@basil.nowhere.org> (raw)
In-Reply-To: <48CACD68.4050006@zytor.com> (H. Peter Anvin's message of "Fri, 12 Sep 2008 13:13:28 -0700")
"H. Peter Anvin" <hpa@zytor.com> writes:
> Yinghai Lu wrote:
>> to see how wrong could be set by BIOS.
>>
>
> I'm starting to think that all this dumping of ACPI information needs
> to be put under a command-line option.
The majority of ACPI information at boot is related to interrupt
routing. While interrupt routing isn't that big a problem anymore
it used to be and when something goes wrong with it you often
have a non booting system. I think it's safer to dump
it by default.
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.
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.
-Andi
---
ak@linux.intel.com
next prev parent reply other threads:[~2008-09-12 21:17 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-12 18:17 [PATCH] apci: dump slit Yinghai Lu
2008-09-12 19:20 ` Andrew Morton
2008-09-12 19:29 ` Yinghai Lu
2008-09-12 20:13 ` H. Peter Anvin
2008-09-12 21:17 ` Andi Kleen [this message]
2008-09-12 21:44 ` Thomas Gleixner
2008-09-12 21:11 ` Andi Kleen
2008-09-12 21:19 ` Thomas Gleixner
2008-09-12 21:30 ` Andi Kleen
2008-09-12 21:41 ` Matt Keenan
2008-09-12 21:49 ` Thomas Gleixner
2008-09-12 22:14 ` Andi Kleen
2008-09-12 21:54 ` Yinghai Lu
2008-09-12 22:29 ` Andi Kleen
2008-09-14 11:22 ` Pavel Machek
2008-09-14 12:26 ` Ingo Molnar
2008-09-14 15:59 ` Pavel Machek
2008-09-14 16:00 ` Pavel Machek
2008-09-14 16:04 ` Ingo Molnar
2008-09-14 18:13 ` Yinghai Lu
2008-09-18 18:26 ` Andi Kleen
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=87y71xqd1x.fsf@basil.nowhere.org \
--to=andi@firstfloor.org \
--cc=akpm@linux-foundation.org \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=tglx@linutronix.de \
--cc=yhlu.kernel@gmail.com \
/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