All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jesper Kristensen <cableman@cs.aau.dk>
To: xen-devel <xen-devel@lists.xensource.com>
Subject: Re: Status of auto_translated_mode
Date: Tue, 28 Mar 2006 16:01:41 +0200	[thread overview]
Message-ID: <442941C5.4040308@cs.aau.dk> (raw)
In-Reply-To: <A95E2296287EAD4EB592B5DEEFCE0E9D4B9F97@liverpoolst.ad.cl.cam.ac.uk>

Ian Pratt wrote:

>>After some investigation, we found that existing 
>>auto_translated_mode matches our model and then would like to 
>>know the status of this mode on xen/x86.
>>
>>1. First a background question, what's the major usage model 
>>for auto_translated_mode? 
>>    
>>
> 
>Currently, the main usage model is to support guests that haven't got
>fully paravirtualied mm systems. It's also useful for a number of
>research projects, such as vm fork, determinsitic replay etc.
>
>  
>
A quick question: Can this be enabled on a per domU basis and how is 
this done correctly? The furthest I can track it is in 
tools/libxc/xc_linux_build.c

    shadow_mode_enabled = 
test_feature_bit(XENFEAT_auto_translated_physmap, required_features);

one could of course for now hardcode shadow_mode_enabled to 1, but it 
sounds like there would be a config file option for this kind of thing. 
I can not seem to backtrack this any further. So my question is this: 
how do I enable translated shadow mode as cleanly as possible?

Best Regards,
Jesper Kristensen

  reply	other threads:[~2006-03-28 14:01 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-03-28 12:33 Status of auto_translated_mode Ian Pratt
2006-03-28 14:01 ` Jesper Kristensen [this message]
2006-03-28 14:13   ` Ian Campbell
2006-03-28 14:25   ` Christian Limpach
  -- strict thread matches above, loose matches on Subject: below --
2006-03-28 14:06 Tian, Kevin
2006-03-28 13:11 Tian, Kevin
2006-03-28 11:28 Tian, Kevin

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=442941C5.4040308@cs.aau.dk \
    --to=cableman@cs.aau.dk \
    --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.