From: Robert Love <rml@tech9.net>
To: Oliver Neukum <oliver@neukum.name>
Cc: Thunder from the hill <thunder@lightweight.ods.org>,
Ralf Baechle <ralf@uni-koblenz.de>,
linux-kernel@vger.kernel.org
Subject: Re: question on spinlocks
Date: 01 Sep 2002 18:11:12 -0400 [thread overview]
Message-ID: <1030918273.12110.3126.camel@phantasy> (raw)
In-Reply-To: <200209020002.41381.oliver@neukum.name>
On Sun, 2002-09-01 at 18:02, Oliver Neukum wrote:
>
> > > No; spin_lock_irqsave/spin_unlock_irqrestore and spin_lock/spin_unlock
> > > have to be used in matching pairs.
> >
> > If it was his least problem! He'll run straight into a "schedule w/IRQs
> > disabled" bug.
>
> OK, how do I drop an irqsave spinlock if I don't have flags?
See my previous message.
Do not do what you are trying to do. Dropping a lock and calling
schedule is fine. Ditto with the interrupt part.
But note:
- interrupts will be reenabled when you reschedule and still
enabled when your task is finally running again.
- Since interrupts are going to magically restore, if you are
worried about the state of interrupts previous to your
function... you have a problem.
OK?
Robert Love
next prev parent reply other threads:[~2002-09-01 22:06 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-01 17:27 question on spinlocks Oliver Neukum
2002-09-01 19:05 ` Ralf Baechle
2002-09-01 21:53 ` Thunder from the hill
2002-09-01 22:02 ` Oliver Neukum
2002-09-01 22:09 ` Thunder from the hill
2002-09-01 22:11 ` Robert Love
2002-09-01 22:33 ` Oliver Neukum
2002-09-02 22:30 ` Jan Hudec
2002-09-03 22:13 ` george anzinger
2002-09-01 22:11 ` Robert Love [this message]
2002-09-01 22:08 ` Robert Love
2002-09-01 22:16 ` Thunder from the hill
[not found] ` <mailman.1030918200.24262.linux-kernel2news@redhat.com>
2002-09-03 20:09 ` Pete Zaitcev
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=1030918273.12110.3126.camel@phantasy \
--to=rml@tech9.net \
--cc=linux-kernel@vger.kernel.org \
--cc=oliver@neukum.name \
--cc=ralf@uni-koblenz.de \
--cc=thunder@lightweight.ods.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