From: "Williams, Dan J" <dan.j.williams@intel.com>
To: "torvalds@linux-foundation.org" <torvalds@linux-foundation.org>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-nvdimm@lists.01.org" <linux-nvdimm@lists.01.org>
Subject: [GIT PULL] libnvdimm fixes for 4.20-rc6
Date: Sun, 9 Dec 2018 06:18:02 +0000 [thread overview]
Message-ID: <705f91734ecb4ffbddb2470a797541c876745c6e.camel@intel.com> (raw)
Hi Linus, please pull from:
git://git.kernel.org/pub/scm/linux/kernel/git/nvdimm/nvdimm tags/libnvdimm-fixes-4.20-rc6
...to receive a regression fix for the Address Range Scrub
implementation, yes another one, and support for platforms that
misalign persistent memory relative to the Linux memory hotplug section
constraint. Longer term, support for sub-section memory hotplug would
alleviate alignment waste, but until then this hack allows a 'struct
page' memmap to be established for these misaligned memory regions.
These have all appeared in a -next release, and thanks to Patrick for
reporting and testing the alignment padding fix.
---
The following changes since commit 9ff01193a20d391e8dbce4403dd5ef87c7eaaca6:
Linux 4.20-rc3 (2018-11-18 13:33:44 -0800)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/nvdimm/nvdimm tags/libnvdimm-fixes-4.20-rc6
for you to fetch changes up to b5fd2e00a60248902315fb32210550ac3cb9f44c:
acpi/nfit: Fix user-initiated ARS to be "ARS-long" rather than "ARS-short" (2018-12-05 14:16:13 -0800)
----------------------------------------------------------------
libnvdimm fixes 4.20-rc6
* Unless and until the core mm handles memory hotplug units smaller than
a section (128M), persistent memory namespaces must be padded to
section alignment. The libnvdimm core already handled section
collision with "System RAM", but some configurations overlap
independent "Persistent Memory" ranges within a section, so additional
padding injection is added for that case.
* The recent reworks of the ARS (address range scrub) state machine to
reduce the number of state flags inadvertantly missed a conversion of
acpi_nfit_ars_rescan() call sites. Fix the regression whereby
user-requested ARS results in a "short" scrub rather than a "long"
scrub.
* Fixup the unit tests to handle / test the 128M section alignment of
mocked test resources.
----------------------------------------------------------------
Dan Williams (3):
tools/testing/nvdimm: Align test resources to 128M
libnvdimm, pfn: Pad pfn namespaces relative to other regions
acpi/nfit: Fix user-initiated ARS to be "ARS-long" rather than "ARS-short"
drivers/acpi/nfit/core.c | 2 +-
drivers/nvdimm/nd-core.h | 2 ++
drivers/nvdimm/pfn_devs.c | 64 +++++++++++++++++++++++-----------------
drivers/nvdimm/region_devs.c | 41 +++++++++++++++++++++++++
tools/testing/nvdimm/test/nfit.c | 35 ++++++++++++++++++++--
5 files changed, 114 insertions(+), 30 deletions(-)
next reply other threads:[~2018-12-09 6:18 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-09 6:18 Williams, Dan J [this message]
2018-12-09 18:50 ` [GIT PULL] libnvdimm fixes for 4.20-rc6 pr-tracker-bot
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=705f91734ecb4ffbddb2470a797541c876745c6e.camel@intel.com \
--to=dan.j.williams@intel.com \
--cc=linux-kernel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).