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: [Xen-devel] xc_get_pfn_list() creates broken core files

To: John Levon <levon@xxxxxxxxxxxxxxxxx>, Keir Fraser <keir@xxxxxxxxxxxxx>
Subject: Re: [Xen-devel] xc_get_pfn_list() creates broken core files
From: Keir Fraser <keir@xxxxxxxxxxxxx>
Date: Thu, 23 Nov 2006 23:33:59 +0000
Cc: xen-devel@xxxxxxxxxxxxxxxxxxx
Delivery-date: Thu, 23 Nov 2006 15:34:11 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <20061123205257.GA4041@xxxxxxxxxxxxxxxxxxxx>
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>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: AccPV9mPGEBvzHtLEdu2gAANk04WTA==
Thread-topic: [Xen-devel] xc_get_pfn_list() creates broken core files
User-agent: Microsoft-Entourage/11.2.5.060620


On 23/11/06 8:52 pm, "John Levon" <levon@xxxxxxxxxxxxxxxxx> wrote:

> Use the guest's own p2m table instead of xc_get_pfn_list(), which cannot
> handle PFNs with no MFN.
> Dump a zeroed page for PFNs with no MFN.
> Clearly deprecate xc_get_pfn_list().
> Do not include a P2M table with HVM domains.
> Refuse to dump HVM until we can map its pages with PFNs.
> 
> Signed-off-by: John Levon <john.levon@xxxxxxx>

Rather than dump zero pages we could save a PFN-GMFN pair for each dumped
page. These can all go at the start of the core file in place of the p2m.
The dumped pages will then be in order of the PFN-GMFN pairs.

For a PV guest PFN=pseudophys, GMFN=machine (real). For an HVM guest
PFN=GMFN=pseudophys.

Finding max_pfn for a HVM guest is a bit tricky right now: we could add a
hypercall to read it out from Xen, or we could have Xen maintain the
shared_info max_pfn field.

 -- Keir


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