linux-kernel - Re: [PATCH] apci: dump slit

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Fri, 12 Sep 2008 23:17:30 +0200
From:	Andi Kleen <andi@...stfloor.org>
To:	"H. Peter Anvin" <hpa@...or.com>
Cc:	Yinghai Lu <yhlu.kernel@...il.com>,
	Andrew Morton <akpm@...ux-foundation.org>, mingo@...e.hu,
	tglx@...utronix.de, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] apci: dump slit

"H. Peter Anvin" <hpa@...or.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@...ux.intel.com
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/