mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Toshi Kani <toshi.kani@hp.com>
To: Dan Williams <dan.j.williams@intel.com>
Cc: linux-nvdimm@ml01.01.org, rafael@kernel.org, neilb@suse.de,
	Lv Zheng <lv.zheng@intel.com>, "H. Peter Anvin" <hpa@zytor.com>,
	hch@lst.de, sfr@canb.auug.org.au,
	"Rafael J. Wysocki" <rafael.j.wysocki@intel.com>,
	Robert Moore <robert.moore@intel.com>,
	mingo@kernel.org, linux-acpi@vger.kernel.org,
	Jens Axboe <axboe@fb.com>, Borislav Petkov <bp@alien8.de>,
	Thomas Gleixner <tglx@linutronix.de>,
	axboe@kernel.dk, gregkh@linuxfoundation.org,
	linux-kernel@vger.kernel.org,
	Andy Lutomirski <luto@amacapital.net>,
	linux-api@vger.kernel.org, akpm@linux-foundation.org,
	Linus Torvalds <torvalds@linux-foundation.org>
Subject: Re: [PATCH v7 00/16] libnvdimm: non-volatile memory devices
Date: Wed, 24 Jun 2015 18:59:09 -0600	[thread overview]
Message-ID: <1435193949.11808.319.camel@misato.fc.hp.com> (raw)
In-Reply-To: <20150617215027.11597.61414.stgit@dwillia2-desk3.amr.corp.intel.com>

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 <toshi.kani@hp.com>

Thanks,
-Toshi


      parent reply	other threads:[~2015-06-25  0:59 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-17 23:13 Dan Williams
2015-06-17 23:13 ` [PATCH v7 01/16] e820, efi: add ACPI 6.0 persistent memory types Dan Williams
2015-06-17 23:13 ` [PATCH v7 02/16] libnvdimm, nfit: initial libnvdimm infrastructure and NFIT support Dan Williams
2015-06-17 23:13 ` [PATCH v7 03/16] libnvdimm: control character device and nvdimm_bus sysfs attributes Dan Williams
2015-06-17 23:13 ` [PATCH v7 04/16] libnvdimm, nfit: dimm/memory-devices Dan Williams
2015-06-17 23:13 ` [PATCH v7 05/16] libnvdimm: control (ioctl) messages for nvdimm_bus and nvdimm devices Dan Williams
2015-06-17 23:13 ` [PATCH v7 06/16] libnvdimm, nvdimm: dimm driver and base libnvdimm device-driver infrastructure Dan Williams
2015-06-17 23:13 ` [PATCH v7 07/16] libnvdimm, nfit: regions (block-data-window, persistent memory, volatile memory) Dan Williams
2015-06-17 23:14 ` [PATCH v7 08/16] libnvdimm: support for legacy (non-aliasing) nvdimms Dan Williams
2015-06-17 23:14 ` [PATCH v7 09/16] libnvdimm, pmem: move pmem to drivers/nvdimm/ Dan Williams
2015-07-01 13:13   ` Geert Uytterhoeven
2015-07-01 16:41     ` Dan Williams
2015-07-01 16:49       ` Geert Uytterhoeven
2015-07-01 17:24         ` Dan Williams
2015-06-17 23:14 ` [PATCH v7 10/16] libnvdimm, pmem: add libnvdimm support to the pmem driver Dan Williams
2015-06-17 23:14 ` [PATCH v7 11/16] libnvdimm, nfit: add interleave-set state-tracking infrastructure Dan Williams
2015-06-17 23:14 ` [PATCH v7 12/16] libnvdimm: namespace indices: read and validate Dan Williams
2015-06-17 23:14 ` [PATCH v7 13/16] libnvdimm: pmem label sets and namespace instantiation Dan Williams
2015-06-17 23:14 ` [PATCH v7 14/16] libnvdimm: blk labels " Dan Williams
2015-06-17 23:14 ` [PATCH v7 15/16] libnvdimm: write pmem label set Dan Williams
2015-06-17 23:14 ` [PATCH v7 16/16] libnvdimm: write blk " Dan Williams
2015-06-20 12:40 ` [PATCH v7 00/16] libnvdimm: non-volatile memory devices Stephen Rothwell
2015-06-25  0:59 ` Toshi Kani [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1435193949.11808.319.camel@misato.fc.hp.com \
    --to=toshi.kani@hp.com \
    --cc=akpm@linux-foundation.org \
    --cc=axboe@fb.com \
    --cc=axboe@kernel.dk \
    --cc=bp@alien8.de \
    --cc=dan.j.williams@intel.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=hch@lst.de \
    --cc=hpa@zytor.com \
    --cc=linux-acpi@vger.kernel.org \
    --cc=linux-api@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-nvdimm@ml01.01.org \
    --cc=luto@amacapital.net \
    --cc=lv.zheng@intel.com \
    --cc=mingo@kernel.org \
    --cc=neilb@suse.de \
    --cc=rafael.j.wysocki@intel.com \
    --cc=rafael@kernel.org \
    --cc=robert.moore@intel.com \
    --cc=sfr@canb.auug.org.au \
    --cc=tglx@linutronix.de \
    --cc=torvalds@linux-foundation.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®