From: David Daney <ddaney@caviumnetworks.com>
To: naveen yadav <yad.naveen@gmail.com>
Cc: Ralf Baechle <ralf@linux-mips.org>,
Himanshu Aggarwal <lkml.himanshu@gmail.com>,
kernelnewbies@nl.linux.org, linux-mips@linux-mips.org
Subject: Re: page size change on MIPS
Date: Fri, 04 Feb 2011 09:25:10 -0800 [thread overview]
Message-ID: <4D4C3676.50802@caviumnetworks.com> (raw)
In-Reply-To: <AANLkTimCfioamQWGeRCFFN=OoWE7-PhGs2tCH+_9H=HO@mail.gmail.com>
On 02/03/2011 08:16 PM, naveen yadav wrote:
> Hi, I am adding readelf info also .
>
> mips-linux-gnu-readelf -S squashfs-root/bin/busybox
> There are 35 section headers, starting at offset 0x174290:
>
Section headers are not relevant to any of this. You need to look at
the program headers. Try 'readelf -l'
David Daney
[...]
>>
>>
>> On Mon, Jan 31, 2011 at 6:38 PM, Ralf Baechle<ralf@linux-mips.org> wrote:
>>> On Sun, Jan 30, 2011 at 08:32:43PM +0530, Himanshu Aggarwal wrote:
>>>
>>>> Why should the application or the toolchains depend on pagesize? I am
>>>> not very clear on this. Can someone explain it?
>>>
>>> To allow loading directly with mmap the executable file's layout must
>>> be such that it's it's segments are on offsets that are a multiple of
>>> the page size so in turn the linker must know that alignment.
>>>
>>> Ralf
>>>
>>
>
prev parent reply other threads:[~2011-02-04 17:25 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-24 15:02 page size change on MIPS naveen yadav
2011-01-24 18:56 ` David Daney
2011-01-24 19:13 ` Kevin D. Kissell
2011-01-27 14:55 ` naveen yadav
2011-01-27 15:18 ` adnan iqbal
2011-01-27 17:44 ` David Daney
2011-01-28 9:18 ` naveen yadav
2011-01-28 18:48 ` David Daney
2011-01-30 15:02 ` Himanshu Aggarwal
2011-01-31 13:08 ` Ralf Baechle
2011-02-04 3:24 ` naveen yadav
2011-02-04 4:16 ` naveen yadav
2011-02-04 17:25 ` David Daney [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=4D4C3676.50802@caviumnetworks.com \
--to=ddaney@caviumnetworks.com \
--cc=kernelnewbies@nl.linux.org \
--cc=linux-mips@linux-mips.org \
--cc=lkml.himanshu@gmail.com \
--cc=ralf@linux-mips.org \
--cc=yad.naveen@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