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: "Keir Fraser" <Keir.Fraser@xxxxxxxxxxxx>, "Tim Deegan" <Tim.Deegan@xxxxxxxxxxxxx>
Subject: RE: [Xen-devel] A different probklem with save/restore on C/S 14823.
From: "Petersson, Mats" <Mats.Petersson@xxxxxxx>
Date: Tue, 17 Apr 2007 17:49:42 +0200
Cc: xen-devel@xxxxxxxxxxxxxxxxxxx
Delivery-date: Tue, 17 Apr 2007 08:48:38 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <C24A9B19.D6F8%Keir.Fraser@xxxxxxxxxxxx>
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: Acd96tTWE6bfmOneEduH7gAWy6hiGQAACQawAABmlkUAADGnsAABKFp7AJZAkKAAAOryRQAfwysAAAUTVMIABlNb4AAAyGDcAAIkXnA=
Thread-topic: [Xen-devel] A different probklem with save/restore on C/S 14823.
> -----Original Message-----
> From: Keir Fraser [mailto:Keir.Fraser@xxxxxxxxxxxx] 
> Sent: 17 April 2007 15:41
> To: Petersson, Mats; Tim Deegan
> Cc: xen-devel@xxxxxxxxxxxxxxxxxxx
> Subject: Re: [Xen-devel] A different probklem with 
> save/restore on C/S 14823.
> 
> 
> 
> 
> On 17/4/07 15:26, "Petersson, Mats" <Mats.Petersson@xxxxxxx> wrote:
> 
> > Here's some debug output, hopefully sufficiently self-explanatory:
> > (XEN) hvm.c:debug_stuff:125: cr3=00000000559cf000,
> > arch.monitor_table=0000000000
> > 1c1920
> > (XEN) Pagetable walk from 0000000000000000:
> > (XEN)  L4[0x000] = 00000000559ce063 000000000001069c
> > (XEN)  L3[0x000] = 00000000559cd063 000000000001069b
> > (XEN)  L2[0x000] = 0000000000000000 ffffffffffffffff

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

> 
> Nothing mapped at address 0 according to that walk. If you 
> try to write
> address 0 immediately before the walk, and that doesn't 
> crash, yet you get
> the above walk, something weird is going on! cr3 being != 
> monitor_table is
> also rather strange, but it's worth probing into why the 
> write of address
> zero isn't crashing first.

Just to make sure, monitor_table contains a virtual address, right, and
it should be made into a physical address, what is the right way to do
that? I'm using virt_to_maddr, but I'm not entirely sure that's the
right thing to do?

--
Mats
> 
>  -- Keir
> 
> 
> 
> 
> 



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