linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Michael Ellerman <mpe@ellerman.id.au>,
	linuxppc dev list <linuxppc-dev@lists.ozlabs.org>
Cc: Stewart Smith <stewart@linux.vnet.ibm.com>,
	Michael Neuling <michael.neuling@au1.ibm.com>
Subject: Re: [PATCH] powerpc/powernv: Tell OPAL about our MMU mode
Date: Thu, 29 Jun 2017 08:53:00 -0500	[thread overview]
Message-ID: <1498744380.3651.45.camel@kernel.crashing.org> (raw)
In-Reply-To: <87efu3bc2z.fsf@concordia.ellerman.id.au>

On Thu, 2017-06-29 at 15:24 +1000, Michael Ellerman wrote:
> Benjamin Herrenschmidt <benh@kernel.crashing.org> writes:
> 
> > On Wed, 2017-06-28 at 15:17 +1000, Michael Ellerman wrote:
> > > Which doesn't really make sense. FSP says it's running (runtime).
> > > 
> > > The end of the OPAL log is below.
> > > 
> > > I think your patch means we're now calling slw_reinit(), whereas
> > > previously we would skip it?
> > 
> > Ugh... and slw_reinit() is somewhat broken I suppose these days. Drat.
> > 
> > Mikey, we probably need to key that off arch 300 or check for a DT prop
> > skiboot would put in that tells Linux it can do this.
> 
> DT prop of accepted reinit flags seems like it would work.
> 
> No prop means HILE_LE/HILE_BE

Maybe... The bug is only with p8 (and I'm changing skiboot to fix
even that) so I think I may just key off ARCH300... we'll see when I
get back to it, got bogged down with other things.

Ben.

      reply	other threads:[~2017-06-29 13:53 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-06-25 20:05 [PATCH] powerpc/powernv: Tell OPAL about our MMU mode Benjamin Herrenschmidt
2017-06-28  5:17 ` Michael Ellerman
2017-06-28 13:06   ` Benjamin Herrenschmidt
2017-06-29  5:24     ` Michael Ellerman
2017-06-29 13:53       ` 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=1498744380.3651.45.camel@kernel.crashing.org \
    --to=benh@kernel.crashing.org \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=michael.neuling@au1.ibm.com \
    --cc=mpe@ellerman.id.au \
    --cc=stewart@linux.vnet.ibm.com \
    /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).