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] A different probklem with save/restore on C/S 14823.

To: "Petersson, Mats" <Mats.Petersson@xxxxxxx>, Tim Deegan <Tim.Deegan@xxxxxxxxxxxxx>
Subject: Re: [Xen-devel] A different probklem with save/restore on C/S 14823.
From: Keir Fraser <Keir.Fraser@xxxxxxxxxxxx>
Date: Tue, 17 Apr 2007 17:16:50 +0100
Cc: xen-devel@xxxxxxxxxxxxxxxxxxx
Delivery-date: Tue, 17 Apr 2007 09:15:40 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <907625E08839C4409CE5768403633E0B018E1BFF@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>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: Acd96tTWE6bfmOneEduH7gAWy6hiGQAACQawAABmlkUAADGnsAABKFp7AJZAkKAAAOryRQAfwysAAAUTVMIABlNb4AAAyGDcAAIkXnAAATKDdw==
Thread-topic: [Xen-devel] A different probklem with save/restore on C/S 14823.
User-agent: Microsoft-Entourage/11.3.3.061214
On 17/4/07 16:49, "Petersson, Mats" <Mats.Petersson@xxxxxxx> wrote:

> Got another one that looks like this:
> (XEN) About to write to NULL
> (XEN) Done
> (XEN) Pagetable walk from 0000000000000000:
> (XEN)  L4[0x000] = 00000000472ea063 000000000000f6ea
> (XEN)  L3[0x000] = 00000000472e9063 000000000000f6e9
> (XEN)  L2[0x000] = 00000000472e8067 000000000000f6e8
> (XEN)  L1[0x000] = 00000000485ae067 0000000000000000

Okay, I think this is expected behaviour from what I can understand of the
monitor_table logic. I'll sort it out with Tim.

 Thanks,
 Keir



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