From: Toshi Kani <toshi.kani@hp.com>
To: kexec@lists.infradead.org
Cc: linux-nvdimm@lists.01.org
Subject: kexec, x86: Need a new e820 type support for kexec
Date: Thu, 23 Jul 2015 18:26:32 -0600 [thread overview]
Message-ID: <1437697592.3214.373.camel@hp.com> (raw)
Hello,
ACPI 6.0 defines a new type in e820, AddressRangePersistentMemory (7), for
NVDIMM. On a system with NVDIMM, kexec displays the following error
message and sets it to RANGE_RESERVED as the fallback type.
Unknown type (Persistent Memory) while parsing
/sys/firmware/memmap/34/type. Please report this as bug. Using
RANGE_RESERVED now.
This new type is defined in "arch/x86/include/uapi/asm/e820.h" in 4.2-rc1
as follows.
#define E820_PMEM 7
kexec needs to know this new type, but I think its build env includes
"/usr/include/asm/e820.h", which is provided by a distribution. On Fedora
22, kernel-headers-4.0.6-300.fc22.x86_64 is the latest kernel header
package and it will take a while for 4.2 headers.
How do we handle such kernel header dependency in the kexec build env?
Thanks,
-Toshi
_______________________________________________
kexec mailing list
kexec@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kexec
next reply other threads:[~2015-07-24 0:28 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-24 0:26 Toshi Kani [this message]
2015-07-24 5:31 ` kexec, x86: Need a new e820 type support for kexec Baoquan He
2015-07-24 5:50 ` Baoquan He
2015-07-24 14:27 ` Toshi Kani
2015-07-24 14:37 ` Toshi Kani
2015-08-06 8:12 ` Baoquan He
2015-08-07 1:13 ` Toshi Kani
2015-08-18 8:34 ` Baoquan He
2015-08-18 14:55 ` Toshi Kani
2015-08-18 8:53 ` Baoquan He
2015-08-18 15:01 ` Toshi Kani
2015-08-19 2:53 ` Baoquan He
2015-08-19 5:36 ` Toshi Kani
2015-08-19 5:59 ` Baoquan He
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=1437697592.3214.373.camel@hp.com \
--to=toshi.kani@hp.com \
--cc=kexec@lists.infradead.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