All of lore.kernel.org
 help / color / mirror / Atom feed
From: Philippe Gerum <rpm@xenomai.org>
To: Luca Galvagno <luca.galvagno@colgp.it>, xenomai@xenomai.org
Subject: Re: [Xenomai] Linux scheduling is hijacked from xenomai scheduling
Date: Tue, 27 Jan 2015 11:23:15 +0100	[thread overview]
Message-ID: <54C76713.2010904@xenomai.org> (raw)
In-Reply-To: <54C760BC.7040301@colgp.it>

On 01/27/2015 10:56 AM, Luca Galvagno wrote:
> Hi to all,
> we are using kernel 2.6.34 with the corresponding ADEOS patch

Which Xenomai release?

> (2.6.34-powerpc-2.10-03.patch ) and Xenomai on a PowerPC MPC5200b.

4 years old kernel and pipeline patch, don't expect much feedback on
this configuration.

> We are facing on a strange behavior when mixing Linux SysCalls with
> Xenomai tasks . The effect of the above mix is that the "pure" (without
> linux syscall) xenomai task continues to run , the remaining "mixed"
> task (for example we have one with a posix socket server) and moreover
> the linux os itself are not scheduled anymore. Specifically, to test
> this behavior, we connected an oscilloscope to a cpu pin , the result is
> that the xenomai task is moving the pin up and down (as it was
> programmed) but the linux machine is neither accessible via ping or via
> SSH.
> 
> Do you have some suggestions, or some tests we can do ?

Xenomai starving the regular kernel from CPU cycles until all the
pending real-time duties have been carried out is the basic idea behind
the dual kernel design, this is nothing strange.

Now the question is: why does your real-time code seem to never complete
its work loop, and there never leaves some CPU time to linux?

-- 
Philippe.


  reply	other threads:[~2015-01-27 10:23 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-27  9:56 [Xenomai] Linux scheduling is hijacked from xenomai scheduling Luca Galvagno
2015-01-27 10:23 ` Philippe Gerum [this message]
2015-01-27 10:32   ` Luca Galvagno
2015-01-27 10:42     ` Philippe Gerum
2015-01-27 11:12       ` Luca Galvagno
2015-01-27 11:24         ` Philippe Gerum
2015-01-27 14:51           ` Luca Galvagno

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=54C76713.2010904@xenomai.org \
    --to=rpm@xenomai.org \
    --cc=luca.galvagno@colgp.it \
    --cc=xenomai@xenomai.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.