From: Richard Henderson <rth@twiddle.net>
To: Prashant Vaibhav <qemu@mercurysquad.com>
Cc: Alexander Graf <agraf@suse.de>,
"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] Loading ELF binaries with very high base addresses
Date: Tue, 12 Jul 2011 11:34:57 -0700 [thread overview]
Message-ID: <4E1C93D1.8030409@twiddle.net> (raw)
In-Reply-To: <8AA1C177-82E3-4783-96C6-A3728A097872@suse.de>
On 07/12/2011 09:43 AM, Alexander Graf wrote:
> For now, just force the mapping to somewhere mappable :)
Unfortunately, I can tell you that there is no such place.
The text segment is mapped by default at 0x4000000000000000
and the data segment is by default mapped at 0x6000000000000000.
If you set guest_base = 0xc000000000000000, which remaps
the text segment to 0, then the data segment will still be
at 0x2000000000000000, which x86_64 still cannot represent.
If you hack the address mapping routines to simply drop the
high bits, then the text and data segments will map on top
of one another. You can well imagine how well that will work.
The *only* way to solve this is with softmmu.
r~
next prev parent reply other threads:[~2011-07-12 18:35 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-12 15:29 [Qemu-devel] Loading ELF binaries with very high base addresses Prashant Vaibhav
2011-07-12 16:43 ` Alexander Graf
2011-07-12 18:34 ` Richard Henderson [this message]
2011-07-12 20:58 ` Prashant Vaibhav
2011-07-12 21:32 ` Richard Henderson
2011-07-13 1:14 ` Prashant Vaibhav
2011-07-12 19:17 ` Peter Maydell
-- strict thread matches above, loose matches on Subject: below --
2011-07-12 17:14 "Marc Lörner"
2011-07-12 18:19 ` Prashant Vaibhav
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=4E1C93D1.8030409@twiddle.net \
--to=rth@twiddle.net \
--cc=agraf@suse.de \
--cc=qemu-devel@nongnu.org \
--cc=qemu@mercurysquad.com \
/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).