From: Michael Ellerman <patch-notifications@ellerman•id.au>
To: Benjamin Herrenschmidt <benh@kernel•crashing.org>,
linuxppc-dev@ozlabs•org
Cc: Russell Currey <ruscur@au1•ibm.com>
Subject: Re: [2/2] powerpc/powernv: Rework EEH initialization on powernv
Date: Wed, 27 Sep 2017 20:32:15 +1000 (AEST) [thread overview]
Message-ID: <3y2Df70nk9z9tXs@ozlabs.org> (raw)
In-Reply-To: <1504766144.12628.15.camel@kernel.crashing.org>
On Thu, 2017-09-07 at 06:35:44 UTC, Benjamin Herrenschmidt wrote:
> Remove the post_init callback which is only used
> by powernv, we can just call it explicitly from
> the powernv code.
>
> This partially kills the ability to "disable" eeh at
> runtime via debugfs as this was calling that same
> callback again, but this is both unused and broken
> in several ways. If we want to revive it, we need
> to create a dedicated enable/disable callback on the
> backend that does the right thing.
>
> Let the bulk of eeh initialize normally at
> core_initcall() like it does on pseries by removing
> the hack in eeh_init() that delays it.
>
> Instead we make sure our eeh->probe cleanly bails
> out of the PEs haven't been created yet and we force
> a re-probe where we used to call eeh_init() again.
>
> Signed-off-by: Benjamin Herrenschmidt <benh@kernel•crashing.org>
> Acked-by: Russell Currey <ruscur@russell•cc>
Patch 2 applied to powerpc next, thanks.
https://git.kernel.org/powerpc/c/b9fde58db7e5738cacb740b0ec5479
cheers
prev parent reply other threads:[~2017-09-27 10:32 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-07 6:35 [PATCH 2/2] powerpc/powernv: Rework EEH initialization on powernv Benjamin Herrenschmidt
2017-09-14 1:12 ` Russell Currey
2017-09-27 10:32 ` Michael Ellerman [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=3y2Df70nk9z9tXs@ozlabs.org \
--to=patch-notifications@ellerman$(echo .)id.au \
--cc=benh@kernel$(echo .)crashing.org \
--cc=linuxppc-dev@ozlabs$(echo .)org \
--cc=ruscur@au1$(echo .)ibm.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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