From: Michael Ellerman <patch-notifications@ellerman•id.au>
To: Russell Currey <ruscur@russell•cc>, linuxppc-dev@lists•ozlabs.org
Cc: alistair@popple•id.au, gwshan@linux•vnet.ibm.com,
Russell Currey <ruscur@russell•cc>
Subject: Re: powerpc/powernv: Don't warn on PE init if unfreeze is unsupported
Date: Fri, 25 Nov 2016 11:04:08 +1100 (AEDT) [thread overview]
Message-ID: <3tPxBd2CWHz9t2G@ozlabs.org> (raw)
In-Reply-To: <20161116011226.24589-1-ruscur@russell.cc>
On Wed, 2016-11-16 at 01:12:26 UTC, Russell Currey wrote:
> Whenever a PE is initialised in powernv, opal_pci_eeh_freeze_clear() is
> called. This is to remove any existing freeze, and has no negative side
> effects if the PE is already in an unfrozen state. On PHB backends that
> don't support this operation and return OPAL_UNSUPPORTED, this creates a
> scary and misleading warning message.
>
> Skip the warning message on init if OPAL_UNSUPPORTED is returned.
>
> As far as I'm aware, this currently only affects NPUs.
>
> Fixes: 313483d ("powerpc/powernv: Unfreeze PE on allocation")
> Signed-off-by: Russell Currey <ruscur@russell•cc>
> Acked-by: Gavin Shan <gwshan@linux•vnet.ibm.com>
> Reviewed-by: Andrew Donnellan <andrew.donnellan@au1•ibm.com>
Applied to powerpc next, thanks.
https://git.kernel.org/powerpc/c/d4791db527bf397c84c9956c3ece96
cheers
prev parent reply other threads:[~2016-11-25 0:04 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-16 1:12 [PATCH] powerpc/powernv: Don't warn on PE init if unfreeze is unsupported Russell Currey
2016-11-16 1:22 ` Gavin Shan
2016-11-16 3:10 ` Andrew Donnellan
2016-11-25 0:04 ` 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=3tPxBd2CWHz9t2G@ozlabs.org \
--to=patch-notifications@ellerman$(echo .)id.au \
--cc=alistair@popple$(echo .)id.au \
--cc=gwshan@linux$(echo .)vnet.ibm.com \
--cc=linuxppc-dev@lists$(echo .)ozlabs.org \
--cc=ruscur@russell$(echo .)cc \
/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