All of lore.kernel.org
 help / color / mirror / Atom feed
From: Philippe Gerum <rpm@xenomai.org>
To: Philippe Gerum <rpm@xenomai.org>
Cc: xenomai@xenomai.org, "Brian L." <bluczkie@domain.hid>,
	Jan Kiszka <jan.kiszka@domain.hid>
Subject: Re: [Xenomai-help] General question on Native Skin tasks
Date: Mon, 17 Apr 2006 19:35:28 +0200	[thread overview]
Message-ID: <4443D1E0.5020708@domain.hid> (raw)
In-Reply-To: <4443AB1F.2060405@domain.hid>

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.

-- 

Philippe.


  reply	other threads:[~2006-04-17 17:35 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-04-16 18:10 [Xenomai-help] General question on Native Skin tasks Brian L.
2006-04-17 13:33 ` Jan Kiszka
2006-04-17 14:50   ` Philippe Gerum
2006-04-17 17:35     ` Philippe Gerum [this message]
2006-04-17 20:03       ` Jan Kiszka
2006-04-17 20:44         ` Jan Kiszka
2006-04-18 19:53   ` Brian L.
2006-04-18 21:04     ` Jan Kiszka
2006-04-19 15:27       ` Brian L.
2006-04-19 17:18         ` Jan Kiszka
2006-04-19 17:42           ` Brian L.
2006-04-19 19:45             ` Jan Kiszka
2006-04-20  3:09               ` Li Yi

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=4443D1E0.5020708@domain.hid \
    --to=rpm@xenomai.org \
    --cc=bluczkie@domain.hid \
    --cc=jan.kiszka@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.