From: Paul Brook <paul@codesourcery.com>
To: Alexander Graf <agraf@suse.de>
Cc: Peter Maydell <peter.maydell@linaro.org>,
Riku Voipio <riku.voipio@iki.fi>,
"dvaleev@suse.com" <dvaleev@suse.com>,
"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>,
Richard Henderson <rth@twiddle.net>
Subject: Re: [Qemu-devel] [PATCH] PPC: Fix linker scripts on ppc hosts
Date: Wed, 14 Dec 2011 00:30:44 +0000 [thread overview]
Message-ID: <201112140030.45213.paul@codesourcery.com> (raw)
In-Reply-To: <218892C4-3E2C-4278-B0E9-D9FF61E2FCB9@suse.de>
> >>>>> When compiling qemu statically with multilib on PPC, we hit the
> >>>>> same issue that commit 845f2c2812d9ed24b36c02a3d06ee83aeafe8b49
> >>>>> is fixing. Do the same here.
> >>>>
> >>>> How many of these ld files can we get rid of if we use -Ttext-segment
> >>>> instead? Generally all we're really caring about is moving the program
> >>>> base around so that it doesn't conflict with the address space we want
> >>>> to use for the client.
> >>>
> >>> Now that we have the automatic GUEST_BASE stuff you shouldn't need to
> >>> do either.
> >>
> >> If it was working, yes :)
> >
> > What doesn't work? I put a fair amout of effort into making it
> > automatically pick a sensible value. If there's some reason that won't
> > work then you probably want to be using -R.
>
> IIRC mmap'ing files would break with 32-on-64, but I'd have to check up on
> the details. I ended up passing MAP_32BIT to all linux-user mmap calla for
> 32-on-x86_64, but that doesn't work with -R.
Hmm, I thought we'd fixed that. It's the reason h2g_valid exists.
Either way it should definitely work with -R. I specifically added that to
avoid problems with the host mmap picking inconvenient addresse.
MAP_32BIT is an unconsionable hack, and doesn't exist on other 64-bit hosts.
Paul
next prev parent reply other threads:[~2011-12-14 0:30 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-12 21:36 [Qemu-devel] [PATCH] PPC: Fix linker scripts on ppc hosts Alexander Graf
2011-12-13 0:55 ` Richard Henderson
2011-12-13 1:05 ` Alexander Graf
2011-12-13 6:19 ` Paul Brook
2011-12-13 7:45 ` Alexander Graf
2011-12-13 16:31 ` Paul Brook
2011-12-13 21:59 ` Alexander Graf
2011-12-14 0:30 ` Paul Brook [this message]
2011-12-14 1:43 ` Alexander Graf
2011-12-14 2:24 ` Paul Brook
2011-12-20 16:17 ` Peter Maydell
2011-12-20 16:29 ` Alexander Graf
2011-12-20 16:33 ` Peter Maydell
2011-12-20 16:43 ` Alexander Graf
2011-12-14 8:53 ` Peter Maydell
2011-12-14 12:04 ` Paul Brook
2011-12-14 12:21 ` Peter Maydell
2011-12-14 17:34 ` Paul Brook
2011-12-13 8:13 ` 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=201112140030.45213.paul@codesourcery.com \
--to=paul@codesourcery.com \
--cc=agraf@suse.de \
--cc=dvaleev@suse.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=riku.voipio@iki.fi \
--cc=rth@twiddle.net \
/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).