From mboxrd@z Thu Jan 1 00:00:00 1970 From: Keir Fraser Subject: Re: Live migration leaves page tables read-only? Date: Sat, 09 Dec 2006 09:22:42 +0000 Message-ID: References: <8A87A9A84C201449A0C56B728ACF491E04EE29@liverpoolst.ad.cl.cam.ac.uk> Mime-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <8A87A9A84C201449A0C56B728ACF491E04EE29@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 , John Byrne Cc: xen-devel , Christian Limpach , Joe Bonasera List-Id: xen-devel@lists.xenproject.org On 9/12/06 8:33 am, "Ian Pratt" wrote: > Although your patch works today, it will break when we add PSE (super > page) support for PV guests as it will confuse PROT_NONE with PSE. > Assuming PROT_NONE only makes sense for L1 entries, we can probably gate > the tests on whether the page table page is an L1 or not to fix this. > > However, it does point out an issue for other OSes: Taking this patch > effectively makes Linux's PROT_NONE (flags 0x80 for a not present PTE) > part of the Xen API. We need to find out whether this is compatible with > *BSD and Solaris' use of flags for not present ptes. If _PAGE_PRESENT is clear then the other N-1 bits can be assumed available for things like swapcache info. Making assumptions about not-present PTEs is not really tenable. -- Keir