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] [Solved] the cause of invalid entries in physical-to-mac

To: xen-devel@xxxxxxxxxxxxxxxxxxx
Subject: Re: [Xen-devel] [Solved] the cause of invalid entries in physical-to-machine table
From: Stephan Creutz <stephan.creutz@xxxxxxxxxxxxxxxxx>
Date: Tue, 6 Feb 2007 13:22:53 +0100
Delivery-date: Tue, 06 Feb 2007 04:22:45 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <20070125185310.47757560.stephan.creutz@xxxxxxxxxxxxxxxxx>
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: <20070125185310.47757560.stephan.creutz@xxxxxxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
On Thu, 25 Jan 2007 18:53:10 +0100
Stephan Creutz <stephan.creutz@xxxxxxxxxxxxxxxxx> wrote:
> I am currently trying to understand the details of live-migration by
> looking at the code xc_linux_save.c in libxc and writing a simple
> program to make things more clear.
> 
> The program memory maps all mfns which are used for the pfn to mfn
> list, goes through all pfns, resolves each pfn to a mfn and tries to
> memory map each of them to read its content. One thing I noticed are
> invalid physical-to-machine list entries (list entries where the
> resulting mfn equals INVALID_P2M_ENTRY and xc_map_foreign_range
> failes). I wonder what are the possible causes for invalid entries in
> the pfn to mfn list. One cause I can think of are pfns that are
> reserved for Xen itself, but what are the other ones?

I used Xen 3.0.3-1 (which forgot to mention in the original mail). After
Upgrading to version 3.0.4-1 the invalid entries disappeared.

Stephan

Attachment: pgpSGrqBBBI1I.pgp
Description: PGP signature

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel
<Prev in Thread] Current Thread [Next in Thread>
  • Re: [Xen-devel] [Solved] the cause of invalid entries in physical-to-machine table, Stephan Creutz <=