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/
Home Products Support Community News


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 15:41:13 +0100
Cc: xen-devel@xxxxxxxxxxxxxxxxxxx
Delivery-date: Tue, 17 Apr 2007 07:40:07 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <907625E08839C4409CE5768403633E0B018E1BFE@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-topic: [Xen-devel] A different probklem with save/restore on C/S 14823.
User-agent: Microsoft-Entourage/

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

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.

 -- Keir

Xen-devel mailing list