public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jie Zhang <jie.zhang@analog.com>
To: Mike Frysinger <vapier.adi@gmail.com>
Cc: Jamie Lokier <jamie@shareable.org>,
	uClinux development list <uclinux-dev@uclinux.org>,
	linux-kernel@vger.kernel.org, Greg Ungerer <gerg@uclinux.org>,
	uclinux-dist-devel@blackfin.uclinux.org,
	David McCullough <davidm@snapgear.com>
Subject: Re: [uClinux-dev] [PATCH/RFC] FDPIC: add hook for arches to customize program header parsing
Date: Sun, 14 Jun 2009 08:42:42 +0800	[thread overview]
Message-ID: <4A344782.2090707@analog.com> (raw)
In-Reply-To: <8bd0f97a0906131732v5394eaf5gb0f7862dfe7f58f3@mail.gmail.com>

Mike Frysinger wrote:
> On Sat, Jun 13, 2009 at 14:25, Jamie Lokier wrote:
>> Mike Frysinger wrote:
>>> On Sat, Jun 13, 2009 at 12:13, Jamie Lokier wrote:
>>>> Mike Frysinger wrote:
>>>>> From: Jie Zhang <jie.zhang@analog.com>
>>>>>
>>>>> The Blackfin port has custom program header flags/addresses for
>>>>> automatically loading regions into the dedicated on-chip SRAM.  So add a
>>>>> hook for ports to leverage.
>>>> It looks like a way for certain special executables to load themselves
>>>> into fixed regions of the on-chip SRAM - and promptly crash if another
>>>> executable does the same.  Not so much a general executable format, as
>>>> a hack to load something specific which should only be done once at a
>>>> time.  What am I missing here?
>>> the addresses are keys, not fixed and/or "real" addresses
>> Oh, I see that is indeed quite nice :-)
>>
>> I see it checks for both flags and special address values.  Are the
>> special address checks mainly historical, as usually flags/types are
>> used to designate special memory types in ELF.
> 
> the EF bits are more for smaller/statically linked applications where
> you want to place the entire ELF into SRAM.  the special PHDRs are for
> selectively compiled code -- i.e. you've done a little bit of
> profiling and testing and know which ones are the hot spots.

Yes. Those e_flags works for the whole ELF file. And these specific 
addresses work as p_flags. May be in future I can add processor specific 
p_flags.


Jie



  reply	other threads:[~2009-06-14  0:49 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-13  1:01 [PATCH/RFC] FDPIC: add hook for arches to customize program header parsing Mike Frysinger
2009-06-13 12:23 ` [uClinux-dev] " David Howells
2009-06-13 16:13 ` Jamie Lokier
2009-06-13 16:40   ` Mike Frysinger
2009-06-13 18:25     ` Jamie Lokier
2009-06-13 18:26       ` Jamie Lokier
2009-06-14  0:32       ` Mike Frysinger
2009-06-14  0:42         ` Jie Zhang [this message]
2009-06-14  9:43 ` Paul Mundt
2009-06-15  1:43 ` Greg Ungerer
2009-06-16  8:24 ` [PATCH] " Mike Frysinger
2009-06-23  5:32   ` Andrew Morton
2009-06-23 11:04     ` Mike Frysinger
2009-12-04 17:44 ` [uClinux-dev] [PATCH/RFC] " David Howells
2009-12-05  0:28   ` Jie Zhang
2009-12-05 15:14     ` David Howells
2009-12-07 10:09       ` Mike Frysinger
2009-12-07  3:27     ` [Uclinux-dist-devel] " Zhang, Sonic
2009-12-07 10:10     ` Mike Frysinger
2009-12-07 10:17       ` Jie Zhang
2009-12-07 10:10   ` Mike Frysinger

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=4A344782.2090707@analog.com \
    --to=jie.zhang@analog.com \
    --cc=davidm@snapgear.com \
    --cc=gerg@uclinux.org \
    --cc=jamie@shareable.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=uclinux-dev@uclinux.org \
    --cc=uclinux-dist-devel@blackfin.uclinux.org \
    --cc=vapier.adi@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