From: Olof Johansson <olof@lixom.net>
To: Paul Mackerras <paulus@samba.org>
Cc: Becky Bruce <Becky.Bruce@freescale.com>,
Michael Schmitz <schmitz@zirkon.biophys.uni-duesseldorf.de>,
debian-powerpc@lists.debian.org,
linuxppc-dev list <linuxppc-dev@ozlabs.org>
Subject: Re: 7447A strange problem with MSR:POW (WAS: can't boot 2.6.17-rc1)
Date: Fri, 14 Apr 2006 14:54:36 -0500 [thread overview]
Message-ID: <20060414195436.GC24769@pb15.lixom.net> (raw)
In-Reply-To: <17471.62187.774127.783000@cargo.ozlabs.ibm.com>
Hi,
On Fri, Apr 14, 2006 at 12:07:23PM -0700, Paul Mackerras wrote:
> Becky Bruce writes:
>
> > Actually, I think the problem is that the code linux is using to turn
> > on nap mode is not guaranteed to put the processor in nap mode by the
> > time the blr in ppc6xx_idle occurs.
>
> Thanks, Becky.
>
> This patch fixes it for me. Comments, anyone?
The bf mnemonics had me scratching my head a while, it's not listed as
a simplified mnemonic in the 64-bit PEM. Two questions below.
> _GLOBAL(power_save_6xx_restore)
> + tophys(r11, r1) /* Make the idle task do a blr */
> + lwz r9,_LINK(r11)
> + stw r9,_NIP(r11)
> mfspr r11,SPRN_HID0
> - rlwinm. r11,r11,0,10,8 /* Clear NAP & copy NAP bit !state to cr1 EQ */
> - cror 4*cr1+eq,4*cr0+eq,4*cr0+eq
> + rlwinm r11,r11,0,10,8 /* Clear NAP */
> BEGIN_FTR_SECTION
> rlwinm r11,r11,0,9,7 /* Clear DOZE */
> END_FTR_SECTION_IFSET(CPU_FTR_CAN_DOZE)
> mtspr SPRN_HID0, r11
>
> #ifdef DEBUG
> - beq cr1,1f
> + bf 9,1f
Where is cr0 set now -- you took the dot off of rlwinm?
> lis r11,(nap_return_count-KERNELBASE)@ha
> lwz r9,nap_return_count@l(r11)
> addi r9,r9,1
> stw r9,nap_return_count@l(r11)
> 1:
> #endif
> -
> +
> +#ifdef CONFIG_SMP
> rlwinm r9,r1,0,0,18
> tophys(r9,r9)
> lwz r11,TI_CPU(r9)
> slwi r11,r11,2
> +#else
> + li r11,0
> +#endif
> /* Todo make sure all these are in the same page
> - * and load r22 (@ha part + CPU offset) only once
> + * and load r11 (@ha part + CPU offset) only once
> */
> BEGIN_FTR_SECTION
> - beq cr1,1f
> + bf 9,1f
Same comment as above w.r.t. cr0?
-Olof
next prev parent reply other threads:[~2006-04-14 19:54 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <Pine.LNX.4.44.0604071010290.18017-100000@zirkon.biophys.uni-duesseldorf.de>
[not found] ` <1144408805.30891.42.camel@localhost.localdomain>
[not found] ` <17463.9759.442768.685153@cargo.ozlabs.ibm.com>
2006-04-13 10:20 ` 7447A strange problem with MSR:POW (WAS: can't boot 2.6.17-rc1) Benjamin Herrenschmidt
2006-04-13 20:46 ` Becky Bruce
2006-04-13 20:55 ` Benjamin Herrenschmidt
2006-04-13 21:46 ` Becky Bruce
2006-04-13 22:37 ` Benjamin Herrenschmidt
2006-04-13 22:44 ` Olof Johansson
2006-04-14 19:07 ` Paul Mackerras
2006-04-14 19:54 ` Olof Johansson [this message]
2006-04-14 20:00 ` Becky Bruce
2006-04-14 22:57 ` Benjamin Herrenschmidt
2006-04-14 20:19 ` Paul Mackerras
2006-04-14 20:24 ` Olof Johansson
2006-04-14 21:09 ` Becky Bruce
2006-04-14 21:01 ` Benjamin Herrenschmidt
2006-04-18 5:45 ` Paul Mackerras
2006-04-18 6:00 ` Benjamin Herrenschmidt
2006-04-18 6:32 ` Paul Mackerras
2006-04-18 6:37 ` Benjamin Herrenschmidt
2006-04-18 14:56 ` Olof Johansson
2006-04-18 16:03 ` Olof Johansson
2006-04-15 11:12 ` Michael Schmitz
2006-04-18 19:29 Becky Bruce
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=20060414195436.GC24769@pb15.lixom.net \
--to=olof@lixom.net \
--cc=Becky.Bruce@freescale.com \
--cc=debian-powerpc@lists.debian.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=paulus@samba.org \
--cc=schmitz@zirkon.biophys.uni-duesseldorf.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.