qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Paul Brook <paul@codesourcery.com>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [4600] variable dynamic translation buffer size
Date: Wed, 28 May 2008 13:55:52 +0100	[thread overview]
Message-ID: <200805281355.53574.paul@codesourcery.com> (raw)
In-Reply-To: <E1K1KnZ-00018e-0T@cvs.savannah.gnu.org>

On Wednesday 28 May 2008, Fabrice Bellard wrote:
> +        code_gen_buffer = mmap(NULL, code_gen_buffer_size,
> +                               PROT_WRITE | PROT_READ | PROT_EXEC,
> +                               flags, -1, 0);

I'd expect this to cause a significant performance regression on hosts that 
have limited branch range (i.e. everything except x86). The mmap region is 
almost never close to the application text segment, so all helper calls have 
to be indirect.

Paul

  reply	other threads:[~2008-05-28 12:56 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-05-28 12:30 [Qemu-devel] [4600] variable dynamic translation buffer size Fabrice Bellard
2008-05-28 12:55 ` Paul Brook [this message]
2008-05-28 15:11   ` Fabrice Bellard
2008-05-28 19:08 ` Blue Swirl

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=200805281355.53574.paul@codesourcery.com \
    --to=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).