From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Jon Loeliger <jdl@jdl.com>
Cc: linuxppc-dev@ozlabs.org
Subject: Re: secondary CPU kicking on 86xx
Date: Sat, 17 Jun 2006 08:18:49 +1000 [thread overview]
Message-ID: <1150496329.23600.54.camel@localhost.localdomain> (raw)
In-Reply-To: <E1FrFmI-0002Vn-UE@jdl.com>
> Or we can dynamically rewrite a branch instruction into
> the reset vector from C code during smp_kick_cpu() time
> like the current powermac code does.
>
> I have working code for both; just need opinions
> and preferences on correct approach/style voiced!
Second approach. #ifdef are evil and they prevent multiple board support
in the same kernel.
Ben.
prev parent reply other threads:[~2006-06-16 22:19 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-16 14:58 secondary CPU kicking on 86xx Jon Loeliger
2006-06-16 22:18 ` Benjamin Herrenschmidt [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=1150496329.23600.54.camel@localhost.localdomain \
--to=benh@kernel.crashing.org \
--cc=jdl@jdl.com \
--cc=linuxppc-dev@ozlabs.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).