From: george anzinger <george@mvista.com>
To: Dawson Engler <engler@csl.Stanford.EDU>
Cc: Manfred Spraul <manfred@colorfullife.com>,
linux-kernel@vger.kernel.org, mc@cs.Stanford.EDU
Subject: Re: [CHECKER] blocking w/ spinlock or interrupt's disabled
Date: Tue, 20 Mar 2001 11:11:34 -0800 [thread overview]
Message-ID: <3AB7AB66.46D0AB8E@mvista.com> (raw)
In-Reply-To: <200103190213.SAA23463@csl.Stanford.EDU>
Dawson Engler wrote:
>
> > Is it difficult to split it into "interrupts disabled" and "spin lock
> > held"?
>
Is it difficult to test for matching spinlock pairs such as
spin_lock_irq/spin_unlock_irq. Sometimes a spin_lock_irq is followed by
a spin_unlock and a separate interrupt re-enable. This sort of usage,
while not strictly wrong, does make it hard to use the spin_lock/unlock
macros to do preemption. This said, pairing information would be very
helpful. Note, there are several flavors here, not just the one I
cited.
George
next prev parent reply other threads:[~2001-03-20 19:17 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-03-18 9:35 [CHECKER] blocking w/ spinlock or interrupt's disabled Manfred Spraul
2001-03-19 2:13 ` Dawson Engler
2001-03-20 19:11 ` george anzinger [this message]
2001-03-19 3:24 ` Linus Torvalds
-- strict thread matches above, loose matches on Subject: below --
2001-03-18 4:23 Dawson Engler
2001-03-23 14:47 ` Kurt Garloff
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=3AB7AB66.46D0AB8E@mvista.com \
--to=george@mvista.com \
--cc=engler@csl.Stanford.EDU \
--cc=linux-kernel@vger.kernel.org \
--cc=manfred@colorfullife.com \
--cc=mc@cs.Stanford.EDU \
/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