All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jan Kiszka <jan.kiszka@domain.hid>
To: xenomai@xenomai.org
Subject: [Xenomai-core] Re: [patch] memory barriers in intr.c :: xnintr_lock/unlock()
Date: Thu, 07 Dec 2006 00:03:17 +0100	[thread overview]
Message-ID: <45774C35.3070101@domain.hid> (raw)
In-Reply-To: <b647ffbd0611111559y8e66c37m12deb64828a85d08@domain.hid>

[-- Attachment #1: Type: text/plain, Size: 993 bytes --]

Dmitry Adamushko wrote:
> Hello,
> 
> following the recent discussion with Jan, here is a patch that aims at
> allowing xnintr_lock/unlock actually do what they were supposed to do in
> the first instance.
> 

[...]

> 
> --- xenomai/ksrc/nucleus/intr-old.c	2006-11-12 00:17:56.000000000 +0100
> +++ xenomai/ksrc/nucleus/intr.c	2006-11-12 00:22:15.000000000 +0100
> @@ -135,12 +135,14 @@ static inline void xnintr_shirq_lock(xni
>  {
>  #ifdef CONFIG_SMP
>  	xnarch_atomic_inc(&shirq->active);
> +	xnarch_memory_barrier();
>  #endif
>  }
>  
>  static inline void xnintr_shirq_unlock(xnintr_shirq_t *shirq)
>  {
>  #ifdef CONFIG_SMP
> +	xnarch_memory_barrier();
>  	xnarch_atomic_dec(&shirq->active);
>  #endif
>  }

As Dmitry and I are still a bit undecided about who to evolve such RCU
locks best but still face this SMP bug in the current code, we are
suggesting now to merge the patch above as-is for 2.3 - before things
get lost for the release.

Jan


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 250 bytes --]

  parent reply	other threads:[~2006-12-06 23:03 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-11-11 23:59 [Xenomai-core] [patch] memory barriers in intr.c :: xnintr_lock/unlock() Dmitry Adamushko
2006-11-17 18:40 ` [Xenomai-core] " Jan Kiszka
2006-11-19 10:55   ` Dmitry Adamushko
2006-11-20  9:13     ` Jan Kiszka
2006-11-20 20:09       ` Dmitry Adamushko
2006-11-20 23:40         ` Jan Kiszka
2006-11-21  9:32           ` Dmitry Adamushko
2006-11-21 11:28             ` Jan Kiszka
2006-12-06 23:03 ` Jan Kiszka [this message]
2006-12-08 17:54   ` Philippe Gerum

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=45774C35.3070101@domain.hid \
    --to=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.