From mboxrd@z Thu Jan 1 00:00:00 1970 From: John Byrne Subject: Re: Live migration leaves page tables read-only? Date: Mon, 11 Dec 2006 11:55:12 -0800 Message-ID: <457DB7A0.8040803@hp.com> References: <456CD0A5.1060701@hp.com> <456CD2DC.2020201@hp.com> <8A87A9A84C201449A0C56B728ACF491E01FA12@liverpoolst.ad.cl.cam.ac.uk> <456CF5F9.7070009@hp.com> <456F6AF5.2090005@hp.com> <8A87A9A84C201449A0C56B728ACF491E01FA69@liverpoolst.ad.cl.cam.ac.uk> <457A4C68.6050800@hp.com> <8A87A9A84C201449A0C56B728ACF491E04EE29@liverpoolst.ad.cl.cam.ac.uk> <457D8EB5.2030105@sun.com> <8A87A9A84C201449A0C56B728ACF491E04EE59@liverpoolst.ad.cl.cam.ac.uk> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <8A87A9A84C201449A0C56B728ACF491E04EE59@liverpoolst.ad.cl.cam.ac.uk> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Ian Pratt Cc: xen-devel , Joe Bonasera , Christian Limpach List-Id: xen-devel@lists.xenproject.org Ian Pratt wrote: > >> Solaris implements PROT_NONE by entirely invalidating the PTE (ie. it >> becomes zero). Hence our PTEs always had either zero or have the > PRESENT >> bit set. The only exception to this was adding some fixage to allow >> for the old Xen writable page table approach which temporarily made >> the upper table non-PRESENT. >> >> So you can make not-present, but non-zero entries mean anything you > want. >> As long as it's the guest OS that creates the entries, we'll just not > do >> it. > > Just to be confirm: in Solaris there are no not-present PTE's that > contain machine addresses. > > This means we need to implement the scheme that Keir suggested to enable > the guest OS to tell xen/xc_save/restore about flags in not-present PTEs > that should trigger a m2p conversion. > > Ian > Ian, Silly me. I thought "xc_linux_save" meant what it said. I haven't paid much attention to BSD or Solaris on Xen and didn't realize that went through the same path. I'd really like to see this fixed for 3.0.4, at least for Linux, but I don't think I'm the person to implement a new "scheme" quickly to do it, but I'll try if someone wants to give me some advice on how to start. On the subject of schemes, what about support for other architectures? Is there anything we should be thinking about for supporting guests with different page sizes, for instance? John Byrne