All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jan Kiszka <jan.kiszka@domain.hid>
To: Steven Seeger <sseeger@domain.hid>
Cc: xenomai@xenomai.org
Subject: Re: [Xenomai-help] fpu
Date: Thu, 07 Feb 2008 16:44:49 +0100	[thread overview]
Message-ID: <47AB2771.7080508@domain.hid> (raw)
In-Reply-To: <51CAD0CE1504444DBE77CBBE51A0135D3769E8@domain.hid>

Steven Seeger wrote:
> This is probably an application error, but I am having some random weird
> behavior where sometimes a double that I add 0.01 to in a periodic task
> gets corrupted and becomes nan. I didn't specify the T_FPU flag in
> rt_task_spawn() but the docs said that flag is assumed for a user space
> task. I've since set that flag manually and haven't had the problem
> happen yet. Is this just a coincidence? 
> 

Likely, as T_FPU is hard-coded for user space threads. You could try to
strip down your test so that incorrect application behaviour can be
excluded (or use the test below).

>  
> 
> The corruption seems to happen in a half-second window where the system
> is doing a lot and only about 35% of the CPU is available to Linux.
> However, I am testing for overruns on rt_task_wait_period() and never
> seeing any.

Overload must not cause data corruption, "only" missed deadlines. This
case needs closer examination.

As some first step: there is the switchtest tool coming with Xenomai. It
includes consistency checks of the FPU environment across context
switches. Maybe you can give this a try under similar load conditions
over a longer period.

Jan

-- 
Siemens AG, Corporate Technology, CT SE 2
Corporate Competence Center Embedded Linux


  reply	other threads:[~2008-02-07 15:44 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-07 15:23 [Xenomai-help] fpu Steven Seeger
2008-02-07 15:44 ` Jan Kiszka [this message]
  -- strict thread matches above, loose matches on Subject: below --
2008-02-08 17:59 Steven Seeger
2008-02-08 18:32 ` Jan Kiszka

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=47AB2771.7080508@domain.hid \
    --to=jan.kiszka@domain.hid \
    --cc=sseeger@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.