From: Philippe Gerum <rpm@xenomai.org>
To: Petr Cervenka <grugh@domain.hid>
Cc: xenomai@xenomai.org
Subject: Re: [Xenomai-help] rtdm_event_timedwait returns -EINTR
Date: Mon, 04 May 2009 16:22:16 +0200 [thread overview]
Message-ID: <1241446936.26544.324.camel@domain.hid> (raw)
In-Reply-To: <200905041620.27243@domain.hid>
On Mon, 2009-05-04 at 16:20 +0200, Petr Cervenka wrote:
> >Assuming you are using the native API (the POSIX interface would have to
> >be adapted the same way), does the following patch help?
> >
>
> The patch doesn't make any difference. It could be because I use mostly rtdm skin in the driver, not native. And the native skin example already resets syscall (but with wrong timeout).
>
> Meanwhile I have found out the type of the signal, which interrupts my syscalls. It's SIGWINCH (or perhaps SIGHARDEN). What is exactly this signal used for, should it be interrupting syscalls?
This is a signal internally used by skins to force a thread in primary
mode; it should not do interrupt syscalls, provided we set the sigaction
flags properly.
>
> Petr
>
--
Philippe.
next prev parent reply other threads:[~2009-05-04 14:22 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200905041613.30996@domain.hid>
[not found] ` <200905041614.26154@domain.hid>
[not found] ` <200905041615.12763@domain.hid>
[not found] ` <200905041616.11698@domain.hid>
[not found] ` <200905041617.10314@domain.hid>
[not found] ` <200905041618.6444@domain.hid>
[not found] ` <200905041619.25024@domain.hid>
[not found] ` <200905041620.27181@domain.hid>
2009-05-04 14:20 ` [Xenomai-help] rtdm_event_timedwait returns -EINTR Petr Cervenka
2009-05-04 14:22 ` Philippe Gerum [this message]
2009-05-04 14:29 ` Philippe Gerum
2009-05-04 16:11 ` Petr Cervenka
2009-05-04 16:21 ` Gilles Chanteperdrix
2009-05-05 8:22 ` Petr Cervenka
2009-05-04 17:15 ` Philippe Gerum
[not found] <200904301508.29432@domain.hid>
[not found] ` <200904301509.13094@domain.hid>
[not found] ` <200904301510.8382@domain.hid>
[not found] ` <200904301511.15875@domain.hid>
[not found] ` <200904301512.9035@domain.hid>
[not found] ` <200904301513.12716@domain.hid>
[not found] ` <200904301514.6099@domain.hid>
[not found] ` <200904301515.16182@domain.hid>
2009-04-30 13:16 ` Petr Cervenka
2009-04-30 14:09 ` Thomas Lockhart
2009-04-30 14:55 ` Philippe Gerum
2009-04-30 15:27 ` Gilles Chanteperdrix
2009-04-30 18:37 ` Philippe Gerum
2009-05-02 16:27 ` Gilles Chanteperdrix
2009-05-02 18:31 ` Philippe Gerum
2009-05-04 8:24 ` Petr Cervenka
2009-05-04 8:41 ` Philippe Gerum
2009-04-30 22:40 ` Thomas Lockhart
2009-05-01 9:34 ` Philippe Gerum
2009-05-01 9:40 ` Philippe Gerum
2009-05-01 21:35 ` Thomas Lockhart
2009-05-01 22:07 ` Philippe Gerum
2009-05-01 23:44 ` Thomas Lockhart
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=1241446936.26544.324.camel@domain.hid \
--to=rpm@xenomai.org \
--cc=grugh@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.