From: Mike Frysinger <vapier@gentoo.org>
To: Stefano Bonifazi <stefboombastic@gmail.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Re: [RFC/PATCH] elfload: add FDPIC support
Date: Mon, 24 Jan 2011 14:11:12 -0500 [thread overview]
Message-ID: <AANLkTikjQW-i2Z5a0eutQL+LWCjE2w3o0MG1rMJcC3HC@mail.gmail.com> (raw)
In-Reply-To: <4D3D7FD4.3090008@gmail.com>
On Mon, Jan 24, 2011 at 08:34, Stefano Bonifazi wrote:
> Is FDPIC something different than simply PIC code (position independent
> code)?
FDPIC ELF is the ELF PIE format used on NOMMU systems so that both the
text and data regions may be located anywhere. it is the only ELF
format supported under NOMMU systems.
> I am also trying to fight with the problem of changing the starting address
> of target code for qemu-user, and I was just moving into the option of using
> PIC target code .. but the original qemu-user load_elf_binary does not work
> on them.. and I was just about to try to edit it..
i dont believe my patch accomplishes that in any way. i will need to
force all files to be loaded at a higher address than zero for the
Blackfin arch (as the first ~4KiB is reserved for the ABI), but that
is independent of FDPIC ELF support.
-mike
next prev parent reply other threads:[~2011-01-24 19:11 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-09 8:48 [Qemu-devel] [RFC/PATCH] elfload: add FDPIC support Mike Frysinger
2011-01-09 18:20 ` Mike Frysinger
2011-01-23 19:51 ` [Qemu-devel] [PATCH] linux-user/FLAT: allow targets to override FLAT reloc processing Mike Frysinger
2011-01-23 19:54 ` Mike Frysinger
2011-01-23 19:51 ` [Qemu-devel] [PATCH v2] linux-user/elfload: add FDPIC support Mike Frysinger
2011-01-24 13:34 ` [Qemu-devel] Re: [RFC/PATCH] elfload: " Stefano Bonifazi
2011-01-24 19:11 ` Mike Frysinger [this message]
2011-01-24 21:06 ` Stefano Bonifazi
2011-01-24 21:27 ` Mike Frysinger
2011-01-24 22:07 ` Stefano Bonifazi
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=AANLkTikjQW-i2Z5a0eutQL+LWCjE2w3o0MG1rMJcC3HC@mail.gmail.com \
--to=vapier@gentoo.org \
--cc=qemu-devel@nongnu.org \
--cc=stefboombastic@gmail.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).