Return-path: Received: from fgwmail5.fujitsu.co.jp ([192.51.44.35]) by bombadil.infradead.org with esmtp (Exim 4.68 #1 (Red Hat Linux)) id 1JgDqG-0000YF-Nq for kexec@lists.infradead.org; Mon, 31 Mar 2008 06:50:05 +0000 From: Akio Takebe Subject: Re: [PATCH 2/4] extract vmcoreinfo from /proc/vmcore for Xen Date: Mon, 31 Mar 2008 15:51:30 +0900 MIME-Version: 1.0 In-Reply-To: <20080331131640.DDCF.ODA@valinux.co.jp> References: <20080331131640.DDCF.ODA@valinux.co.jp> Message-Id: <9CC892FBA61B9Atakebe_akio@jp.fujitsu.com> 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-bounces@lists.infradead.org Errors-To: kexec-bounces+dwmw2=infradead.org@lists.infradead.org To: Itsuro ODA , xen-devel@lists.xensource.com Cc: kexec@lists.infradead.org Hi, Itsuro >--- include/xen/interface/kexec.h.org 2008-03-25 09:08:43.000000000 +0900 >+++ include/xen/interface/kexec.h 2008-03-25 09:12:02.000000000 +0900 >@@ -111,6 +111,10 @@ > #define KEXEC_RANGE_MA_CRASH 0 /* machine address and size of crash area */ > #define KEXEC_RANGE_MA_XEN 1 /* machine address and size of Xen itself */ > #define KEXEC_RANGE_MA_CPU 2 /* machine address and size of a CPU note */ >+#define KEXEC_RANGE_MA_VMCOREINFO 3 /* machine address and size of >vmcoreinfo */ >+ >+extern size_t vmcoreinfo_max_size_xen; Why don't you use VMCOREINFO_BYTES (4096) instead of vmcoreinfo_max_size_xen? Best Regards, Akio Takebe _______________________________________________ kexec mailing list kexec@lists.infradead.org http://lists.infradead.org/mailman/listinfo/kexec