From: Andrew Morton <akpm@linux-foundation.org>
To: rostedt@goodmis.org
Cc: monstr@monstr.eu, linux-kernel@vger.kernel.org,
michal.simek@petalogix.com, arnd@arndb.de,
john.williams@petalogix.com, tglx@linutronix.de,
peter.fritzsche@gmx.de, anton@samba.org, mingo@elte.hu
Subject: Re: [PATCH] asm-generic: Use raw_local_irq_save/restore instead local_irq_save/restore
Date: Wed, 26 May 2010 10:08:05 -0700 [thread overview]
Message-ID: <20100526100805.171b3c48.akpm@linux-foundation.org> (raw)
In-Reply-To: <1274884963.22648.245.camel@gandalf.stny.rr.com>
On Wed, 26 May 2010 10:42:43 -0400 Steven Rostedt <rostedt@goodmis.org> wrote:
> On Wed, 2010-05-26 at 10:48 +0200, monstr@monstr.eu wrote:
> > From: Michal Simek <monstr@monstr.eu>
> >
> > start/stop_critical_timing function for preemptirqsoff, preemptoff
> > and irqsoff tracers contains atomic_inc and atomic_dec operations.
> >
> > Atomic operations used local_irq_save/restore macros to ensure
> > atomic access but they are traced by the same function which is causing
> > recursion problem.
> >
> > The reason is when these tracers are turn ON then local_irq_save/restore
> > macros are changed in include/linux/irqflags.h to call trace_hardirqs_on/off
> > which call start/stop_critical_timing.
> >
> > Microblaze was affected because use generic atomic implementation.
> >
> > Signed-off-by: Michal Simek <monstr@monstr.eu>
>
> Acked-by: Steven Rostedt <rostedt@goodmis.org>
>
Sighed-at-by: me.
> > diff --git a/include/asm-generic/atomic.h b/include/asm-generic/atomic.h
> > index 058129e..6c190fd 100644
> > --- a/include/asm-generic/atomic.h
> > +++ b/include/asm-generic/atomic.h
> > @@ -57,11 +57,11 @@ static inline int atomic_add_return(int i, atomic_t *v)
> > unsigned long flags;
> > int temp;
> >
> > - local_irq_save(flags);
> > + raw_local_irq_save(flags);
> > temp = v->counter;
> > temp += i;
> > v->counter = temp;
> > - local_irq_restore(flags);
> > + raw_local_irq_restore(flags);
> >
> > return temp;
> > }
If a developer looks at atomic_add_return() and asks himself "why did
this use raw_local_irq_save()", the only way of answering that question
is to go groveling through the git logs, which is a right PITA if
you're trying to get some coding work done.
Guys, any time you add code which is non-obvious at the raw C level, it
*needs* a comment!
next prev parent reply other threads:[~2010-05-26 17:09 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1274863724-14906-1-git-send-email-monstr@monstr.eu>
[not found] ` <1274863724-14906-2-git-send-email-monstr@monstr.eu>
2010-05-26 14:42 ` [PATCH] asm-generic: Use raw_local_irq_save/restore instead local_irq_save/restore Steven Rostedt
2010-05-26 17:08 ` Andrew Morton [this message]
2010-05-26 17:11 ` Steven Rostedt
2010-05-27 7:14 ` Michal Simek
2010-05-27 9:11 ` Yong Zhang
2010-07-26 8:49 ` Michal Simek
2010-07-27 23:18 ` Andrew Morton
2010-07-27 23:54 ` Mike Frysinger
2010-07-28 5:23 ` Michal Simek
2010-07-28 5:20 ` Michal Simek
2010-07-28 5:35 ` Mike Frysinger
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=20100526100805.171b3c48.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=anton@samba.org \
--cc=arnd@arndb.de \
--cc=john.williams@petalogix.com \
--cc=linux-kernel@vger.kernel.org \
--cc=michal.simek@petalogix.com \
--cc=mingo@elte.hu \
--cc=monstr@monstr.eu \
--cc=peter.fritzsche@gmx.de \
--cc=rostedt@goodmis.org \
--cc=tglx@linutronix.de \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox