From: Michael Schnell <mschnell@lumino.de>
To: linux-embedded@vger.kernel.org
Subject: Re: AMP on an SMP system
Date: Thu, 08 Aug 2013 09:41:08 +0200 [thread overview]
Message-ID: <52034B94.6030809@lumino.de> (raw)
In-Reply-To: <51FB6EE1.3090708@lumino.de>
As a résumé of this discussion I feel that it would be very viable to to
a commercial or non-commercial project that allows for easy use of a
single (or even multiple ) dedicated AMP CPU(s) working together with an
SMP Linux system in a multi core ARM Cortex A9 chip.
Here the supplier would need to provide:
- means to dedicate one (or more) CPU(s) to an AMP system(s)
(including setting the AMP Bit to prevent 1st level cache
synchronization for this CPU(s), and possibly including a patch for the
scheduler that performance prevents degradation due to the count of
managed CPUs being not identical with those found in hardware)
- means for communication with the AMP system(s) (i.e. a prototype for
a Kernel driver that allows for bidirectional "message-queue"- / pipe-
like communication using a DMA-alike non-cached memory region and mutual
interrupts for notification
- means to load and start a program in an AMP system (supposedly
provided by the same Kernel driver). Here supposedly some kind of cache
flush needs to be done as the cache synchronization is switched off for
the AMP CPU(s).
- appropriate documentation (including a definition on how to do the
software for the AMP system and including hints on how to calculate the
max latency)
What do you think ?
-Michael
next prev parent reply other threads:[~2013-08-08 7:41 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
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 [this message]
-- 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=52034B94.6030809@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 read-only IMAP folder(s) and NNTP newsgroup(s).