From: Philippe Gerum <rpm@xenomai.org>
To: Ronny Meeus <ronny.meeus@gmail.com>
Cc: xenomai@xenomai.org
Subject: Re: [Xenomai] Xenomai-forge: thread using 100% cpu load
Date: Wed, 06 Mar 2013 16:49:51 +0100 [thread overview]
Message-ID: <5137659F.6060205@xenomai.org> (raw)
In-Reply-To: <CAMJ=MEcMeQ2oj+g099xxOukwBvGaxyNwQ5dtYDCZfMOOgD8kng@mail.gmail.com>
On 03/06/2013 03:32 PM, Ronny Meeus wrote:
> si_code=SI_TIMER, si_pid=51, si_uid=0, si_value={int=273724880,
> ptr=0x1050b5d0}}, NULL, 16) = 32
> 11309 15.442127 +++ killed by SIGKILL +++
>
> I'm not an expert in this, but to me it looks like the create_timer
> call, executed in the context of the 11308 thread, gets interrupted
> because a signal is received by thread 11309. This signal is generated
> because of a timer expiry which creates a new thread and processes the
> callback function.
>
> Is it not possible to disable all signals of the process during the
> creation of the timer in xenomai. In this way we can avoid the race
> condition in the library. This might be not a clean solution but would
> it work as a temporary one until you finish the timer handling you
> talk about in one of your earlier mails.
Fiddling with signal masks to work around an underlying bug would be
asking for more trouble. Time is a scarce enough resource.
BTW can I have some
> information about what you are planning to change?
>
This one:
http://git.xenomai.org/?p=xenomai-forge.git;a=commit;h=cf30fb5e22a1a3d66412f1024be1ba86260904cc
This implementation passes the psos testsuite in -forge, and runs your
testcase fine. Please pull this change and let me know if the situation
improves.
--
Philippe.
next prev parent reply other threads:[~2013-03-06 15:49 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-28 19:19 [Xenomai] Xenomai-forge: thread using 100% cpu load Ronny Meeus
2013-02-28 20:10 ` Gilles Chanteperdrix
2013-02-28 20:22 ` Thomas De Schampheleire
2013-02-28 20:27 ` Gilles Chanteperdrix
2013-03-01 8:22 ` Philippe Gerum
2013-03-01 8:26 ` Gilles Chanteperdrix
2013-03-01 8:30 ` Philippe Gerum
2013-03-01 8:30 ` Gilles Chanteperdrix
2013-03-01 8:41 ` Philippe Gerum
2013-03-02 11:13 ` Ronny Meeus
2013-03-05 12:43 ` Ronny Meeus
2013-03-05 13:28 ` Philippe Gerum
2013-03-05 14:08 ` Philippe Gerum
2013-03-05 14:25 ` Ronny Meeus
2013-03-05 14:47 ` Philippe Gerum
2013-03-05 14:53 ` Ronny Meeus
2013-03-06 10:55 ` Ronny Meeus
2013-03-06 11:09 ` Philippe Gerum
2013-03-06 11:18 ` Philippe Gerum
2013-03-06 13:24 ` Philippe Gerum
2013-03-06 13:49 ` Philippe Gerum
2013-03-06 14:32 ` Ronny Meeus
2013-03-06 15:49 ` Philippe Gerum [this message]
2013-03-07 10:02 ` Ronny Meeus
2013-03-07 10:32 ` Philippe Gerum
2013-03-07 15:56 ` Philippe Gerum
2013-03-07 19:51 ` Ronny Meeus
2013-03-08 7:44 ` Ronny Meeus
2013-02-28 20:30 ` Ronny Meeus
2013-02-28 20:35 ` Gilles Chanteperdrix
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=5137659F.6060205@xenomai.org \
--to=rpm@xenomai.org \
--cc=ronny.meeus@gmail.com \
--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.