From: "Williams, Dan J" <dan.j.williams@intel.com>
To: "torvalds@linux-foundation.org" <torvalds@linux-foundation.org>,
"akpm@linux-foundation.org" <akpm@linux-foundation.org>
Cc: "linux-nvdimm@lists.01.org" <linux-nvdimm@lists.01.org>,
"linux-acpi@vger.kernel.org" <linux-acpi@vger.kernel.org>
Subject: [GIT PULL] libnvdimm for 4.4
Date: Tue, 10 Nov 2015 09:26:27 +0000 [thread overview]
Message-ID: <1447147587.4739.7.camel@intel.com> (raw)
Hi Linus, please pull from...
git://git.kernel.org/pub/scm/linux/kernel/git/nvdimm/nvdimm
tags/libnvdimm-for-4.4
...to receive the libnvdimm update for 4.4. Outside of the new ACPI-NFIT hot-add support this pull request is more notable for what it does not contain, than what it does. There were a handful of development topics this cycle, dax get_user_pages, dax fsync, and raw block dax, that need more more iteration and will wait for 4.5.
The patches to make devm and the pmem driver NUMA aware have been in
-next for several weeks. The hot-add support has not, but is contained
to the NFIT driver and is passing unit tests. The coredump support is
straightforward and was looked over by Jeff. All of it has received a
0day build success notification across 107 configs.
The following changes since commit 7379047d5585187d1288486d4627873170d0005a:
Linux 4.3-rc6 (2015-10-18 16:08:42 -0700)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/nvdimm/nvdimm tags/libnvdimm-for-4.4
for you to fetch changes up to ab27a8d04b32b6ee8c30c14c4afd1058e8addc82:
coredump: add DAX filtering for FDPIC ELF coredumps (2015-11-09 13:29:54 -0500)
----------------------------------------------------------------
libnvdimm for 4.4:
1/ Add support for the ACPI 6.0 NFIT hot add mechanism to process
updates of the NFIT at runtime.
2/ Teach the coredump implementation how to filter out DAX mappings.
3/ Introduce NUMA hints for allocations made by the pmem driver, and as
a side effect all devm allocations now hint their NUMA node by
default.
----------------------------------------------------------------
Dan Williams (8):
x86, mm: quiet arch_add_memory()
pmem: kill memremap_pmem()
devm_memunmap: use devres_release()
devm_memremap: convert to return ERR_PTR
devm: make allocations numa aware by default
devm_memremap_pages: use numa_mem_id
pmem, memremap: convert to numa aware allocations
Merge branch 'for-4.4/hotplug' into libnvdimm-for-next
Ross Zwisler (2):
coredump: add DAX filtering for ELF coredumps
coredump: add DAX filtering for FDPIC ELF coredumps
Vishal Verma (2):
nfit: in acpi_nfit_init, break on a 0-length table
acpi: nfit: Add support for hot-add
Documentation/filesystems/proc.txt | 22 +--
arch/x86/mm/init.c | 4 +-
arch/x86/mm/init_64.c | 4 +-
drivers/acpi/nfit.c | 298 ++++++++++++++++++++++++++++++-------
drivers/acpi/nfit.h | 2 +
drivers/base/devres.c | 19 +--
drivers/nvdimm/pmem.c | 28 ++--
fs/binfmt_elf.c | 10 ++
fs/binfmt_elf_fdpic.c | 15 ++
include/linux/device.h | 16 +-
include/linux/pmem.h | 26 +---
include/linux/sched.h | 4 +-
kernel/memremap.c | 16 +-
tools/testing/nvdimm/test/nfit.c | 164 +++++++++++++++++++-
14 files changed, 494 insertions(+), 134 deletions(-)
reply other threads:[~2015-11-10 9:28 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=1447147587.4739.7.camel@intel.com \
--to=dan.j.williams@intel.com \
--cc=akpm@linux-foundation.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-nvdimm@lists.01.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.