From: tgh <tianguanhua@ncic.ac.cn>
To: Tim Deegan <Tim.Deegan@xensource.com>,
Ian Campbell <Ian.Campbell@XenSource.com>,
Ian Pratt <Ian.Pratt@cl.cam.ac.uk>
Cc: xen-devel@lists.xensource.com, Levin Johnson <levin.johnson@lycos.com>
Subject: Re: PV guest + shadow paging
Date: Mon, 22 Oct 2007 19:01:14 +0800 [thread overview]
Message-ID: <471C82FA.7040104@ncic.ac.cn> (raw)
In-Reply-To: <20070730081523.GA24708@york.uk.xensource.com>
hi
what is the auto_translated_physmap ?how does it work?and what about
other mechanisms and how many mechanisms for paging are there in xen ?
Thank you in advance
Tim Deegan 写道:
> At 07:34 +0100 on 30 Jul (1185780899), Ian Campbell wrote:
>
>> Adding
>> features = "auto_translated_physmap|writable_page_tables"
>> to the config file should add those features to the set passed to the
>> guest. I can't remember which set you would need to enable shadow mode,
>> you may have to dig round in the builder and/or hypervisor to figure it
>> out.
>>
>
> IIRC, "auto_translated_physmap" turns on both shadow mode and
> auto-translation. You could enable just the shadowing without the
> auto-translation by changing tools/libxc/xc_dom_x86.c to remove
> XEN_DOMCTL_SHADOW_ENABLE_TRANSLATE from the "mode" argument to
> xc_shadow_control().
>
>
>> However I'm not sure shadow mode (other than log-dirty) isn't broken for
>> PV guests. It's been a long time since I tried it but it was broken back
>> when the paravirt_ops tree was still trying to use it.
>>
>
> Auto-translate was (briefly) fixed at that time too, but I'm quite sure
> it doesn't work in the current tree. Some people had this kind of thing
> going for academic research projects; maybe one of them can comment.
>
> Cheers,
>
> Tim.
>
>
next prev parent reply other threads:[~2007-10-22 11:01 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-28 15:58 PV guest + shadow paging Levin Johnson
2007-07-29 21:38 ` Ian Pratt
2007-07-30 6:34 ` Ian Campbell
2007-07-30 8:15 ` Tim Deegan
2007-10-22 11:01 ` tgh [this message]
2007-10-22 11:20 ` Tim Deegan
2007-10-22 12:01 ` Samuel Thibault
2007-10-23 15:13 ` Mark Williamson
2007-10-24 4:32 ` Jeremy Fitzhardinge
2007-10-24 8:21 ` Tim Deegan
2007-10-24 10:00 ` Jeremy Fitzhardinge
2007-10-24 10:05 ` Keir Fraser
2007-10-24 18:59 ` Jeremy Fitzhardinge
2007-10-24 20:39 ` Nakajima, Jun
2007-10-24 21:47 ` Jeremy Fitzhardinge
-- strict thread matches above, loose matches on Subject: below --
2007-07-27 19:12 Levin Johnson
2007-07-27 15:54 Levin Johnson
2007-07-26 22:32 Levin Johnson
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=471C82FA.7040104@ncic.ac.cn \
--to=tianguanhua@ncic.ac.cn \
--cc=Ian.Campbell@XenSource.com \
--cc=Ian.Pratt@cl.cam.ac.uk \
--cc=Tim.Deegan@xensource.com \
--cc=levin.johnson@lycos.com \
--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.