From: 류호은 <hoeun.ryu@lge.com>
To: <mingo@kernel.org>, <peterz@infradead.org>, <aaron.lu@intel.com>,
<adobriyan@gmail.com>, <frederic@kernel.org>,
<ying.huang@intel.com>
Cc: <linux-kernel@vger.kernel.org>
Subject: smp_call_function() friends and irq/bottom_half context
Date: Thu, 10 May 2018 13:58:29 +0900 [thread overview]
Message-ID: <00fb01d3e81b$89b9c2d0$9d2d4870$@lge.com> (raw)
Hi, all.
I'm reading kernel/smp.c code and I found comments on smp_call_function()
and smp_call_function_[single/many]
saying that these functions are cannot be called in interrupt disabled
context or irq/bottom half handlers.
I understand that there is a potential deadlock issue when caller CPU of
the functions is waiting for the completion of the callback of other CPUs.
But I was wondering if this is the case even when the caller CPU doesn't
wait for the completion (wait == 0).
Thank you.
next reply other threads:[~2018-05-10 4:58 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-10 4:58 류호은 [this message]
2018-05-10 10:16 ` smp_call_function() friends and irq/bottom_half context Peter Zijlstra
2018-05-11 6:24 ` Hoeun Ryu
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='00fb01d3e81b$89b9c2d0$9d2d4870$@lge.com' \
--to=hoeun.ryu@lge.com \
--cc=aaron.lu@intel.com \
--cc=adobriyan@gmail.com \
--cc=frederic@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=peterz@infradead.org \
--cc=ying.huang@intel.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;
as well as URLs for NNTP newsgroup(s).