qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Ian Rogers <ian.rogers@manchester.ac.uk>
To: Paul Brook <paul@codesourcery.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] QVM86, SKAS.. many modules, one vision?
Date: Mon, 09 May 2005 13:59:00 +0100	[thread overview]
Message-ID: <427F5E94.9050501@manchester.ac.uk> (raw)
In-Reply-To: <200505091339.03936.paul@codesourcery.com>

Paul Brook wrote:

>For user-mode emulation the largest chunk of address space is the translated 
>code buffer. This needs to be able to directly address the guest memory 
>space, so sharing a VM with the host qemu process isn't really a problem. We 
>just map the host qemu out of the way somewhere. This is different from 
>native UML where with SKAS you can run applications without any foreign areas 
>mapped into the guest address space.
>  
>
Yup, but if you are emulating more than just a user process (ie a whole 
OS), or you can't guarantee the security of the user process (ie it 
could go messing with the translation cache), then just mapping things 
elsewhere is just adopting the ostrich position. Multi-segments are an 
obvious way to solve this but currently there's little support in the 
OS. modify_ldt works quite well, you can hide the translation cache 
below it, but it means you can't map pages at the end of the address 
space. That's why some module support would be good.

Regards,

Ian Rogers

      reply	other threads:[~2005-05-09 13:07 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-05-09  9:09 [Qemu-devel] QVM86, SKAS.. many modules, one vision? Ian Rogers
2005-05-09 12:39 ` Paul Brook
2005-05-09 12:59   ` Ian Rogers [this message]

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=427F5E94.9050501@manchester.ac.uk \
    --to=ian.rogers@manchester.ac.uk \
    --cc=paul@codesourcery.com \
    --cc=qemu-devel@nongnu.org \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).