From: Peter Bergner <bergner@vnet.ibm.com>
To: linux-ia64@vger.kernel.org
Subject: Re: [Linux-ia64] IA64 ELF header question...
Date: Thu, 24 Jan 2002 13:51:48 +0000 [thread overview]
Message-ID: <marc-linux-ia64-105590698805926@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-105590698805902@msgid-missing>
Cary Coutant wrote:
> PA-RISC also uses function descriptors. On HP-UX, for both PA-RISC and
> IA-64, the e_entry field is the address of the code entry point itself,
> rather than the address of a function descriptor. Our dynamic loader
> initializes its own gp value, and when it's time for the dynamic loader
> to call the application's entry point, it knows what the gp value should
> be, so we don't need a function descriptor.
This looks also to be the case for Linux/IA64 (from what I gathered from
looking at the IA64 kernel and GLIBC source). Changing our ABI to match
this doesn't look promising, as we're not the only OS using this ABI.
This means I'll need to modify the kernel to reloc our function
descriptor (FD)
entries. The only problem is, I don't have enough information in
start_thread
to know whether I need to reloc the FD entries or not. Seems like I'll
need
to place some code in fs/binfmt_elf.c to gather up the information
needed
to perform the reloc's in start_thread.
Note I don't really want to reloc the function descriptor entries, just
the values I copy out of the entries as I stuff them into my pt_regs
struct.
Peter
prev parent reply other threads:[~2002-01-24 13:51 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-21 18:48 [Linux-ia64] IA64 ELF header question Peter Bergner
2002-01-22 22:26 ` Cary Coutant
2002-01-24 13:51 ` Peter Bergner [this message]
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=marc-linux-ia64-105590698805926@msgid-missing \
--to=bergner@vnet.ibm.com \
--cc=linux-ia64@vger.kernel.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