From: Andrei Borzenkov <arvidjaar@gmail.com>
To: "Elliott, Robert (Persistent Memory)" <elliott@hpe.com>,
The development of GNU GRUB <grub-devel@gnu.org>,
"dan.j.williams@intel.com" <dan.j.williams@intel.com>,
"linux-nvdimm@lists.01.org" <linux-nvdimm@lists.01.org>
Subject: Re: grub causing NVDIMMs to be treated as normal memory
Date: Thu, 26 Nov 2015 19:55:15 +0300 [thread overview]
Message-ID: <56573973.9060806@gmail.com> (raw)
In-Reply-To: <94D0CD8314A33A4D9D801C0FE68B40295BE55713@G9W0745.americas.hpqcorp.net>
26.11.2015 09:15, Elliott, Robert (Persistent Memory) пишет:
...
> ...
> mmap/efi/mmap.c:66: EFI memory region 0x880000000-0xc80000000: 14
> Unknown memory type 14, considering reserved
> mmap/efi/mmap.c:66: EFI memory region 0x1480000000-0x1a80000000: 14
> Unknown memory type 14, considering reserved
>
>
>
> This is booting a new kernel with the EFI boot stub, so I can't
> confirm that it fixes the issue of exposing the address range as
> normal, but based on the print it's probably working. I could
> add prints in grub-core/loader/i386/linux.c grub_e820_add_region
> to confirm the e820 contents at exit.
>
Thanks. If it results in wrong e820 type we have much larger problem so
I do not think it necessary.
I pushed it; as I understand this should serve as stopgap. If I get
around to implement persistent memory type would you test it? But as I
cannot tell when it happens, feel free to submit patch in the meantime :)
next prev parent reply other threads:[~2015-11-26 16:55 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-24 23:52 grub causing NVDIMMs to be treated as normal memory Elliott, Robert (Persistent Memory)
2015-11-25 14:08 ` Andrei Borzenkov
2015-11-25 16:51 ` Dan Williams
2015-11-25 17:04 ` Elliott, Robert (Persistent Memory)
2015-11-25 17:07 ` Seth Goldberg
2015-11-25 18:36 ` Andrei Borzenkov
2015-11-26 0:12 ` Elliott, Robert (Persistent Memory)
2015-11-26 3:30 ` Andrei Borzenkov
2015-11-26 6:15 ` Elliott, Robert (Persistent Memory)
2015-11-26 16:55 ` Andrei Borzenkov [this message]
2015-11-26 23:24 ` Elliott, Robert (Persistent Memory)
2015-11-27 3:58 ` Andrei Borzenkov
2015-11-27 6:22 ` Elliott, Robert (Persistent Memory)
2015-11-27 11:08 ` Vladimir 'φ-coder/phcoder' Serbinenko
2015-11-27 11:48 ` Andrei Borzenkov
2015-11-27 13:55 ` Vladimir 'φ-coder/phcoder' Serbinenko
2015-11-27 17:23 ` Andrei Borzenkov
2015-11-28 6:41 ` Elliott, Robert (Persistent Memory)
2015-12-01 0:25 ` Elliott, Robert (Persistent Memory)
2015-12-03 17:50 ` Elliott, Robert (Persistent Memory)
2015-12-08 17:15 ` Andrei Borzenkov
2015-12-09 6:37 ` Elliott, Robert (Persistent Memory)
2015-12-29 17:17 ` Vladimir 'φ-coder/phcoder' Serbinenko
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=56573973.9060806@gmail.com \
--to=arvidjaar@gmail.com \
--cc=dan.j.williams@intel.com \
--cc=elliott@hpe.com \
--cc=grub-devel@gnu.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).