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]
Message-ID: <CALCETrXQEOiPxXvx86-T2qKmpNvBJC9OaSPn30heem_PanbSog@mail.gmail.com>
Date:	Tue, 10 Mar 2015 06:19:14 -0700
From:	Andy Lutomirski <luto@...capital.net>
To:	joeyli <jlee@...e.com>
Cc:	Matthew Wilcox <willy@...ux.intel.com>,
	Boaz Harrosh <boaz@...xistor.com>,
	Ross Zwisler <ross.zwisler@...ux.intel.com>,
	Thomas Gleixner <tglx@...utronix.de>, X86 ML <x86@...nel.org>,
	Dan Williams <dan.j.williams@...el.com>,
	"Roger C. Pao" <rcpao.enmotus@...il.com>,
	Ingo Molnar <mingo@...hat.com>,
	linux-nvdimm <linux-nvdimm@...ts.01.org>,
	linux-kernel <linux-kernel@...r.kernel.org>,
	"H. Peter Anvin" <hpa@...or.com>,
	Christoph Hellwig <hch@...radead.org>
Subject: Re: [PATCH 3/3] e820: Add the unknown-12 Memory type (DDR3-NvDIMM)

On Mar 10, 2015 1:12 AM, "joeyli" <jlee@...e.com> wrote:
>
> Hi,
>
> On Mon, Mar 09, 2015 at 02:10:37PM +0200, Boaz Harrosh wrote:
> > 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?)
> >
>
> Per my understand...
>
> With EFI Boot Stub, there have setup_e820() codes in arch/x86/boot/compressed/eboot.c
> that used to transfer EFI memmap to e820 entries. Currently doesn't have any
> EFI_MEMORY_TYPE reflects to NvDIMM that will map to e820_type.
>
> I wonder what kind of EFI_MEMORY_TYPE reported by UEFI BIOS on those "shipped
> NvDIMMs motherboards", like supermicro X9DRH-iF-NV. Then we may need add code
> to setup_e820() for mapping the efi memory type to e820 type 12 region.

Nothing useful.  You can't detect the NvDIMM in EFI mode on my board
as far as I know.

Rumor has it that we'll learn more about the EFI case very soon.

--Andy

>
> > >
> > > --Andy
> > >
> >
> > Thanks
> > Boaz
> >
>
> Thanks a lot!
> Joey Lee
--
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/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ