From: Michael Neuling <mikey@neuling.org>
To: Michael Ellerman <mpe@ellerman.id.au>,
"Gautham R. Shenoy" <ego@linux.vnet.ibm.com>,
Benjamin Herrenschmidt <benh@kernel.crashing.org>,
Paul Mackerras <paulus@samba.org>,
Vaidyanathan Srinivasan <svaidy@linux.vnet.ibm.com>,
"Shreyas B. Prabhu" <shreyasbp@gmail.com>
Cc: linuxppc-dev@lists.ozlabs.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] powernv: Clear SPRN_PSSCR when a POWER9 CPU comes online
Date: Wed, 23 Nov 2016 10:35:16 +1100 [thread overview]
Message-ID: <1479857716.6542.60.camel@neuling.org> (raw)
In-Reply-To: <87bmx7um7s.fsf@concordia.ellerman.id.au>
On Wed, 2016-11-23 at 10:30 +1100, Michael Ellerman wrote:
> "Gautham R. Shenoy" <ego@linux.vnet.ibm.com> writes:
>=20
> > From: "Gautham R. Shenoy" <ego@linux.vnet.ibm.com>
> >=20
> > Ensure that PSSCR is set to a safe value corresponding to no
> > state-loss each time a POWER9 CPU comes online.
>=20
> Is this a bug fix? I can't tell from the change log.
There are no known bugs it's fixing. =C2=A0
It's just safer to run with a known default value, rather than what we rand=
omly
inherit from previous firmware.
Mikey
WARNING: multiple messages have this Message-ID (diff)
From: Michael Neuling <mikey@neuling.org>
To: Michael Ellerman <mpe@ellerman.id.au>,
"Gautham R. Shenoy" <ego@linux.vnet.ibm.com>,
Benjamin Herrenschmidt <benh@kernel.crashing.org>,
Paul Mackerras <paulus@samba.org>,
Vaidyanathan Srinivasan <svaidy@linux.vnet.ibm.com>,
"Shreyas B. Prabhu" <shreyasbp@gmail.com>
Cc: linuxppc-dev@lists.ozlabs.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] powernv: Clear SPRN_PSSCR when a POWER9 CPU comes online
Date: Wed, 23 Nov 2016 10:35:16 +1100 [thread overview]
Message-ID: <1479857716.6542.60.camel@neuling.org> (raw)
In-Reply-To: <87bmx7um7s.fsf@concordia.ellerman.id.au>
On Wed, 2016-11-23 at 10:30 +1100, Michael Ellerman wrote:
> "Gautham R. Shenoy" <ego@linux.vnet.ibm.com> writes:
>
> > From: "Gautham R. Shenoy" <ego@linux.vnet.ibm.com>
> >
> > Ensure that PSSCR is set to a safe value corresponding to no
> > state-loss each time a POWER9 CPU comes online.
>
> Is this a bug fix? I can't tell from the change log.
There are no known bugs it's fixing.
It's just safer to run with a known default value, rather than what we randomly
inherit from previous firmware.
Mikey
next prev parent reply other threads:[~2016-11-22 23:35 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-22 18:06 [PATCH] powernv: Clear SPRN_PSSCR when a POWER9 CPU comes online Gautham R. Shenoy
2016-11-22 23:30 ` Michael Ellerman
2016-11-22 23:35 ` Michael Neuling [this message]
2016-11-22 23:35 ` Michael Neuling
2016-11-23 0:32 ` Michael Neuling
2016-11-23 0:32 ` Michael Neuling
2016-11-28 12:15 ` Michael Ellerman
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=1479857716.6542.60.camel@neuling.org \
--to=mikey@neuling.org \
--cc=benh@kernel.crashing.org \
--cc=ego@linux.vnet.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mpe@ellerman.id.au \
--cc=paulus@samba.org \
--cc=shreyasbp@gmail.com \
--cc=svaidy@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 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.