From: Jan Kiszka <jan.kiszka@domain.hid>
To: barbalace@domain.hid
Cc: xenomai-help <xenomai@xenomai.org>, adeos-main@gna.org
Subject: Re: [Xenomai-help] Re: [Adeos-main] [PATCH] ppc mvme5500
Date: Mon, 11 Dec 2006 15:32:17 +0100 [thread overview]
Message-ID: <457D6BF1.1040507@domain.hid> (raw)
In-Reply-To: <457D609F.8030301@domain.hid>
[-- Attachment #1: Type: text/plain, Size: 1278 bytes --]
Wolfgang Grandegger wrote:
> barbalace@domain.hid wrote:
>> Testing with the native skin I notice (Xenomai2.2.0) that mutex
>> doesn't behave
>> like I think:
>> 1. create a mutex
>> 2. lock the mutex (infinite)
>> 3. start a RT task
>> 4. lock the mutex in the RT task (infinite)
>> 5. register an interrupt
>>
>> 6a. ...wait...
>> 6. reach an interrupt and unlock the mutex
>> 6b. ...then...
>>
>> 7. start 2-times the code after the previous rt_mutex_lock [this is not
>> correct!!!]
>> 8. goto 6a.
>>
>> the rt_mutex_lock is clearly in a for loop.
>> Probably I'm in truble. Using a semaphore resolve my problems.
>> When using mutex I lose the machine control.
>
> I don't have a quick answer but maybe somebody else can help.
Antonio, please use a recent Xenomai version (e.g. 2.2.5) to avoid that
we may hunt old issues. Next post a simple demo code to xenomai-help,
showing the misbehaviour. We could then check if other archs are
involved, if it's reproducible on further PPC boards, or if some mistake
might have slipped into the code.
From your description I wonder if you lock the mutex in line 2 from the
correct context (a Xenomai thread). If you call that lock from main,
don't forget to invoke rt_task_shadow first.
Jan
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 250 bytes --]
next prev parent reply other threads:[~2006-12-11 14:32 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-08 0:28 [Adeos-main] [PATCH] ppc mvme5500 barbalace
2006-12-08 11:57 ` Wolfgang Grandegger
2006-12-08 16:35 ` barbalace
2006-12-08 20:38 ` Wolfgang Grandegger
[not found] ` <1165665886.457aa65e2c26e@domain.hid>
[not found] ` <457AAEB9.20403@domain.hid>
[not found] ` <1165834501.457d390514d36@domain.hid>
[not found] ` <457D57B4.3000802@domain.hid>
[not found] ` <1165843368.457d5ba8692bd@domain.hid>
2006-12-11 13:43 ` [Xenomai-help] " Wolfgang Grandegger
2006-12-11 14:32 ` Jan Kiszka [this message]
2006-12-11 17:55 ` barbalace
2006-12-11 18:10 ` Jan Kiszka
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=457D6BF1.1040507@domain.hid \
--to=jan.kiszka@domain.hid \
--cc=adeos-main@gna.org \
--cc=barbalace@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.