[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Xen-devel] A different probklem with save/restore on C/S 14823.

  • To: "Petersson, Mats" <Mats.Petersson@xxxxxxx>, Tim Deegan <Tim.Deegan@xxxxxxxxxxxxx>
  • 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
  • List-id: Xen developer discussion <xen-devel.lists.xensource.com>
  • Thread-index: Acd96tTWE6bfmOneEduH7gAWy6hiGQAACQawAABmlkUAADGnsAABKFp7AJZAkKAAAOryRQAfwysAAAUTVMIABlNb4AAAyGDc
  • Thread-topic: [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

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



Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.