From: Paul Brook <paul@codesourcery.com>
To: qemu-devel@nongnu.org
Cc: Wolfgang Schildbach <Wolfgang.Schildbach@codingtechnologies.com>
Subject: Re: [Qemu-devel] qemu qemu-doc.texi
Date: Mon, 12 Jun 2006 17:47:12 +0100 [thread overview]
Message-ID: <200606121747.13346.paul@codesourcery.com> (raw)
In-Reply-To: <OF33112006.EFBB8BEE-ONC125718B.0055D73A-C125718B.00597A92@codingtechnologies.com>
> Where would I (start to) look for the reasons behind this? Is this
> something that needs to be "fixed" on the ARM side (i.e. fix the location
> where the ARM code looks for the environment)?
Look at the code in load_elf_binary that uses target_mmap to map the loadable
segments into memory. The page size I'm referring to below is the target page
size (4k for qemu-arm). target_mmap is more-or-less a wrapper around normal
mmap that deals with the corner cases and differences in page size when
host != target.
There are two issues:
- mmap requires the file offset be a multiple of the page size. This is
relatively easy to fix. If the file data is misaligned create an anonymous
mapping and pread the data.
- The code assumes the VMA of the segments after roundind to a page boundary
do not overlap. ie. a single memory page will contain data from no more than
one segment. Fixing this is more complicated and probably involves merging
the regions used by sections with "overlapping" pages.
Paul
next prev parent reply other threads:[~2006-06-12 16:47 UTC|newest]
Thread overview: 61+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-11 16:28 [Qemu-devel] qemu qemu-doc.texi Paul Brook
2006-06-12 14:09 ` Wolfgang Schildbach
2006-06-12 14:18 ` Paul Brook
2006-06-12 16:17 ` Wolfgang Schildbach
2006-06-12 16:47 ` Paul Brook [this message]
2006-06-19 14:47 ` Wolfgang Schildbach
-- strict thread matches above, loose matches on Subject: below --
2008-03-18 6:52 Aurelien Jarno
2008-03-18 6:51 Aurelien Jarno
2008-01-17 22:22 Andrzej Zaborowski
2008-01-09 12:14 Thiemo Seufer
2007-12-17 3:47 Thiemo Seufer
2007-12-17 3:38 Thiemo Seufer
2007-12-11 21:56 Andrzej Zaborowski
2007-11-26 18:46 Blue Swirl
2007-11-21 22:38 Thiemo Seufer
2007-08-25 1:40 Thiemo Seufer
2007-07-13 18:40 Thiemo Seufer
2007-07-11 21:43 Thiemo Seufer
2007-06-04 0:50 Paul Brook
2007-05-23 20:16 Paul Brook
2007-05-01 17:53 Andrzej Zaborowski
2007-02-28 16:25 Paul Brook
2007-02-19 1:23 Thiemo Seufer
2007-02-10 22:14 Thiemo Seufer
2007-02-05 19:42 Fabrice Bellard
2007-02-05 19:38 Fabrice Bellard
2006-12-11 18:35 Thiemo Seufer
2006-09-20 20:28 Fabrice Bellard
2006-09-03 17:10 Fabrice Bellard
2006-08-21 20:28 Fabrice Bellard
2006-08-21 20:26 Fabrice Bellard
2006-08-19 16:56 Fabrice Bellard
2006-08-07 21:34 Fabrice Bellard
2006-06-21 21:19 Fabrice Bellard
2006-06-16 21:48 Paul Brook
2006-06-14 18:35 Fabrice Bellard
2006-05-26 0:49 Paul Brook
2006-05-13 16:55 Paul Brook
2006-05-06 14:23 Fabrice Bellard
2006-04-23 21:57 Fabrice Bellard
2006-04-16 18:46 Paul Brook
2006-03-31 21:17 Fabrice Bellard
2006-02-20 0:35 Paul Brook
2006-02-01 21:30 Fabrice Bellard
2005-12-19 22:12 Fabrice Bellard
2005-12-18 20:11 Fabrice Bellard
2005-11-19 17:42 Fabrice Bellard
2005-07-28 22:27 Fabrice Bellard
2005-07-03 17:34 Fabrice Bellard
2005-06-05 16:48 Fabrice Bellard
2005-03-13 9:43 Fabrice Bellard
2005-02-20 19:09 Fabrice Bellard
2005-02-12 15:16 Fabrice Bellard
2005-02-12 15:02 Fabrice Bellard
2004-12-13 20:07 Fabrice Bellard
2003-10-28 1:38 Fabrice Bellard
2003-10-28 0:48 Fabrice Bellard
2003-07-13 22:37 Fabrice Bellard
2003-07-06 19:01 Fabrice Bellard
2003-06-30 23:16 Fabrice Bellard
2003-06-27 18:50 Fabrice Bellard
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=200606121747.13346.paul@codesourcery.com \
--to=paul@codesourcery.com \
--cc=Wolfgang.Schildbach@codingtechnologies.com \
--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).