From: Ingo Molnar <mingo@elte.hu>
To: Andrew Morton <akpm@osdl.org>
Cc: Thomas Hood <jdthood@yahoo.co.uk>, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Documentation/preempt-locking.txt clarification
Date: Wed, 10 Nov 2004 12:03:13 +0100 [thread overview]
Message-ID: <20041110110313.GA5493@elte.hu> (raw)
In-Reply-To: <20041110005742.35828d2b.akpm@osdl.org>
* Andrew Morton <akpm@osdl.org> wrote:
> But I don't see why that's needed: if the preempt command came from
> another CPU then this CPU will take the cross-CPU interrupt as soon as
> interrupts are enabled. And the preempt command couldn't have come
> from _this_ CPU, because it had interrupts disabled.
this CPU can easily trigger a reschedule by _waking_ another task
synchronously (from within the irqs-off section) and hence causing
itself to preempt. I'd not say it's common, but it can happen in quite
unexpected places, so i'd encourage us to keep the more cautious advice
that is in the current text.
Ingo
prev parent reply other threads:[~2004-11-10 10:01 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1073302283.1903.85.camel@thanatos.hubertnet>
[not found] ` <1074561880.26456.26.camel@localhost>
2004-11-10 8:21 ` Thomas Hood
2004-11-10 8:57 ` Andrew Morton
2004-11-10 9:27 ` Thomas Hood
2004-11-10 9:45 ` Andrew Morton
2004-11-10 10:59 ` Ingo Molnar
2004-11-10 11:03 ` Ingo Molnar [this message]
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=20041110110313.GA5493@elte.hu \
--to=mingo@elte.hu \
--cc=akpm@osdl.org \
--cc=jdthood@yahoo.co.uk \
--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
Powered by JetHome