From: Maxim Kuvyrkov <maxim@kugelworks.com>
To: jiji vinitha <jiji.vinitha@gmail.com>
Cc: libc-help@sourceware.org, prelink@sourceware.org
Subject: Re: Question about prelink address layout
Date: Mon, 04 Feb 2013 19:58:00 -0000 [thread overview]
Message-ID: <3E97E3E1-9615-4A98-86F6-8267678657A0@kugelworks.com> (raw)
In-Reply-To: <CADRbbMXJXbUaH6CUOrLUs8AJGU5ozg1dy7EZ7cxxi0XXVwYxqg@mail.gmail.com>
<Moved to libc-help@ and prelink@ from libc-alpha@>
On 5/02/2013, at 12:13 AM, jiji vinitha wrote:
> Hi,
> Sorry if its not proper to ask here.
The canonical list for prelink questions is prelink@sourceware.org , but libc-help@ is also OK. Libc-alpha is for glibc development.
> I have question regarding prelink virtual space address layout .
> I am using prelink in an arm linux environment.
> I can see that prelink virtual memory slot is fixed in the prelink
> source code(arch-arm.c) ie, 0x41000000-0x50000000 for arm.
> With this, prelinking was working fine for me with kernel
> configurations (CONFIG_VMSPLIT_3G = y and CONFIG_VMSPLIT_2G = y).
> But when I changed my kernel configuration to CONFIG_VMSPLIT_1G=y, I
> find that prelink checking is failed at runtime, because prelink
> expects the libaries to be loaded at 0x41xxxxxx and it is not possible
> to mmap in this address range in 1G/3G configuarion.
> Is this virtual space address layout is fixed in prelink or can it be
> configurable ?
You need to adjust mmap_base setting in arch-arm.c from 0x41000000 to a value that your 1G kernel uses to map shared libraries. AFAICT, there's no configurable setting to adjust this from command line.
--
Maxim Kuvyrkov
KugelWorks
parent reply other threads:[~2013-02-04 19:58 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <CADRbbMXJXbUaH6CUOrLUs8AJGU5ozg1dy7EZ7cxxi0XXVwYxqg@mail.gmail.com>]
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=3E97E3E1-9615-4A98-86F6-8267678657A0@kugelworks.com \
--to=maxim@kugelworks.com \
--cc=jiji.vinitha@gmail.com \
--cc=libc-help@sourceware.org \
--cc=prelink@sourceware.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 read-only IMAP folder(s) and NNTP newsgroup(s).