From: Gilles Chanteperdrix <gilles.chanteperdrix@xenomai.org>
To: Steven Seeger <sseeger@domain.hid>
Cc: xenomai@xenomai.org
Subject: Re: [Xenomai-help] fpu issue
Date: Sun, 10 Feb 2008 16:41:05 +0100 [thread overview]
Message-ID: <18351.6929.602080.809203@domain.hid> (raw)
In-Reply-To: <51CAD0CE1504444DBE77CBBE51A0135D376ACD@slcmail.slc.mew.int>
Steven Seeger wrote:
> > An idea is to disassemble the kernel task code and the function it
> calls
> > to see if FPU is really never used.
> >
> > If this task really never calls any function using FPU, it would be
> nice
> > if you could (as we always ask, you may have noticed) reduce your test
> > case to a simple code where only FPU operations and every thing which
> > causes task switches (blocking calls, and calls waking up other tasks)
> > is kept.
>
> My application has 12 threads most of which wait on queues. How am I
> going to reduce this to a simple case? Most of my threads are userspace
> except for 2.
You should start with an example having the 12 same threads as the real
code, then try removing threads one by one and look if the bug is still
there. If you need the 12 threads, then send us your example with the 12
threads.
>
> I guess I'll see what I can do. I'll try the disassembler, too.
>
> Steven
--
Gilles Chanteperdrix.
next prev parent reply other threads:[~2008-02-10 15:41 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-09 1:36 [Xenomai-help] fpu issue Steven Seeger
2008-02-09 13:29 ` Gilles Chanteperdrix
2008-02-10 15:32 ` Steven Seeger
2008-02-10 15:41 ` Gilles Chanteperdrix [this message]
2008-02-10 16:36 ` Gilles Chanteperdrix
-- strict thread matches above, loose matches on Subject: below --
2009-01-20 4:25 Steven Seeger
2009-01-20 7:20 ` Gilles Chanteperdrix
2009-01-20 14:34 ` Steven Seeger
2009-01-20 14:49 ` Gilles Chanteperdrix
2009-01-20 14:55 ` Steven Seeger
2009-01-20 14:56 ` Gilles Chanteperdrix
2009-01-21 0:40 ` Steven Seeger
2009-01-21 9:28 ` Gilles Chanteperdrix
2009-01-21 13:30 ` Steven Seeger
2009-01-21 16:42 ` Steven Seeger
2009-01-21 16:48 ` Gilles Chanteperdrix
2009-01-21 17:07 ` Steven Seeger
2009-01-21 17:11 ` Gilles Chanteperdrix
2009-01-21 17:16 ` Steven Seeger
2009-01-21 17:42 ` Steven Seeger
2009-01-21 18:01 ` Gilles Chanteperdrix
2009-01-21 19:41 ` Steven Seeger
2009-01-21 19:48 ` Gilles Chanteperdrix
2009-01-21 20:05 ` Steven Seeger
2009-01-21 20:08 ` Steven Seeger
2009-01-21 20:45 ` Steven Seeger
2009-01-21 20:47 ` Steven Seeger
2009-01-21 21:13 ` Gilles Chanteperdrix
2009-01-21 21:20 ` Steven Seeger
2009-01-21 21:26 ` Gilles Chanteperdrix
2009-01-21 21:27 ` Steven Seeger
2009-01-21 21:44 ` Steven Seeger
2009-01-21 21:56 ` Gilles Chanteperdrix
2009-01-21 21:57 ` Steven Seeger
2009-01-26 16:13 ` Gilles Chanteperdrix
2009-01-21 16:43 ` Steven Seeger
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=18351.6929.602080.809203@domain.hid \
--to=gilles.chanteperdrix@xenomai.org \
--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.