From: Manfred Spraul <manfred@colorfullife.com>
To: Zwane Mwaikambo <zwane@fsmlabs.com>
Cc: linux-kernel@vger.kernel.org, Andrew Morton <akpm@osdl.org>
Subject: Re: [PATCH] smp_call_function WARN_ON
Date: Sun, 15 Aug 2004 08:55:13 +0200 [thread overview]
Message-ID: <411F08D1.7060400@colorfullife.com> (raw)
Zwane wrote:
>The WARN_ON() is really only true if you're waiting for the other
>processors.
>
>
>
Wrong: At least on i386 the code always waits for delivery of the IPI,
it just doesn't wait for completion of the callback.
Do you need IPIs from irq or bh context? It would be tricky to change
the current code: an IPI just delivers an interrupt without any payload.
The global 'call_data' variable contains the description of the IPI and
accesses to it must be synchronized.
IPIs from BH context do no work either: they can deadlock against the
tasklist_lock: the first cpu calls read_lock(&tasklist_lock) from
process context, another cpu calls write_lock_irq(&tasklist_lock), and
then the first cpu tries smp_call_function() from bh context.
--
Manfred
next reply other threads:[~2004-08-15 6:52 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-15 6:55 Manfred Spraul [this message]
2004-08-15 7:51 ` Zwane Mwaikambo
-- strict thread matches above, loose matches on Subject: below --
2004-08-15 3:03 Zwane Mwaikambo
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=411F08D1.7060400@colorfullife.com \
--to=manfred@colorfullife.com \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=zwane@fsmlabs.com \
/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®