From: linux@arm.linux.org.uk (Russell King - ARM Linux)
To: linux-arm-kernel@lists.infradead.org
Subject: init_kprobes() takes too much time during boot up
Date: Tue, 3 Jan 2012 09:09:24 +0000 [thread overview]
Message-ID: <20120103090924.GC2914@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <1324641249.2215.25.camel@linaro1>
On Fri, Dec 23, 2011 at 11:54:09AM +0000, Jon Medhurst (Tixy) wrote:
> Does Linux have some general IPI interface we could use to synchronize
> CPU rather than stop_machine? All we need to do is interrupt other cores
> and make them wait until we write a new instruction to memory and do a
> cache flush and relevant barrier instructions.
Maybe smp_call_function(). I'm not sure whether making the called
function spin until the calling CPU sets a flag is a good idea though -
that sounds like it could cause lockups by preventing other IPIs
happening. Bear in mind that calling flush_* functions from IPIs is
not a good idea because they'll want to IPI themselves - you have to
use the local_flush_* stuff instead.
prev parent reply other threads:[~2012-01-03 9:09 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-23 3:06 init_kprobes() takes too much time during boot up Eric Miao
2011-12-23 3:20 ` Nicolas Pitre
2011-12-23 11:54 ` Jon Medhurst (Tixy)
2012-01-03 9:09 ` Russell King - ARM Linux [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=20120103090924.GC2914@n2100.arm.linux.org.uk \
--to=linux@arm.linux.org.uk \
--cc=linux-arm-kernel@lists.infradead.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;
as well as URLs for NNTP newsgroup(s).