Re: [Xenomai-help] IDDP send-receive example emits SIGXCPU signal

[Philippe Gerum <rpm@xenomai.org>]

On 11/23/2011 09:31 AM, Guvenc Gulce wrote:
> Yes.. I have enabled the support for iddp sockets in the kernel configuration. It looks like that
>
> it works with xenomai 2.6.0 when I enable the
>
> pthread_set_mode_np(0, PTHREAD_WARNSW);
> after the socket() and bind() calls. (tested again with the example code from xenomai)
>
> My question is:
>
> Is it designed that way that the calls socket() and bind() for IDDP cause a switch to
>
> secondary mode and the calls recvfrom() and sendto() do not ? In other words
>
> does the real-timeliness guarantee exist only for recvfrom() and sendto() ?

No. socket() or bind() have no reason to switch to secondary mode, 
unless socket() fails for the AF_RTIPC domain, in which case the call is 
routed to the regular kernel to handle the address family. You not only 
need to enable IDDP in the kernel, but you also have to wrap POSIX calls 
to libpthread_rt services.

If socket(AF_RTIPC, ...) failed reaching Xenomai/RTDM, then it will also 
fail with the regular kernel, and this call will return an error.

>
>
> Thanks&  Regards
>
> Guvenc
>
>
>
>
> ----- Original Message -----
> From: Gilles Chanteperdrix<gilles.chanteperdrix@xenomai.org>
> To: Guvenc Gulce<gulceg@domain.hid>
> Cc: "xenomai@xenomai.org"<xenomai@xenomai.org>
> Sent: Friday, November 11, 2011 12:43 PM
> Subject: Re: [Xenomai-help] IDDP send-receive example emits SIGXCPU signal
>
> On 11/11/2011 08:04 AM, Guvenc Gulce wrote:
>> looks like XENOMAI_SKINCALL3 macro is failing for some reason but I can't
>>
>> explain this behavior as I am using the example code linked with the correct
>>
>> xenomai libraries. Any help would be highly appreciated.
>
> Do you have support for iddp sockets enabled in kernel configuration? If
> yes, do you have the same issue with xenomai 2.6.0?
>


-- 
Philippe.