linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Becky Bruce <Becky.Bruce@freescale.com>
Cc: linuxppc-dev list <linuxppc-dev@ozlabs.org>,
	Michael Schmitz <schmitz@zirkon.biophys.uni-duesseldorf.de>,
	debian-powerpc@lists.debian.org,
	Paul Mackerras <paulus@samba.org>
Subject: Re: 7447A strange problem with MSR:POW (WAS: can't boot 2.6.17-rc1)
Date: Fri, 14 Apr 2006 06:55:37 +1000	[thread overview]
Message-ID: <1144961737.4935.28.camel@localhost.localdomain> (raw)
In-Reply-To: <21F7D7D8-B9BC-44EB-B07B-F888D89DCF25@freescale.com>


> 
> The above code should really look like this:
> 
>          mfmsr   r7
>          ori     r7,r7,MSR_EE
>          oris    r7,r7,MSR_POW@h
>          sync
>          isync
>          mtmsr   r7
>          isync
> label:
>          b label
> 	blr

Ohhh ... we always assumed mtmsr with MSR_POW was
immediate/synchronous ! That explains a lot. The problem with the above
though is that we'll never get out unless we also hack the exception
path to change the return address once an exception happens. It's not
that difficult especially since we already have a special case to handle
returning from NAP there, on ppc32 at least. ppc64 will need a bit more
investigation.

Do you see another way to loop until NAP has gone ? Maybe reading msr in
a loop until POW gets cleared would do the trick ?

> Hope this helps - I don't have hardware to test this on, so I can't  
> be sure, but it seems to explain the behavior you're seeing if I'm  
> understanding the problem correctly.

It definitely does ! Thanks a lot.

Ben.

  reply	other threads:[~2006-04-13 20:55 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 [this message]
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
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=1144961737.4935.28.camel@localhost.localdomain \
    --to=benh@kernel.crashing.org \
    --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 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).