From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from eggs.gnu.org ([140.186.70.92]:39143)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <paolo.bonzini@gmail.com>) id 1RJp4Y-0005ui-Ra
	for qemu-devel@nongnu.org; Fri, 28 Oct 2011 12:14:23 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <paolo.bonzini@gmail.com>) id 1RJp4X-0001p6-VX
	for qemu-devel@nongnu.org; Fri, 28 Oct 2011 12:14:22 -0400
Received: from mail-qy0-f173.google.com ([209.85.216.173]:59663)
	by eggs.gnu.org with esmtp (Exim 4.71)
	(envelope-from <paolo.bonzini@gmail.com>) id 1RJp4X-0001p2-Nf
	for qemu-devel@nongnu.org; Fri, 28 Oct 2011 12:14:21 -0400
Received: by qyk10 with SMTP id 10so3858989qyk.4
	for <qemu-devel@nongnu.org>; Fri, 28 Oct 2011 09:14:21 -0700 (PDT)
Sender: Paolo Bonzini <paolo.bonzini@gmail.com>
Message-ID: <4EAAD4D8.3000300@redhat.com>
Date: Fri, 28 Oct 2011 18:14:16 +0200
From: Paolo Bonzini <pbonzini@redhat.com>
MIME-Version: 1.0
References: <CAFEAcA_ykMbGV85y+jDApTC-rwYM32SiU2+BvdT=n7qUKQfi2A@mail.gmail.com>
In-Reply-To: <CAFEAcA_ykMbGV85y+jDApTC-rwYM32SiU2+BvdT=n7qUKQfi2A@mail.gmail.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Subject: Re: [Qemu-devel] ARM hosts: code_gen_alloc() maps code buffer on
	top of libc heap
List-Id: <qemu-devel.nongnu.org>
List-Unsubscribe: <https://lists.nongnu.org/mailman/options/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://lists.nongnu.org/archive/html/qemu-devel>
List-Post: <mailto:qemu-devel@nongnu.org>
List-Help: <mailto:qemu-devel-request@nongnu.org?subject=help>
List-Subscribe: <https://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=subscribe>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: David Gilbert <david.gilbert@linaro.org>, QEMU Developers <qemu-devel@nongnu.org>

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