Xen 
 
Home About Xen.org Xen Xen Summit Wiki Mailing List Bug Tracker Xen Downloads
 
   
 

xen-devel

[Xen-devel] Re: [PATCH 2/4] extract vmcoreinfo from /proc/vmcore for Xen

To: Itsuro ODA <oda@xxxxxxxxxxxxx>, xen-devel@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-devel] Re: [PATCH 2/4] extract vmcoreinfo from /proc/vmcore for Xen
From: Akio Takebe <takebe_akio@xxxxxxxxxxxxxx>
Date: Mon, 31 Mar 2008 15:51:30 +0900
Cc: kexec@xxxxxxxxxxxxxxxxxxx
Delivery-date: Sun, 30 Mar 2008 23:50:30 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <20080331131640.DDCF.ODA@xxxxxxxxxxxxx>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References: <20080331131640.DDCF.ODA@xxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
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


_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel

<Prev in Thread] Current Thread [Next in Thread>