From: John Byrne <john.l.byrne@hp.com>
To: Ian Pratt <m+Ian.Pratt@cl.cam.ac.uk>
Cc: xen-devel <xen-devel@lists.xensource.com>,
Joe Bonasera <joe.bonasera@sun.com>,
Christian Limpach <Christian.Limpach@xensource.com>
Subject: Re: Live migration leaves page tables read-only?
Date: Mon, 11 Dec 2006 11:55:12 -0800 [thread overview]
Message-ID: <457DB7A0.8040803@hp.com> (raw)
In-Reply-To: <8A87A9A84C201449A0C56B728ACF491E04EE59@liverpoolst.ad.cl.cam.ac.uk>
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
next prev parent reply other threads:[~2006-12-11 19:55 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
2006-12-11 17:00 ` Joe Bonasera
2006-12-11 18:29 ` Ian Pratt
2006-12-11 19:55 ` John Byrne [this message]
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=457DB7A0.8040803@hp.com \
--to=john.l.byrne@hp.com \
--cc=Christian.Limpach@xensource.com \
--cc=joe.bonasera@sun.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.