All of lore.kernel.org
 help / color / mirror / Atom feed
From: Marco Stornelli <marco.stornelli@coritel.it>
To: Sanal Kumar V K <sanalvk@centillium.com>
Cc: linuxppc-embedded@ozlabs.org
Subject: Re: Running a section of code from internal memory
Date: Thu, 08 May 2008 14:45:18 +0200	[thread overview]
Message-ID: <4822F5DE.80502@coritel.it> (raw)
In-Reply-To: <4822E5CE.3090701@centillium.com>

Sanal Kumar V K ha scritto:
> Hi All,
> 
> I am porting a GW/router application to embedded Linux for a product
> based on SoC; following is the version information:
> 
> kernel: 2.6.10
> uClibc: 0.9.27
> gcc: 3.4.3
> binutils: 2.15.94.0.2.2
> 
> A small part of the code needs to run from the on-chip "L2 scratch" for
> getting optimum performance. I would really appreciate if some could
> give me some pointers regarding the following questions:
> 
> 1. Is #pragma section supported by gcc.
> The compiler prints this warning "ignoring #pragma section" and the
> pragma is ignored indicating that it is not supported. Is there any way
> I can get the pragma working for gcc or any alternative?
> 
> 2. Is there any patch available to modify the kernel thread creation so
> as to place the stack and tcb in the user configured addresses for
> kernel threads (similar to taskInit() in VxWorks)?
> 
> Thanks in advance,
> Sanal
> 
> 
> _______________________________________________
> Linuxppc-embedded mailing list
> Linuxppc-embedded@ozlabs.org
> https://ozlabs.org/mailman/listinfo/linuxppc-embedded
> 
I think at application level you can use the #pragma directive but I'm 
sure that you can't use this directive at kernel level.

  reply	other threads:[~2008-05-08 13:14 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-05-08 11:36 Running a section of code from internal memory Sanal Kumar V K
2008-05-08 12:45 ` Marco Stornelli [this message]
2008-05-08 15:33 ` Scott Wood
2008-05-12 14:33   ` Sanal Kumar V K
2008-05-12 15:56     ` Scott Wood

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=4822F5DE.80502@coritel.it \
    --to=marco.stornelli@coritel.it \
    --cc=linuxppc-embedded@ozlabs.org \
    --cc=sanalvk@centillium.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.