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

Re: [Crash-utility] Re: [Xen-devel] [PATCH] Add xen_phys_start value in

To: "Discussion list for crash utility usage, maintenance and development" <crash-utility@xxxxxxxxxx>
Subject: Re: [Crash-utility] Re: [Xen-devel] [PATCH] Add xen_phys_start value in the crash info note
From: Dave Anderson <anderson@xxxxxxxxxx>
Date: Fri, 30 May 2008 10:40:59 -0400
Cc: Itsuro ODA <oda@xxxxxxxxxxxxx>, xen-devel@xxxxxxxxxxxxxxxxxxx, kexec@xxxxxxxxxxxxxxxxxxx
Delivery-date: Fri, 30 May 2008 07:41:31 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <C465CB32.2176B%keir.fraser@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: <C465CB32.2176B%keir.fraser@xxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Thunderbird 2.0.0.14 (Windows/20080421)
Keir Fraser wrote:
On 30/5/08 06:13, "Itsuro ODA" <oda@xxxxxxxxxxxxx> wrote:

This patch makes the vmcore utilities (ex. crash, makedumpfile) be
able to get the relocation address of the xen hypervisor from a vmcore.
It is necessary for the utilities to find the data of the hypervisor
structures.

Note that this patch does not raise any comptibility issue for the
utilities (which I know) nor the other components of xen.

Since it both changes the size of the crash_info elf note, and adds the new
field in the middle of the crash_info structure, how can it not affect
compatibility?

 -- Keir

Itsuro did it that way on purpose.  It maintains backwards compatibility by
keeping the dom0_pfn_to_mfn_frame_list_list field as the last field in the
PT_NOTE.  crash doesn't know what a crash_xen_info_t structure is, but only
its old and new size.

Dave



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

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