From: Philippe Gerum <rpm@xenomai.org>
To: Bertram Stemer <bertram.stemer@domain.hid>
Cc: "'xenomai@xenomai.org'" <xenomai@xenomai.org>
Subject: Re: [Xenomai-help] Cast a double value fails
Date: Wed, 07 Mar 2012 13:01:21 +0100 [thread overview]
Message-ID: <4F574E11.7050209@domain.hid> (raw)
In-Reply-To: <59395C11A1D1C44ABE7AD0566C50F68BCC15A49EDD@mary.at.omicron.at>
On 03/07/2012 12:46 PM, Bertram Stemer wrote:
> Hi,
> I'm using Xenomai 2.5.6 with Linux 2.6.36 on a PowerPC and
> have written a real-time application that runs on an isolated
> CPU (Kernel option isolcpus). When I start this application on
> another core, where a plain Linux application runs I get
> sporadically unexpected results in the non real-time application,
> when casting a double to an integer?!
>
> To reproduce this behavior I have a small non real-time test
> application that runs in parallel to the RT application:
> ...
> while (1) {
> int z = 4.0;
> if (z != 4)
> printf("cast error detected!");
> /* sleep some microseconds */
> }
> ...
>
> Does anyone know how this can happen? Is there a CPU utilization
> bound for real-time applications that run on the same CPU with
> plain Linux tasks?
isolcpus does not actually fully isolates CPU from non-rt activity. What
you see is likely a bug in the Xenomai core, leaking fpu context bits
spuriously between -rt and non-rt. Adding this to the todo list.
>
> Thanks in advance,
> Bertram
>
> _______________________________________________
> Xenomai-help mailing list
> Xenomai-help@domain.hid
> https://mail.gna.org/listinfo/xenomai-help
>
--
Philippe.
prev parent reply other threads:[~2012-03-07 12:01 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-07 11:46 [Xenomai-help] Cast a double value fails Bertram Stemer
2012-03-07 12:01 ` Philippe Gerum [this message]
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=4F574E11.7050209@domain.hid \
--to=rpm@xenomai.org \
--cc=bertram.stemer@domain.hid \
--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.