linux-kernel - Re: [PATCH v2 12/12] driver: Google Memory Console

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:	Mon, 14 Mar 2011 07:01:02 -0700
From:	Tim Hockin <thockin@...gle.com>
To:	Ingo Molnar <mingo@...e.hu>
Cc:	"H. Peter Anvin" <hpa@...nel.org>,
	Mike Waychison <mikew@...gle.com>, Greg KH <greg@...ah.com>,
	Matt Domsch <Matt_Domsch@...l.com>,
	Alan Cox <alan@...rguk.ukuu.org.uk>,
	Duncan Laurie <dlaurie@...gle.com>,
	Aaron Durbin <adurbin@...gle.com>, x86@...nel.org,
	linux-kernel@...r.kernel.org, San Mehat <san@...gle.com>
Subject: Re: [PATCH v2 12/12] driver: Google Memory Console

This same BIOS logic is used across a number of Platforms.  We could
use something like the vendor strings to trigger this code off, I
suppose, but ick.  It's already in a google/ subdir and wrapped with
CONFIG_GOOGLE_MEMCONSOLE.



On Mon, Mar 14, 2011 at 2:22 AM, Ingo Molnar <mingo@...e.hu> wrote:
>
> * H. Peter Anvin <hpa@...nel.org> wrote:
>
>> On 03/13/2011 09:58 PM, Tim Hockin wrote:
>> > "Sufficient" or not, that's how the BIOSes we've got work.  We can't
>> > retrofit that.
>>
>> Uhm... what about, say, a DMI signature?
>
> Yes - how does the dmidecode output look like on such a box?
>
> Thanks,
>
>        Ingo
>
--
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/