From: Russell King <rmk@arm.linux.org.uk>
To: andrewm@uow.edu.au (Andrew Morton)
Cc: jsimmons@suse.com (James Simmons),
linux-kernel@vger.kernel.org (Linux Kernel Mailing List),
linux-fbdev@vuser.vu.union.edu (FrameBuffer List),
linuxconsole-dev@lists.sourceforge.net (Linux console project)
Subject: Re: console spin_lock
Date: Thu, 18 Jan 2001 21:50:15 +0000 (GMT) [thread overview]
Message-ID: <200101182150.f0ILoFp30979@flint.arm.linux.org.uk> (raw)
In-Reply-To: <3A66E4D3.B2BEFCBB@uow.edu.au> from "Andrew Morton" at Jan 18, 2001 11:42:59 PM
Andrew Morton writes:
> The subtler problem will be interrupt-capable drivers which
> do a bare spin_lock() to serialise wrt their interrupt routines,
> relying upon interrupts being disabled. They'll be deadlocky
> and will need changing. That's trivial to find and fix though.
Uhh, what if you have this situation:
interrupt (level triggered)
enter interrupt handler
printk (can re-enable interrupts?)
enter interrupt handler
printk (can re-enable interrupts?)
enter interrupt handler
printk (can re-enable interrupts?)
....
So surely this isn't a new problem?
_____
|_____| ------------------------------------------------- ---+---+-
| | Russell King rmk@arm.linux.org.uk --- ---
| | | | http://www.arm.linux.org.uk/personal/aboutme.html / / |
| +-+-+ --- -+-
/ | THE developer of ARM Linux |+| /|\
/ | | | --- |
+-+-+ ------------------------------------------------- /\\\ |
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2001-01-18 22:05 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-17 0:05 James Simmons
2001-01-17 13:49 ` Andrew Morton
2001-01-17 18:22 ` Roman Zippel
2001-01-17 23:40 ` James Simmons
2001-01-18 12:42 ` Andrew Morton
2001-01-18 21:50 ` Russell King [this message]
2001-01-19 1:23 ` James Simmons
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=200101182150.f0ILoFp30979@flint.arm.linux.org.uk \
--to=rmk@arm.linux.org.uk \
--cc=andrewm@uow.edu.au \
--cc=jsimmons@suse.com \
--cc=linux-fbdev@vuser.vu.union.edu \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxconsole-dev@lists.sourceforge.net \
/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®