From: Thomas Gleixner <tglx@linutronix.de>
To: Chen Gang <gang.chen@asianux.com>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] kernel/timer.c: using spin_lock_irqsave instead of spin_lock + local_irq_save, especially when CONFIG_LOCKDEP not defined
Date: Thu, 20 Jun 2013 11:02:23 +0200 (CEST) [thread overview]
Message-ID: <alpine.DEB.2.02.1306201055580.4013@ionos.tec.linutronix.de> (raw)
In-Reply-To: <51C2C077.2050900@asianux.com>
On Thu, 20 Jun 2013, Chen Gang wrote:
> On 06/20/2013 03:36 PM, Thomas Gleixner wrote:
> > On Thu, 20 Jun 2013, Chen Gang wrote:
> >> > On 06/19/2013 06:49 PM, Thomas Gleixner wrote:
> >>> > > We must do this because some architectures implement
> >>> > > do_raw_spin_lock_flags() in the following way:
> >>> > >
> >>> > > do_raw_spin_lock_flags(l, flags)
> >>> > > {
> >>> > > while (!arch_spin_trylock(l)) {
> >>> > > if (!irq_disabled_flags(flags)) {
> >>> > > arch_irq_restore(flags);
> >>> > > cpu_relax();
> >>> > > arch_irq_disable();
> >>> > > }
> >>> > > }
> >>> > > }
> >>> > >
> >> >
> >> > For mn10300 and sparc64 (not space32), it doesn't like your demo above.
> > Sigh. You're an sparc64 and mn10300 assembler expert, right?
> >
>
> No, do you mean: "only the related expert can discuss about it" ?
A discussion requires that the people who are discussing something are
familiar with the matter.
> >> > For API definition, it has no duty to make it correct if the user call
> >> > them with informal ways, especially, the implementation is related with
> >> > various architectures.
> > Nonsense.
> >
>
> The word 'Nonsense' seems not quite polite. ;-)
It might be not polite, but it's correct. And I really start to get
annoyed.
> At least, when some one see this usage below:
>
> spin_lock_irqsave(&l1, flags);
> spin_unlock(&l1);
> spin_lock(&l2);
> spin_unlock_irqrestore(&l2, flags);
>
> most of them will be amazing.
What's amazing about this?
It's the equivivalent to:
local_irq_save(flags);
spin_lock(&l1);
spin_unlock(&l1);
spin_lock(&l2);
spin_unlock(&l2);
local_irq_restore(flags);
The only difference is, that spin_lock_irqsave() implementations are
allowed to reenable interrupts while spinning, but again that's an
implementation detail which does not matter at all.
Thanks,
tglx
next prev parent reply other threads:[~2013-06-20 9:02 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-19 2:59 Chen Gang
2013-06-19 8:41 ` Thomas Gleixner
2013-06-19 9:42 ` Chen Gang
2013-06-19 9:59 ` Thomas Gleixner
2013-06-19 10:07 ` Chen Gang
2013-06-19 10:49 ` Thomas Gleixner
2013-06-20 4:14 ` Chen Gang
2013-06-20 7:36 ` Thomas Gleixner
2013-06-20 8:42 ` Chen Gang
2013-06-20 9:02 ` Thomas Gleixner [this message]
2013-06-20 10:31 ` Chen Gang
2013-06-19 10:21 ` Chen Gang
2013-06-19 10:53 ` Thomas Gleixner
2013-06-20 8:37 ` Chen Gang
2013-06-20 9:07 ` Thomas Gleixner
2013-06-20 9:53 ` Chen Gang
2013-06-20 10:42 ` Thomas Gleixner
2013-06-20 10:59 ` Chen Gang
2013-06-20 9:12 ` Eric Dumazet
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=alpine.DEB.2.02.1306201055580.4013@ionos.tec.linutronix.de \
--to=tglx@linutronix.de \
--cc=gang.chen@asianux.com \
--cc=linux-kernel@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®