From: Paolo Bonzini <pbonzini@redhat.com>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: David Gilbert <david.gilbert@linaro.org>,
QEMU Developers <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] ARM hosts: code_gen_alloc() maps code buffer on top of libc heap
Date: Fri, 28 Oct 2011 18:14:16 +0200 [thread overview]
Message-ID: <4EAAD4D8.3000300@redhat.com> (raw)
In-Reply-To: <CAFEAcA_ykMbGV85y+jDApTC-rwYM32SiU2+BvdT=n7qUKQfi2A@mail.gmail.com>
On 10/28/2011 04:32 PM, Peter Maydell wrote:
>
> I suspect we need to drop the MAP_FIXED requirement and
> fix the TCG code to cope with emitting code for longer-range
> branches for calls to host fns etc (calls/branches within the
> generated code should be ok to keep using the short-range
> branch insn I think). There is already no guarantee that
> the generated code and the host C code are within short
> branch range of each other...
Does USE_STATIC_CODE_GEN_BUFFER fix it? Do you know why "Currently it
is not recommended to allocate big chunks of data in user mode"?
Paolo
next prev parent reply other threads:[~2011-10-28 16:14 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-28 14:32 [Qemu-devel] ARM hosts: code_gen_alloc() maps code buffer on top of libc heap Peter Maydell
2011-10-28 16:14 ` Paolo Bonzini [this message]
2011-10-28 16:32 ` Peter Maydell
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=4EAAD4D8.3000300@redhat.com \
--to=pbonzini@redhat.com \
--cc=david.gilbert@linaro.org \
--cc=peter.maydell@linaro.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 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.