Re: [Xenomai-help] General question on Native Skin tasks

[Jan Kiszka <jan.kiszka@domain.hid>]

[-- Attachment #1: Type: text/plain, Size: 1550 bytes --]

Jan Kiszka wrote:
> Philippe Gerum wrote:
>> Philippe Gerum wrote:
>>> Jan Kiszka wrote:
>>>
>>>> Brian L. wrote:
>>>>
>>>>> If I create a native-skin RT_TASK from userspace with no flags, i.e.
>>>>>
>>>>> void task(void*)
>>>>> {
>>>>>    for (;;) ;
>>>>> }
>>>>> int main()
>>>>> {
>>>>>   RT_TASK t;
>>>>>   rt_task_create(&t, 0, 3, 0);
>>>>>   rt_task_start(&t,task,0);
>>>>>   (do something which blocks)
>>>>> }
>>>>
>>>>
>>>> mlockall left out for simplicity? Or is it also missing on your real
>>>> test? In the latter case, occasional application crashes are "normal"
>>>> (as described below).
>>>>
>>>> Philippe, you suggested some code for detecting this. We should really,
>>>> really add this soon (maybe to the exception path)!
>>>>
>>> The submitted patch works pretty well detecting unlocked memory, I'm
>>> using it right now, but I'd like something a bit more self-explanatory
>>> than just receiving SIGXCPU. I don't think the execption path is the
>>> right place to put this, since the mlockall issue causes random bugs,
>>> and you likely want to detect them early and unconditionally.
>>>
>> Commit #941 should provide a reliable guard against lack of process
>> memory locking.
>>
> 
> Hmm, a simple test using the latency tool with disabled mlockall did not
> yet show any effect on my system. Shouldn't there pop up some message
> when starting such a "broken" program?
> 

The usual "rebuild your stuff before you try" (I missed a kernel
rebuild). Works very nicely!

Jan


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 252 bytes --]