linux-kernel - Re: [PATCH 3/3] e820: Add the unknown-12 Memory type (DDR3-NvDIMM)

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 for Android: free password hash cracker in your pocket

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

Date:	Mon, 09 Mar 2015 14:10:37 +0200
From:	Boaz Harrosh <boaz@...xistor.com>
To:	Andy Lutomirski <luto@...capital.net>,
	Dan Williams <dan.j.williams@...el.com>
CC:	Ingo Molnar <mingo@...hat.com>, X86 ML <x86@...nel.org>,
	linux-kernel <linux-kernel@...r.kernel.org>,
	"Roger C. Pao" <rcpao.enmotus@...il.com>,
	Thomas Gleixner <tglx@...utronix.de>,
	linux-nvdimm <linux-nvdimm@...ts.01.org>,
	"H. Peter Anvin" <hpa@...or.com>,
	Matthew Wilcox <willy@...ux.intel.com>,
	Christoph Hellwig <hch@...radead.org>,
	Ross Zwisler <ross.zwisler@...ux.intel.com>
Subject: Re: [PATCH 3/3] e820: Add the unknown-12 Memory type (DDR3-NvDIMM)

On 03/06/2015 01:09 AM, Andy Lutomirski wrote:
<>
> 
> I will be shocked if a standard of this form ever appears.  Modern
> systems *don't have e820*.  The BIOSes that are using this type 12
> hack are awful throwbacks.

So far the systems we have, with DDR4 NvDIMM(s) (Actual chips arriving soon)
still have BIOS (On by default). The BIOS was yelled "Wolfe" for so long NOW ;-)
Again these are working system in the field, who will switch them all to UEFI?

How will the UEFI present them to the system? can you point me to the relevant
code? (Or did you mean BIOS but with a different communication path than e820?)

> 
> --Andy
> 

Thanks
Boaz

--
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/