From mboxrd@z Thu Jan 1 00:00:00 1970 Return-path: Received: from g9t5009.houston.hp.com ([15.240.92.67]) by bombadil.infradead.org with esmtps (Exim 4.80.1 #2 (Red Hat Linux)) id 1ZIQqU-0001I8-KG for kexec@lists.infradead.org; Fri, 24 Jul 2015 00:28:15 +0000 Message-ID: <1437697592.3214.373.camel@hp.com> Subject: kexec, x86: Need a new e820 type support for kexec From: Toshi Kani Date: Thu, 23 Jul 2015 18:26:32 -0600 Mime-Version: 1.0 List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: "kexec" Errors-To: kexec-bounces+dwmw2=infradead.org@lists.infradead.org To: kexec@lists.infradead.org Cc: linux-nvdimm@lists.01.org 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