linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Dan Williams <dan.j.williams@intel.com>
To: linux-nvdimm@lists.01.org
Cc: linux-mm@kvack.org, akpm@linux-foundation.org,
	linux-kernel@vger.kernel.org
Subject: [PATCH 0/2] devm_memremap_pages vs section-misaligned pmem
Date: Mon, 29 Feb 2016 18:56:20 -0800	[thread overview]
Message-ID: <20160301025620.12812.87268.stgit@dwillia2-desk3.amr.corp.intel.com> (raw)

Recent testing uncovered two bugs around the handling of section-misaligned
pmem regions:

1/ If the pmem section overlaps "System RAM" we need to fail the
   devm_memremap_pages() request.  Previously we would mis-detect a
   memory map like the following:

	100000000-37bffffff : System RAM
	37c000000-837ffffff : Persistent Memory

2/ If the pmem section is misaligned, but otherwise does not overlap
   memory from another zone, the altmap needs to be fixed up to add the
   alignment padding to the 'reserved ' pfns of the altmap.

---

Dan Williams (2):
      libnvdimm, pmem: fix 'pfn' support for section-misaligned namespaces
      mm: fix mixed zone detection in devm_memremap_pages


 drivers/nvdimm/pmem.c |   29 +++++++++++++++++++++++++++--
 kernel/memremap.c     |    9 ++++-----
 2 files changed, 31 insertions(+), 7 deletions(-)

--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org.  For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>

             reply	other threads:[~2016-03-01  2:56 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-01  2:56 Dan Williams [this message]
2016-03-01  2:56 ` [PATCH 1/2] libnvdimm, pmem: fix 'pfn' support for section-misaligned namespaces Dan Williams
2016-03-01  3:16   ` kbuild test robot
2016-03-01  2:56 ` [PATCH 2/2] mm: fix mixed zone detection in devm_memremap_pages Dan Williams

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=20160301025620.12812.87268.stgit@dwillia2-desk3.amr.corp.intel.com \
    --to=dan.j.williams@intel.com \
    --cc=akpm@linux-foundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=linux-nvdimm@lists.01.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).