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 PHC | |
Open Source and information security mailing list archives
| ||
|
Date: Fri, 19 Sep 2014 09:27:36 -0700 From: Dan Williams <dan.j.williams@...el.com> To: Jeff Moyer <jmoyer@...hat.com>, Boaz Harrosh <boaz@...xistor.com> Cc: Boaz Harrosh <openosd@...il.com>, Ross Zwisler <ross.zwisler@...ux.intel.com>, Jens Axboe <axboe@...nel.dk>, Matthew Wilcox <matthew.r.wilcox@...el.com>, linux-fsdevel <linux-fsdevel@...r.kernel.org>, "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>, linux-nvdimm@...1.01.org Subject: Re: [Linux-nvdimm] [PATCH v2] pmem: Initial version of persistent memory driver On Tue, Sep 16, 2014 at 6:54 AM, Jeff Moyer <jmoyer@...hat.com> wrote: > Boaz Harrosh <boaz@...xistor.com> writes: > >> On 09/11/2014 07:31 PM, Dan Williams wrote: >> <> >>> >>> The point I am getting at is not requiring a priori knowledge of the >>> physical memory map of a system. Rather, place holder variables to >>> enable simple dynamic discovery. >>> >> >> "simple dynamic discovery" does not yet exist and when the DDR4 NvDIMM >> will be released then we still have those DDR3 out there which will >> not work with the new discovery, which I need to support as well. > > Boaz, > > Are you telling me that vendors are shipping parts that present > themselves as E820_RAM, and that you have to manually block off the > addresses from the kernel using the kernel command line? If that is > true, then that is just insane and unsupportable. All the hardware I > have access to: > 1) does not present itself as normal memory and > 2) provides some means for discovering its address and size Jeff, Yes, agree. Boaz, The UEFI organization is in the process of defining a generic specification for platform non-volatile memory resources. Let's wait until that is publicly available before adding any new device discovery capabilities to pmem. -- 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