Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753342AbbFYA7q (ORCPT ); Wed, 24 Jun 2015 20:59:46 -0400 Received: from g1t5424.austin.hp.com ([15.216.225.54]:55609 "EHLO g1t5424.austin.hp.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752429AbbFYA7k (ORCPT ); Wed, 24 Jun 2015 20:59:40 -0400 X-Greylist: delayed 30031 seconds by postgrey-1.27 at vger.kernel.org; Wed, 24 Jun 2015 20:59:39 EDT Message-ID: <1435193949.11808.319.camel@misato.fc.hp.com> Subject: Re: [PATCH v7 00/16] libnvdimm: non-volatile memory devices From: Toshi Kani To: Dan Williams Cc: linux-nvdimm@ml01.01.org, rafael@kernel.org, neilb@suse.de, Lv Zheng , "H. Peter Anvin" , hch@lst.de, sfr@canb.auug.org.au, "Rafael J. Wysocki" , Robert Moore , mingo@kernel.org, linux-acpi@vger.kernel.org, Jens Axboe , Borislav Petkov , Thomas Gleixner , axboe@kernel.dk, gregkh@linuxfoundation.org, linux-kernel@vger.kernel.org, Andy Lutomirski , linux-api@vger.kernel.org, akpm@linux-foundation.org, Linus Torvalds Date: Wed, 24 Jun 2015 18:59:09 -0600 In-Reply-To: <20150617215027.11597.61414.stgit@dwillia2-desk3.amr.corp.intel.com> References: <20150617215027.11597.61414.stgit@dwillia2-desk3.amr.corp.intel.com> Content-Type: text/plain; charset="UTF-8" X-Mailer: Evolution 3.10.4 (3.10.4-4.fc20) Mime-Version: 1.0 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 2826 Lines: 66 On Wed, 2015-06-17 at 19:13 -0400, Dan Williams wrote: > A new sub-system in support of non-volatile memory storage devices. > > Stephen, please add libnvdimm-for-next to -next: > > git://git.kernel.org/pub/scm/linux/kernel/git/djbw/nvdimm libnvdimm-for-next > > Changes since v6 [1]: > > 1/ Deferred the patches dependent on ->rw_bytes() (BTT - stacked block > driver, BLK - mmio aperture windows driver, NFIT_TEST - unit test > infrastructure for all libnvdimm + nfit components) to their own > patchset. Make the ->rw_bytes() implementation the first patch in > that series (Christoph) > > 2/ Collected acks from Christoph and Rafael! > > 3/ Add a HAS_IOMEM dependency to CONFIG_BLK_DEV_PMEM following commit > b6f2098fb708 "block: pmem: Add dependency on HAS_IOMEM" in 4.1-rc8. > > 4/ Move libnvdimm to subsys_initcall() and move arch/x86/kernel/pmem.c > back to device_initcall(). This allows ACPI_NFIT to be built-in. > (Linda) > > 5/ Drop the ACPI_DRIVER_ALL_NOTIFY_EVENTS flag in the nfit driver. > (Rafael) > > 6/ Reference count the nvdimm_drvdata object. This fixes a bug that was > found when the unit tests were extended to test disabling an nvdimm > while a region device still had references to label data. > : > Dan Williams (16): > e820, efi: add ACPI 6.0 persistent memory types > libnvdimm, nfit: initial libnvdimm infrastructure and NFIT support > libnvdimm: control character device and nvdimm_bus sysfs attributes > libnvdimm, nfit: dimm/memory-devices > libnvdimm: control (ioctl) messages for nvdimm_bus and nvdimm devices > libnvdimm, nvdimm: dimm driver and base libnvdimm device-driver infrastructure > libnvdimm, nfit: regions (block-data-window, persistent memory, volatile memory) > libnvdimm: support for legacy (non-aliasing) nvdimms > libnvdimm, pmem: move pmem to drivers/nvdimm/ > libnvdimm, pmem: add libnvdimm support to the pmem driver > libnvdimm, nfit: add interleave-set state-tracking infrastructure > libnvdimm: namespace indices: read and validate > libnvdimm: pmem label sets and namespace instantiation. > libnvdimm: blk labels and namespace instantiation > libnvdimm: write pmem label set > libnvdimm: write blk label set We have been successfully running this patchset on our NFIT-enabled prototype systems with pmem. (Intel example _DSM, label, blk are not available for testing.) So for patch 1/16 to 4/15, and 6/16 to 10/16. Tested-by: Toshi Kani Thanks, -Toshi -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/