From: Thomas Hood <jdthood@mail.com>
To: unlisted-recipients:; (no To-header on input)@localhost.localdomain
Cc: linux-kernel@vger.kernel.org
Subject: Re: Question about rtc_lock
Date: 06 Oct 2001 10:40:54 -0400 [thread overview]
Message-ID: <1002379256.857.3.camel@thanatos> (raw)
In-Reply-To: <E15prGs-0001G3-00@the-village.bc.nu>
In-Reply-To: <E15prGs-0001G3-00@the-village.bc.nu>
On Sat, 2001-10-06 at 09:13, Alan Cox wrote:
> > No, but what if the rtc interrupts while the lock is held in this
> > bit of code?
>
> Thats fine. It wont take the lock
But the first line of irq_interrupt() is:
spin_lock (&rtc_lock);
If one has a multi-processor machine, and CPUx is going through
the bootflag code, which takes the rtc_lock, and that CPU is
interrupted and enters rtc_interrupt(), which tries to take the
rtc_lock, won't it deadlock?
If not, then I'm missing some clue about how these spinlocks work.
Thomas
next prev parent reply other threads:[~2001-10-06 14:41 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-10-06 3:49 Question about rtc_lock Thomas Hood
2001-10-06 13:01 ` Alan Cox
2001-10-06 13:06 ` Thomas Hood
2001-10-06 13:13 ` Alan Cox
2001-10-06 14:40 ` Thomas Hood [this message]
2001-10-06 15:24 ` Jonathan Lundell
2001-10-07 3:24 ` Thomas Hood
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=1002379256.857.3.camel@thanatos \
--to=jdthood@mail.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