All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bruce Ashfield <bruce.ashfield@windriver.com>
To: David Mulder <dmulder@lasx.com>
Cc: "yocto@yoctoproject.org" <yocto@yoctoproject.org>
Subject: Re: Can I disable RT throttling?
Date: Mon, 11 Mar 2013 13:45:39 -0400	[thread overview]
Message-ID: <513E1843.3070604@windriver.com> (raw)
In-Reply-To: <19F0379280417C4A8FE3BD23AA7298E501347F52@EXMBX202A.mmeprod.cbeyond>

On 13-03-11 01:38 PM, David Mulder wrote:
>> From: Trevor Woerner [mailto:twoerner@gmail.com]
>> You can call sched_setaffinity() before fork()ing your task, or use
>> taskset on the cmdline.
>
> Will that work on a core that's offline?

Nope. Only with an online core controlled by the Linux scheduler.
If you do end up trying to get AMP working, you need to plumbing
to load the other OS/kernel in a reserved memory location, set the
program counter and start the OS.

But that secondary OS has to know how to behave in a system that
it doesn't control, and you'll need ways to communicate with it
from Linux.

remoteproc/rpmsg can solve some of the issues that I mention, but
it is far from out of the box.

That's why there's more interest in running a single task with
exclusive CPU in userspace. The work and scaffolding required to
get an AMP system up and running is non trivial.

Cheers,

Bruce

> _______________________________________________
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto
>



  reply	other threads:[~2013-03-11 17:45 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-08 22:36 Can I disable RT throttling? David Mulder
2013-03-09  3:28 ` Bruce Ashfield
2013-03-09 17:12   ` Vin Shelton
2013-03-10  3:09     ` Bruce Ashfield
2013-03-11 16:15   ` David Mulder
2013-03-11 17:32     ` Trevor Woerner
2013-03-11 17:38       ` David Mulder
2013-03-11 17:45         ` Bruce Ashfield [this message]
2013-03-11 18:13           ` David Mulder
2013-03-12  0:14             ` Bruce Ashfield
2013-03-10 11:42 ` Fredrik Markström
2013-03-10 18:00   ` Bruce Ashfield

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=513E1843.3070604@windriver.com \
    --to=bruce.ashfield@windriver.com \
    --cc=dmulder@lasx.com \
    --cc=yocto@yoctoproject.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.