[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 17:35:20 +0100
  • Cc: xen-devel@xxxxxxxxxxxxxxxxxxx
  • Delivery-date: Tue, 17 Apr 2007 09:34:14 -0700
  • List-id: Xen developer discussion <xen-devel.lists.xensource.com>
  • Thread-index: Acd96tTWE6bfmOneEduH7gAWy6hiGQAACQawAABmlkUAADGnsAABKFp7AJZAkKAAAOryRQAfwysAAAUTVMIABlNb4AAAyGDcAAIkXnAAATKDdwAAFYywAACP3Jc=
  • Thread-topic: [Xen-devel] A different probklem with save/restore on C/S 14823.

On 17/4/07 17:22, "Petersson, Mats" <Mats.Petersson@xxxxxxx> wrote:

> So just to confirm, you think that this should be fixed (i.e. the
> null-access should not be possible), but I should test the latest to see
> if save/restore works better there, as there is no need to search
> further for the actual cause of the "write to zero is possible" problem?

Yeah, I'm pretty sure this behaviour is intentional. Slot 0 of the
monitor_table top-level table points at a shadow linear map. So feel free to
upgrade your tree now -- no more tracking down to be done. :-)

 -- Keir



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


 


Rackspace

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