qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Paul Brook <paul@codesourcery.com>
To: qemu-devel@nongnu.org
Cc: Blue Swirl <blauwirbel@gmail.com>
Subject: Re: [Qemu-devel] 4G address space remapping on 64-bit host
Date: Fri, 29 Jun 2007 14:00:40 +0100	[thread overview]
Message-ID: <200706291400.40815.paul@codesourcery.com> (raw)
In-Reply-To: <f43fc5580706290241jd71cb66y99f9e6ab25e4ab3f@mail.gmail.com>

> 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?

I'd expect the overhead of SIGSEGV+mmap to be prohibitive. I don't have 
numbers to back this up, but experience with MIPS system emulation shows that 
TLB miss cost can have significant effect on overall performance.

Like Fabrice, I think this would be most useful in combination with some sort 
of hypervisor.  Somewhere on my TODO list is porting qemu to run directly as 
a paravirtual Xen DomU.  This means you can insert the guest pagetable walk 
directly into the host mmu fault handler, and do clever things with shadow 
pagetables.

I should probably get the cycle counting patches polished and applied. These 
include a mechanism for distinguishing RAM and MMIO accesses.

Paul

  parent reply	other threads:[~2007-06-29 13:00 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
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 [this message]
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=200706291400.40815.paul@codesourcery.com \
    --to=paul@codesourcery.com \
    --cc=blauwirbel@gmail.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).