WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

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

To: Akio Takebe <takebe_akio@xxxxxxxxxxxxxx>
Subject: [Xen-devel] Re: [PATCH 2/4] extract vmcoreinfo from /proc/vmcore for Xen
From: Itsuro ODA <oda@xxxxxxxxxxxxx>
Date: Mon, 31 Mar 2008 16:07:57 +0900
Cc: xen-devel@xxxxxxxxxxxxxxxxxxx, kexec@xxxxxxxxxxxxxxxxxxx
Delivery-date: Mon, 31 Mar 2008 00:08:22 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <9CC892FBA61B9Atakebe_akio@xxxxxxxxxxxxxx>
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> <9CC892FBA61B9Atakebe_akio@xxxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Hi,

On Mon, 31 Mar 2008 15:51:30 +0900
Akio Takebe <takebe_akio@xxxxxxxxxxxxxx> wrote:

> 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?

There is no significant reason now. Just reserve the posibility
to make it variable.

Thanks.
-- 
Itsuro ODA <oda@xxxxxxxxxxxxx>


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

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