From: Dave Chinner <david@fromorbit.com>
To: linux-kernel@vger.kernel.org
Cc: Dan Williams <dan.j.williams@intel.com>, linux-nvdimm@lists.01.org
Subject: [regression, 4.9, pmem] memmap= command line, pmem device creation behaviour changed
Date: Wed, 12 Oct 2016 10:31:51 +1100 [thread overview]
Message-ID: <20161011233151.GK23194@dastard> (raw)
Hi Dan,
I boot my DAX test machine with "memmap=8G!16G,8G!24G" on the kernel
command line to give me two 8GB pmem devices. This has worked fine
on all kernels including 4.8. I just updated that test machine to a
TOT linus kernel (4.9), and now I get a single 16GB pmem device.
i.e. the memory map the kernel generates is different. This is
what I get on boot from a 4.9 kernel:
[ 0.000000] e820: BIOS-provided physical RAM map:
[ 0.000000] BIOS-e820: [mem 0x0000000000000000-0x000000000009fbff] usable
[ 0.000000] BIOS-e820: [mem 0x000000000009fc00-0x000000000009ffff] reserved
[ 0.000000] BIOS-e820: [mem 0x00000000000f0000-0x00000000000fffff] reserved
[ 0.000000] BIOS-e820: [mem 0x0000000000100000-0x00000000bffdefff] usable
[ 0.000000] BIOS-e820: [mem 0x00000000bffdf000-0x00000000bfffffff] reserved
[ 0.000000] BIOS-e820: [mem 0x00000000feffc000-0x00000000feffffff] reserved
[ 0.000000] BIOS-e820: [mem 0x00000000fffc0000-0x00000000ffffffff] reserved
[ 0.000000] BIOS-e820: [mem 0x0000000100000000-0x000000083fffffff] usable
[ 0.000000] NX (Execute Disable) protection: active
[ 0.000000] e820: user-defined physical RAM map:
[ 0.000000] user: [mem 0x0000000000000000-0x000000000009fbff] usable
[ 0.000000] user: [mem 0x000000000009fc00-0x000000000009ffff] reserved
[ 0.000000] user: [mem 0x00000000000f0000-0x00000000000fffff] reserved
[ 0.000000] user: [mem 0x0000000000100000-0x00000000bffdefff] usable
[ 0.000000] user: [mem 0x00000000bffdf000-0x00000000bfffffff] reserved
[ 0.000000] user: [mem 0x00000000feffc000-0x00000000feffffff] reserved
[ 0.000000] user: [mem 0x00000000fffc0000-0x00000000ffffffff] reserved
[ 0.000000] user: [mem 0x0000000100000000-0x00000003ffffffff] usable
[ 0.000000] user: [mem 0x0000000400000000-0x00000007ffffffff] persistent (type 12)
[ 0.000000] user: [mem 0x0000000800000000-0x000000083fffffff] usable
On 4.8, I get two persistent (type 12) sections, each of 8GB. 4.9 is
giving me a single 16GB region. This needs to behave like a 4.8
kernel and return two persistent regions - persistent memory device
setup cannot be allowed to change from kernel to kernel. Change in
mapping and device setup like this will cause the corruption of
and/or loss of data in the persistent memory devices that have
changed shape, size or disappeared....
Cheers,
Dave.
--
Dave Chinner
david@fromorbit.com
WARNING: multiple messages have this Message-ID (diff)
From: Dave Chinner <david@fromorbit.com>
To: linux-kernel@vger.kernel.org
Cc: Dan Williams <dan.j.williams@intel.com>, linux-nvdimm@ml01.01.org
Subject: [regression, 4.9, pmem] memmap= command line, pmem device creation behaviour changed
Date: Wed, 12 Oct 2016 10:31:51 +1100 [thread overview]
Message-ID: <20161011233151.GK23194@dastard> (raw)
Hi Dan,
I boot my DAX test machine with "memmap=8G!16G,8G!24G" on the kernel
command line to give me two 8GB pmem devices. This has worked fine
on all kernels including 4.8. I just updated that test machine to a
TOT linus kernel (4.9), and now I get a single 16GB pmem device.
i.e. the memory map the kernel generates is different. This is
what I get on boot from a 4.9 kernel:
[ 0.000000] e820: BIOS-provided physical RAM map:
[ 0.000000] BIOS-e820: [mem 0x0000000000000000-0x000000000009fbff] usable
[ 0.000000] BIOS-e820: [mem 0x000000000009fc00-0x000000000009ffff] reserved
[ 0.000000] BIOS-e820: [mem 0x00000000000f0000-0x00000000000fffff] reserved
[ 0.000000] BIOS-e820: [mem 0x0000000000100000-0x00000000bffdefff] usable
[ 0.000000] BIOS-e820: [mem 0x00000000bffdf000-0x00000000bfffffff] reserved
[ 0.000000] BIOS-e820: [mem 0x00000000feffc000-0x00000000feffffff] reserved
[ 0.000000] BIOS-e820: [mem 0x00000000fffc0000-0x00000000ffffffff] reserved
[ 0.000000] BIOS-e820: [mem 0x0000000100000000-0x000000083fffffff] usable
[ 0.000000] NX (Execute Disable) protection: active
[ 0.000000] e820: user-defined physical RAM map:
[ 0.000000] user: [mem 0x0000000000000000-0x000000000009fbff] usable
[ 0.000000] user: [mem 0x000000000009fc00-0x000000000009ffff] reserved
[ 0.000000] user: [mem 0x00000000000f0000-0x00000000000fffff] reserved
[ 0.000000] user: [mem 0x0000000000100000-0x00000000bffdefff] usable
[ 0.000000] user: [mem 0x00000000bffdf000-0x00000000bfffffff] reserved
[ 0.000000] user: [mem 0x00000000feffc000-0x00000000feffffff] reserved
[ 0.000000] user: [mem 0x00000000fffc0000-0x00000000ffffffff] reserved
[ 0.000000] user: [mem 0x0000000100000000-0x00000003ffffffff] usable
[ 0.000000] user: [mem 0x0000000400000000-0x00000007ffffffff] persistent (type 12)
[ 0.000000] user: [mem 0x0000000800000000-0x000000083fffffff] usable
On 4.8, I get two persistent (type 12) sections, each of 8GB. 4.9 is
giving me a single 16GB region. This needs to behave like a 4.8
kernel and return two persistent regions - persistent memory device
setup cannot be allowed to change from kernel to kernel. Change in
mapping and device setup like this will cause the corruption of
and/or loss of data in the persistent memory devices that have
changed shape, size or disappeared....
Cheers,
Dave.
--
Dave Chinner
david@fromorbit.com
next reply other threads:[~2016-10-11 23:31 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-11 23:31 Dave Chinner [this message]
2016-10-11 23:31 ` [regression, 4.9, pmem] memmap= command line, pmem device creation behaviour changed Dave Chinner
2016-10-12 1:14 ` Dan Williams
2016-10-12 1:14 ` 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=20161011233151.GK23194@dastard \
--to=david@fromorbit.com \
--cc=dan.j.williams@intel.com \
--cc=linux-kernel@vger.kernel.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 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.