From: Paolo Minazzi <Paolo.Minazzi@mitrol.it>
To: Gilles Chanteperdrix <gilles.chanteperdrix@xenomai.org>
Cc: xenomai@xenomai.org
Subject: Re: [Xenomai] Make a block of code atomic
Date: Wed, 10 Jul 2013 13:46:47 +0200 [thread overview]
Message-ID: <51DD49A7.5060109@mitrol.it> (raw)
In-Reply-To: <51DD4760.6050908@xenomai.org>
Il 10/07/2013 13.37, Gilles Chanteperdrix ha scritto:
> On 07/09/2013 01:40 PM, Paolo Minazzi wrote:
>
>> Hi,
>>
>> I would like to make a block of kernel code atomic, so that no one (both
>> xenomai and Linux) can interrupt it.
>> I use the following :
>>
>> #define my_local_irq_save(x) ((x) =
>> ipipe_test_and_stall_pipeline_head()& 1)
>> #define my_local_irq_restore(x) ipipe_restore_pipeline_head(x)
>>
>> my_local_irq_save(flags);
>> < critical section>
>> my_local_irq_restore(flags);
>>
>> It works well enough, but rarely an rtdm irq enter into my critical
>> section.
>> The rtdm irq is registered in this way : rtdm_irq_request(&priv->irqHnd,
>> ETH_PORT_IRQ_NUM(priv->port), irqHandler, RTDM_IRQTYPE_EDGE, "rtdm_eth",
>> priv);
>>
>> Is it normal ? Are you sure that it cannot happen ?
>
>
> Looking at ipipe_test_and_stall_head implementation on the I-pipe
> patch for Linux 3.8:
>
> static inline unsigned long ipipe_test_and_stall_head(void)
> {
> hard_local_irq_disable();
> return __test_and_set_bit(IPIPE_STALL_FLAG, &__ipipe_head_status);
> }
>
> getting an interrupt in your critical section would mean that
> "hard_local_irq_disable" is broken on the architecture where you use it.
>
> That being said, I do not know if I look at the implementation you are
> using, since you did not give us any information about version and
> architecture you are using.
>
Hi Gilles, thanks for your answer.
I found this morning that was linux to re-enable interrupts.
The following
#define my_local_irq_save(x) ((x) =
ipipe_test_and_stall_pipeline_head()& 1)
#define my_local_irq_restore(x) ipipe_restore_pipeline_head(x)
works well if no one touch irq flags directly. Unfortunately was not my
case.
Thanks again,
Paolo
prev parent reply other threads:[~2013-07-10 11:46 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-09 11:40 [Xenomai] Make a block of code atomic Paolo Minazzi
2013-07-10 11:37 ` Gilles Chanteperdrix
2013-07-10 11:46 ` Paolo Minazzi [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=51DD49A7.5060109@mitrol.it \
--to=paolo.minazzi@mitrol.it \
--cc=gilles.chanteperdrix@xenomai.org \
--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.