From: Michael Schnell <mschnell@lumino.de>
Cc: linux-embedded@vger.kernel.org
Subject: Re: AMP on an SMP system
Date: Mon, 05 Aug 2013 11:04:07 +0200 [thread overview]
Message-ID: <51FF6A87.6080100@lumino.de> (raw)
In-Reply-To: <20130805081758.GI30920@pengutronix.de>
On 08/05/2013 10:17 AM, Robert Schwebel wrote:
> On Mon, Aug 05, 2013 at 09:25:18AM +0200, Michael Schnell wrote:
>>> You can't. And you can't, even if you try to run bare-metal software
>>> on a dedicated core. I can't imagine how for example the cache
>>> influences between the cores could be determined.
>> This would render all efforts for hard realtime embedded Linux
>> applications useless. You always need to calculate the max latency.
> You can't calculate the max latency with today's complex processor
> hardware any more. It's all a matter of system failure probabilities.
So don't use them for realtime embedded applications ?
There are companies such as SysGo that seem to claim this possibility
with their PikeOS (see
http://www.sysgo.com/products/pikeos-rtos-and-virtualization-concept/rtos-technology/
). AFAIK, they don't even are able to use dedicated cores (yet). Of
course they don't support "virtual peripheral" technology here, but
strict determinism is a strung requirement with the critical "security"
applications they have in mind.
> Nevertheless, there always have been settings where you could get rid
> of all realtime complexity by spending a 1-Euro microcontroller to the
> BOM.
For "virtual peripherals" applications you will need either a fast CPU
or an FPGA.
> AM335x has PRU subprocessors (not ARM architecture).
The 4788 page "AM335x Applications Processor Technical Reference Manual"
(SPRUH73 – October 2011) on page 226 depicts the "ARM Cortex M3 Memory
Map".
> What kind of application is that?
At first we are discussion DMX I/O (there already is a running project
doing this with the 335x PRUS (on a BeagleBone board).
But this is only sample "virtual peripheral" project with rather low
demand that easily could be done with "a 1-Euro microcontroller". (and
in fact we already did this using a PIC33).
But in future we are planning for several kinds of propriety digital
waveforms that are to be generated or analyzed.
-Michael
next prev parent reply other threads:[~2013-08-05 9:04 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-02 8:33 AMP on an SMP system Michael Schnell
2013-08-02 11:42 ` 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 [this message]
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=51FF6A87.6080100@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).