From: Dan Williams <dan.j.williams@intel.com>
To: Oren Berman <oren@lightbitslabs.com>
Cc: "linux-nvdimm@lists.01.org" <linux-nvdimm@lists.01.org>
Subject: Re: Detecting NUMA per pmem
Date: Wed, 10 Jan 2018 08:38:40 -0800 [thread overview]
Message-ID: <CAPcyv4hOqiq8LjHv7Qtt5J1SxJouiwvJVvAS9WgzWbcnoWEeQw@mail.gmail.com> (raw)
In-Reply-To: <CAN=ZobQyy3taNhB_sXjeeUdWx0xP1aL3icr5_+ANFmBH+4Ge5A@mail.gmail.com>
On Wed, Jan 10, 2018 at 7:23 AM, Oren Berman <oren@lightbitslabs.com> wrote:
> Now to all of the forum
>
> Hi Dan
>
> Thanks we are going to try this.
>
> Can you explain why this can cause this issue - is the NVDIMM memory space
> also being randomized?
> Is it done during runtime?
>
Yes, kaslr randomizes the direct map. We have seen problems with it in
the past relative to setting up pmem mappings. We fixed one such bug
with this commit:
fc5f9d5f151c x86/mm: Fix boot crash caused by incorrect loop count
calculation in sync_global_pgds()
...but it appears we may have another bug in this area.
_______________________________________________
Linux-nvdimm mailing list
Linux-nvdimm@lists.01.org
https://lists.01.org/mailman/listinfo/linux-nvdimm
next prev parent reply other threads:[~2018-01-10 16:33 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAN=ZobSmQ97gRKFaho7DPvXVD18W4145JfTQ5Ncf80Tw17fkGA@mail.gmail.com>
[not found] ` <20171020162227.GA8576@linux.intel.com>
2017-10-22 11:33 ` Detecting NUMA per pmem Oren Berman
2017-10-22 13:52 ` Dan Williams
2017-12-27 18:53 ` Oren Berman
2017-12-28 9:14 ` Dan Williams
2017-12-28 10:03 ` Oren Berman
2017-12-28 18:16 ` Dan Williams
2017-12-31 8:23 ` Yigal Korman
2018-01-09 22:25 ` Oren Berman
2018-01-09 23:05 ` Dan Williams
2018-01-10 7:21 ` Oren Berman
2018-01-10 13:13 ` Oren Berman
2018-01-10 14:51 ` Dan Williams
2018-01-10 15:23 ` Oren Berman
2018-01-10 16:38 ` Dan Williams [this message]
2018-01-10 17:41 ` Oren Berman
2018-06-29 5:17 ` Oren Berman
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=CAPcyv4hOqiq8LjHv7Qtt5J1SxJouiwvJVvAS9WgzWbcnoWEeQw@mail.gmail.com \
--to=dan.j.williams@intel.com \
--cc=linux-nvdimm@lists.01.org \
--cc=oren@lightbitslabs.com \
/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).