public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Scott Wood <scottwood@freescale.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] Run a standalone application on a core other than 0
Date: Mon, 8 Jul 2013 16:41:37 -0500	[thread overview]
Message-ID: <1373319697.8183.177@snotra> (raw)
In-Reply-To: <CANFGKe9S1bBbJncFoZGG9wbWk-JL_8AeoxSKyj=GGGyHsiLsCA@mail.gmail.com> (from joao.fernandes@ist.utl.pt on Mon Jul  8 14:07:53 2013)

On 07/08/2013 02:07:53 PM, Jo?o Fernandes wrote:
> Indeed, my code currently doesn't setup the TLB.

So you're using the initial mapping that the U-Boot spin table code  
creates?

It looks like that entry is missing MAS2_M.  This needs to be fixed.

The secondary IMA that U-Boot creates also needs to begin at effective  
address zero to be ePAPR-compliant.

> Yes, U-Boot is still running on core 0. I'm looking for a  
> non-preemptive environment to run some
> benchmarks,

U-Boot is a bootloader, not a benchmarking environment.  It is strongly  
recommended that you not leave U-Boot running on any CPU (including  
spin table code) if you're running benchmarks.  For example, U-Boot  
will be continuously polling the serial port, which includes sync  
instructions that get broadcast to other CPUs.

> Is there a way to link my standalone application with the functions in
> U-Boot that manage the TLB, caches, etc.?

You could in theory create a custom U-Boot instance that runs in this  
way -- but again, U-Boot is a bootloader and is not ideally suited to  
this task.  What hardware init are you referring to?

-Scott

       reply	other threads:[~2013-07-08 21:41 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CANFGKe9S1bBbJncFoZGG9wbWk-JL_8AeoxSKyj=GGGyHsiLsCA@mail.gmail.com>
2013-07-08 21:41 ` Scott Wood [this message]
2013-07-02 12:02 [U-Boot] Run a standalone application on a core other than 0 João Fernandes
2013-07-02 21:11 ` Scott Wood
2013-07-08 17:22   ` João Fernandes
2013-07-08 18:16     ` 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=1373319697.8183.177@snotra \
    --to=scottwood@freescale.com \
    --cc=u-boot@lists.denx.de \
    /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