From mboxrd@z Thu Jan 1 00:00:00 1970 Return-path: Received: from g4t3426.houston.hp.com ([15.201.208.54]) by bombadil.infradead.org with esmtps (Exim 4.80.1 #2 (Red Hat Linux)) id 1ZIe7f-0005uG-ES for kexec@lists.infradead.org; Fri, 24 Jul 2015 14:38:51 +0000 Message-ID: <1437748639.3214.379.camel@hp.com> Subject: Re: kexec, x86: Need a new e820 type support for kexec From: Toshi Kani Date: Fri, 24 Jul 2015 08:37:19 -0600 In-Reply-To: <20150724053145.GA19975@dhcp-128-28.nay.redhat.com> References: <1437697592.3214.373.camel@hp.com> <20150724053145.GA19975@dhcp-128-28.nay.redhat.com> 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: Baoquan He Cc: linux-nvdimm@ml01.01.org, kexec@lists.infradead.org On Fri, 2015-07-24 at 13:31 +0800, Baoquan He wrote: > On 07/23/15 at 06:26pm, Toshi Kani wrote: > > 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 > > It need be added in struct e820entry:include/x86/x86-linux.h and > memory_range:kexec/kexec.h and their related handling. Could you give > more details about this memory type? I downloaded a ACPI 6.0 spec but > am not familiar with this. Oh, I see. It has a locally defined header. The e820 types are defined in Table 15-312, page 683, of ACPI 6.0. Thanks, -Toshi _______________________________________________ kexec mailing list kexec@lists.infradead.org http://lists.infradead.org/mailman/listinfo/kexec