[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.
> -----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
|
Lists.xenproject.org is hosted with RackSpace, monitoring our |