All of lore.kernel.org
 help / color / mirror / Atom feed
From: Michael Schnell <mschnell@lumino.de>
To: linux-embedded@vger.kernel.org
Subject: AMP on an SMP system
Date: Fri, 02 Aug 2013 10:33:37 +0200	[thread overview]
Message-ID: <51FB6EE1.3090708@lumino.de> (raw)

Hi Experts.

Is there a kind of "official" way to set aside one of the available 
cores in an SMP system from the Linux OS to do deeply embedded 
extremely-low-latency stuff in a kind of single task "main loop" type 
environment ? I.e. creating a true coprocessor from an SMP hardware.

Some of the problems that come in ind here include:

  - how to make the Linux initialization ignore one of the available 
cores  or free a core later on ?
Here I found this:
http://www.linuxtopia.org/online_books/linux_kernel/kernel_configuration/re46.html
So using one of the four cores for special purpose in fact is viable.

  - how to have  a Linux task start the free running main loop ?

  - how to assign certain interrupts to that core and have ISRs run 
there only dedicatedly interrupting the "main loop" and not ever being 
blocked by any Linux activity ?
here I found this:
https://access.redhat.com/site/solutions/15482
In fact of course the hardware defines if/how a certain Interrupt can be 
assigned to a certain CPU. How is this usually done when using ARM 
Cortex A9+ cores ?

  - what about MMU issues ?

  - how to have a Linux application communicate with the non.-Linux 
application running on the dedicated core ?
Here I found this:
http://lwn.net/Articles/464391


For example I (e.g.) would like a (now rather cheap) standard quadcore 
ARM Cortex A9 processor chip and modify a Debian distribution in a way 
that support this stuff.

Thanks for any pointers ?

-Michael

             reply	other threads:[~2013-08-02  8:33 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-08-02  8:33 Michael Schnell [this message]
2013-08-02 11:42 ` AMP on an SMP system Robert Schwebel
2013-08-02 12:13   ` Michael Schnell
2013-08-02 14:53     ` Marco Stornelli
2013-08-02 15:24       ` Michael Schnell
2013-08-02 15:37         ` Marco Stornelli
2013-08-02 16:00           ` Michael Schnell
2013-08-02 15:58             ` Marco Stornelli
2013-08-03 19:11       ` Robert Schwebel
2013-08-05  7:25         ` Michael Schnell
2013-08-05  8:17           ` Robert Schwebel
2013-08-05  9:04             ` Michael Schnell
2013-08-04 21:28 ` Lambrecht Jürgen
2013-08-05  7:36   ` Michael Schnell
2013-08-05 10:00   ` Lambrecht Jürgen
2013-08-07  8:23     ` Michael Schnell
2013-08-07  8:29       ` Michael Schnell
2013-08-07  9:04       ` Michael Schnell
2013-08-08  7:41 ` Michael Schnell
  -- strict thread matches above, loose matches on Subject: below --
2013-08-02 16:16 Jon Sevy
2013-08-05  7:45 ` Michael Schnell
2013-08-05  8:21   ` Robert Schwebel
2013-08-05  8:42     ` Michael Schnell
2013-08-05  9:06 Guenter Ebermann
2013-08-05  9:34 ` Michael Schnell

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=51FB6EE1.3090708@lumino.de \
    --to=mschnell@lumino.de \
    --cc=linux-embedded@vger.kernel.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 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.