From: Keir Fraser <keir@xensource.com>
To: Ian Pratt <m+Ian.Pratt@cl.cam.ac.uk>, John Byrne <john.l.byrne@hp.com>
Cc: xen-devel <xen-devel@lists.xensource.com>,
Christian Limpach <Christian.Limpach@xensource.com>,
Joe Bonasera <joe.bonasera@sun.com>
Subject: Re: Live migration leaves page tables read-only?
Date: Sat, 09 Dec 2006 09:48:10 +0000 [thread overview]
Message-ID: <C1A036DA.596A%keir@xensource.com> (raw)
In-Reply-To: <C1A033C0.5966%keir@xensource.com>
On 9/12/06 9:34 am, "Keir Fraser" <keir@xensource.com> wrote:
>> 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.
>
> Speaking more constructively we could have a pte_active_mask communicated
> via elfnote or xenbus (or some other way) which the tools would apply to
> PTEs to determine if they contain an MFN. Default would be 0x1.
Or we could apply the special case only for images with the OS elfnote set
to 'linux', if all Linux kernels have the same PROT_NONE definition.
With any of these solutions, the problem is how to communicate the flag or
mask to xc_linux_save/xc_linux_restore, and how to propagate it across
save/restore (i.e., how is it represented in a saved image?).
-- Keir
next prev parent reply other threads:[~2006-12-09 9:48 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-29 0:13 Live migration leaves page tables read-only? John Byrne
2006-11-29 0:22 ` John Byrne
2006-11-29 1:36 ` Ian Pratt
2006-11-29 2:52 ` John Byrne
2006-11-29 7:42 ` Keir Fraser
2006-11-29 16:49 ` John Byrne
2006-11-30 23:36 ` John Byrne
2006-12-01 1:13 ` Ian Pratt
2006-12-09 5:40 ` John Byrne
2006-12-09 5:44 ` John Byrne
2006-12-09 8:33 ` Ian Pratt
2006-12-09 9:22 ` Keir Fraser
2006-12-09 9:34 ` Keir Fraser
2006-12-09 9:48 ` Keir Fraser [this message]
2006-12-11 17:00 ` Joe Bonasera
2006-12-11 18:29 ` Ian Pratt
2006-12-11 19:55 ` John Byrne
2006-12-11 21:30 ` Joe Bonasera
2007-01-14 4:11 ` John Byrne
2007-01-14 8:21 ` Ian Pratt
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=C1A036DA.596A%keir@xensource.com \
--to=keir@xensource.com \
--cc=Christian.Limpach@xensource.com \
--cc=joe.bonasera@sun.com \
--cc=john.l.byrne@hp.com \
--cc=m+Ian.Pratt@cl.cam.ac.uk \
--cc=xen-devel@lists.xensource.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.