From: Peter Zijlstra <peterz@infradead.org>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: Thomas Gleixner <tglx@linutronix.de>,
Linux Kernel list <linux-kernel@vger.kernel.org>,
Ingo Molnar <mingo@elte.hu>
Subject: Re: [PATCH 1/2] lockdep: implement full check without irq checking
Date: Thu, 30 Oct 2008 12:15:16 +0100 [thread overview]
Message-ID: <1225365316.7803.69.camel@twins> (raw)
In-Reply-To: <1225362995.3690.10.camel@johannes.berg>
On Thu, 2008-10-30 at 11:36 +0100, Johannes Berg wrote:
> > del_timer_sync():
> >
> > local_irq_save(flags);
> > lock_aquire(my fake timer lock);
> > lock_release(...);
> > local_irq_restore(flags);
> >
> > and make that conditional CONFIG_PROVE_LOCKING and or wrap it up
> > somewhere..
>
> Yeah, that is possible, but it seemed to me that would affect the
> performance of del_timer_sync() quite a bit. Not sure it matters. And on
> powerpc (which I care about) it won't actually affect performance much
> because we lazily disable IRQs, but still. The >= 2 change also seemed
> to generate smaller code?
Its debug code, and I the >= 2 change makes the code much less obvious.
So I prefer the slightly less performant but conceptually cleaner IRQ
disable variant.
next prev parent reply other threads:[~2008-10-30 11:15 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-23 19:35 [PATCH 0/2] Timer sync lock checking Johannes Berg
2008-10-23 19:44 ` [PATCH 1/2] lockdep: implement full check without irq checking Johannes Berg
2008-10-29 15:23 ` Peter Zijlstra
2008-10-30 10:36 ` Johannes Berg
2008-10-30 11:15 ` Peter Zijlstra [this message]
2008-10-30 11:25 ` Johannes Berg
2008-10-23 19:46 ` [PATCH 2/2] timer: implement lockdep deadlock detection Johannes Berg
2008-10-23 20:37 ` [PATCH 3/2] tasklet: " Johannes Berg
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=1225365316.7803.69.camel@twins \
--to=peterz@infradead.org \
--cc=johannes@sipsolutions.net \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--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 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.