All of lore.kernel.org
 help / color / mirror / Atom feed
From: Philippe Gerum <rpm@xenomai.org>
To: ali hagigat <hagigatali@gmail.com>
Cc: xenomai <xenomai@xenomai.org>
Subject: Re: [Xenomai] installing a signal handler
Date: Wed, 05 Feb 2014 12:42:45 +0100	[thread overview]
Message-ID: <52F223B5.2010408@xenomai.org> (raw)
In-Reply-To: <CAKKWdtdpVTdD6j1QYXB-wF_3SjpQWDTB62=kKrCWU7Y1zkc9_Q@mail.gmail.com>

On 02/05/2014 12:08 PM, ali hagigat wrote:
> On 2/3/14, Philippe Gerum <rpm@xenomai.org> wrote:
>> On 02/01/2014 01:36 PM, ali hagigat wrote:
>>> It seems that signal handler does not execute...
>>> -------------- next part --------------
>>>> cat /proc/xenomai/sched
>>> CPU  PID    CLASS  PRI      TIMEOUT   TIMEBASE   STAT       NAME
>>>     0  0      idle    -1      -         master     R          ROOT/0
>>>     1  0      idle    -1      -         master     R          ROOT/1
>>>     2  0      idle    -1      -         master     R          ROOT/2
>>>     3  0      idle    -1      -         master     R          ROOT/3
>>>     0  0      rt      50      -         master     Df         KTask1
>>>     0  0      rt      50      -         master     Df         KTask2
>>>
>>>
>>>> dmesg
>>> notify is successful...
>>>
>>
>> This deprecated feature does not wake up the receiving task.
>>
>> --
>> Philippe.
>>
>
> There are some warning messages complaining using the deprecated
> function, "rt_task_create()" at compile.
> but no warn message for rt_task_notify().
> This function does not work at user space too.
>

Your application code does wrong assumptions on what 
rt_task_notify/catch really does. So I'm unsure what "too" refers to in 
your sentence, but as a matter of fact, your code can't work.

Besides, would you have cared for the warning at rt_task_create() and 
refrained from using a dead interface from kernel space, you would not 
have even considered using rt_task_notify() for sending signals to a 
kernel-based native task in the first place.

Regarding the behavior of rt_task_notify() from user-space, you have to 
provide evidence that you are properly using the interface, so that 
people are not always investing time fixing your own bugs. You received 
more than enough information in the previous conversations to do so. 
FWIW, I had a quick look at the Xenomai code, and did not find anything 
wrong.

-- 
Philippe.


      reply	other threads:[~2014-02-05 11:42 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-01 12:36 [Xenomai] installing a signal handler ali hagigat
2014-02-02 21:43 ` Gilles Chanteperdrix
2014-02-02 21:51   ` Gilles Chanteperdrix
2014-02-03 10:09     ` ali hagigat
2014-02-03 10:39 ` Philippe Gerum
2014-02-05 11:08   ` ali hagigat
2014-02-05 11:42     ` Philippe Gerum [this message]

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=52F223B5.2010408@xenomai.org \
    --to=rpm@xenomai.org \
    --cc=hagigatali@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.