qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Richard Henderson <rth@twiddle.net>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: Claudio Fontana <Claudio.Fontana@huawei.com>,
	Michael Tokarev <mjt@tls.msk.ru>, Ed Maste <emaste@freebsd.org>,
	qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Could configure generate QEMU's linker scripts?
Date: Mon, 03 Jun 2013 07:23:28 -0700	[thread overview]
Message-ID: <51ACA6E0.5090202@twiddle.net> (raw)
In-Reply-To: <CAFEAcA-E5qf+zi4nvK933vEUDPen8BrEnGMurZ3Xzy+BDq2DPg@mail.gmail.com>

On 06/02/2013 10:15 AM, Peter Maydell wrote:
> So for a new architecture how do we determine whether we need
> to fiddle with the start address or not? (More specifically,
> is aarch64 going to need a linker script or just to go in the
> configure list of "hosts which don't need one" ?)

Basically, for a non-PIE build, is there room to run the -linux-user guest
binary?  That means getting out of the way of the guest's default link
location.  If the host default link location is above 2G you may be good; above
4G is even better.


r~

  reply	other threads:[~2013-06-03 14:23 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-19 16:30 [Qemu-devel] Could configure generate QEMU's linker scripts? Ed Maste
2013-05-19 19:24 ` Paolo Bonzini
2013-05-20  0:22   ` Aurelien Jarno
2013-05-20 17:21 ` Richard Henderson
2013-05-21 17:51   ` Ed Maste
2013-05-21 18:14     ` Richard Henderson
2013-06-02 17:15   ` Peter Maydell
2013-06-03 14:23     ` Richard Henderson [this message]
2013-06-03 14:57       ` Peter Maydell
2013-06-03 15:01         ` Richard Henderson
2013-06-04 15:55         ` Claudio Fontana
2013-06-04 16:13           ` Peter Maydell
2013-06-04 16:18             ` Richard Henderson
2013-06-05  9:03             ` Claudio Fontana

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=51ACA6E0.5090202@twiddle.net \
    --to=rth@twiddle.net \
    --cc=Claudio.Fontana@huawei.com \
    --cc=emaste@freebsd.org \
    --cc=mjt@tls.msk.ru \
    --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 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).