qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Fabrice Bellard <fabrice@bellard.org>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] 4G address space remapping on 64-bit host
Date: Fri, 29 Jun 2007 12:15:25 +0200	[thread overview]
Message-ID: <4684DBBD.2090907@bellard.org> (raw)
In-Reply-To: <f43fc5580706290241jd71cb66y99f9e6ab25e4ab3f@mail.gmail.com>

Hi,

In fact, running in 64 bit is not necessary : It is simpler and more 
efficient to use kqemu (or KVM) to handle the address space remapping. 
The trick is to run the translator in the upper part or lower part of 
the 32 bit address space and to protect it with segments.

Even in 64 bit mode, using kqemu would be more efficient because it 
could handle scattered address spaces more efficiently than the host OS.

Fabrice.

Blue Swirl wrote:
> Hi,
> 
> I had an idea of mapping the full 32-bit target virtual address space
> to a 4GB area on 64-bit hosts. Then the loads and stores to normal RAM
> (except page tables, code_mem_write etc) could be made much faster,
> falling back to softmmu for other pages. The idea has come up before,
> for example in this Fabrice's message:
> http://article.gmane.org/gmane.comp.emulators.qemu/685
> 
> But I'm not sure if this would be worth the effort, the speedup would
> depend on the frequency of the loads/stores and also translation time
> vs. translated code execution times. Does anyone have good statistics
> on those?
> 
> 
> 
> 

  reply	other threads:[~2007-06-29 10:15 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-06-29  9:41 [Qemu-devel] 4G address space remapping on 64-bit host Blue Swirl
2007-06-29 10:15 ` Fabrice Bellard [this message]
2007-06-29 16:48   ` Blue Swirl
2007-06-29 20:48     ` Fabrice Bellard
2007-07-03  7:48       ` Blue Swirl
2007-06-29 13:00 ` Paul Brook
2007-06-29 17:14   ` Gwenole Beauchesne
2007-06-29 21:03     ` Paul Brook

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=4684DBBD.2090907@bellard.org \
    --to=fabrice@bellard.org \
    --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).