All of lore.kernel.org
 help / color / mirror / Atom feed
From: Pintu Kumar <pintu.ping@gmail.com>
To: Julien Blanc <julien.blanc@sprinte.eu>
Cc: "Xenomai@xenomai.org" <xenomai@xenomai.org>
Subject: Re: [Xenomai] Problem with rt_cond_wait and rt_cond_signal combination
Date: Wed, 28 Mar 2018 15:34:16 +0530	[thread overview]
Message-ID: <CAOuPNLiMyXRLBOcLSbpVtuSKc=2tkM+mQXQoXH79GXBjhz8Zsw@mail.gmail.com> (raw)
In-Reply-To: <1522224881.2732.2.camel@sprinte.eu>

On Wed, Mar 28, 2018 at 1:44 PM, Julien Blanc <julien.blanc@sprinte.eu> wrote:
> Le mercredi 28 mars 2018 à 13:24 +0530, Pintu Kumar a écrit :
>> Hi,
>>
>> We are facing one issue on Xenomai-3 on x86_64 system.
>> Kernel: 4.9.51
>> ipipe version: 4
>> # /usr/xenomai/sbin/version
>> Xenomai/cobalt v3.0.6 -- #5956064 (2018-03-20 12:13:33 +0100)
>>
>> Its a very simple API level test.
>> We create a condition variable and wait for the condition inside a
>> task.
>> Then, we immediately signal the condition from the main thread, and
>> simply
>> wait for the test to finish.
>
> Looks like you're signalling the condition variable before it is even
> begin waited by the newly created thread, so i would say the behaviour
> is normal.
>
> If this is just for test purpose, you can for example add a sleep
> inside your main thread so that you make sure that the child thread
> reaches the rt_cond_wait call before the main thread executes
> rt_cond_signal.
>

Oh yes, I already tried by adding 1 second sleep before signal, but still the
condition task hangs.

This test case works fine on Xenomai 2.6


> Regards,
>
> Julien
>
> _______________________________________________
> Xenomai mailing list
> Xenomai@xenomai.org
> https://xenomai.org/mailman/listinfo/xenomai


  reply	other threads:[~2018-03-28 10:04 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-03-28  7:54 [Xenomai] Problem with rt_cond_wait and rt_cond_signal combination Pintu Kumar
2018-03-28  8:12 ` Philippe Gerum
2018-03-28  9:32   ` Pintu Kumar
2018-03-28  9:46     ` Philippe Gerum
2018-03-28  8:14 ` Julien Blanc
2018-03-28 10:04   ` Pintu Kumar [this message]
2018-03-28 13:29     ` Philippe Gerum
2018-03-28 15:07 ` Philippe Gerum
2018-03-28 17:20   ` Pintu Kumar
2018-03-28 17:32     ` Philippe Gerum
2018-03-30  6:42       ` Pintu Kumar
2018-03-30  6:53         ` Pintu Kumar
2018-03-30  8:04           ` Philippe Gerum
2018-03-30  8:08             ` Philippe Gerum
2018-03-30 13:43             ` Pintu Kumar

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='CAOuPNLiMyXRLBOcLSbpVtuSKc=2tkM+mQXQoXH79GXBjhz8Zsw@mail.gmail.com' \
    --to=pintu.ping@gmail.com \
    --cc=julien.blanc@sprinte.eu \
    --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.