From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Jon Loeliger <jdl@jdl.com>
Cc: linuxppc-dev@ozlabs.org
Subject: Re: [PATCH 4/9 v3] Add starting of secondary 86xx CPUs.
Date: Sun, 18 Jun 2006 13:05:17 +1000 [thread overview]
Message-ID: <1150599918.23600.150.camel@localhost.localdomain> (raw)
In-Reply-To: <E1Frjem-0004Ou-2S@jdl.com>
> + .globl __secondary_start_mpc86xx
> +__secondary_start_mpc86xx:
> + mfspr r3, SPRN_PIR
> + stw r3, __secondary_hold_acknowledge@l(0)
> + mr r24, r3 /* cpu # */
> + b __secondary_start
The above looks generic enough... why not call it
__secondary_start_PIR ? :) Might be useful for other platforms I
reckon...
> .globl __secondary_start_pmac_0
> __secondary_start_pmac_0:
> /* NB the entries for cpus 0, 1, 2 must each occupy 8 bytes. */
> @@ -1088,7 +1095,12 @@ load_up_mmu:
> LOAD_BAT(1,r3,r4,r5)
> LOAD_BAT(2,r3,r4,r5)
> LOAD_BAT(3,r3,r4,r5)
> -
> +BEGIN_FTR_SECTION
> + LOAD_BAT(4,r3,r4,r5)
> + LOAD_BAT(5,r3,r4,r5)
> + LOAD_BAT(6,r3,r4,r5)
> + LOAD_BAT(7,r3,r4,r5)
> +END_FTR_SECTION_IFSET(CPU_FTR_HAS_HIGH_BATS)
> blr
Looks good.
next prev parent reply other threads:[~2006-06-18 3:05 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-17 22:52 [PATCH 4/9 v3] Add starting of secondary 86xx CPUs Jon Loeliger
2006-06-18 3:05 ` Benjamin Herrenschmidt [this message]
2006-06-19 14:06 ` Jon Loeliger
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=1150599918.23600.150.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).