From: Leonardo Bras <leonardo@linux.ibm.com>
To: "Desnes A. Nunes do Rosario" <desnesn@linux.ibm.com>,
linuxppc-dev@lists.ozlabs.org
Cc: gromero@linux.ibm.com
Subject: Re: [PATCH, v2] powerpc: fix hardware PMU exception bug on PowerVM compatibility mode systems
Date: Thu, 27 Feb 2020 12:25:20 -0300 [thread overview]
Message-ID: <65b583ab89ebff348f5e464740da863a8f7f22b5.camel@linux.ibm.com> (raw)
In-Reply-To: <20200227134715.9715-1-desnesn@linux.ibm.com>
[-- Attachment #1: Type: text/plain, Size: 1630 bytes --]
On Thu, 2020-02-27 at 10:47 -0300, Desnes A. Nunes do Rosario wrote:
> PowerVM systems running compatibility mode on a few Power8 revisions are
> still vulnerable to the hardware defect that loses PMU exceptions arriving
> prior to a context switch.
>
> The software fix for this issue is enabled through the CPU_FTR_PMAO_BUG
> cpu_feature bit, nevertheless this bit also needs to be set for PowerVM
> compatibility mode systems.
>
> Fixes: 68f2f0d431d9ea4 ("powerpc: Add a cpu feature CPU_FTR_PMAO_BUG")
> Signed-off-by: Desnes A. Nunes do Rosario <desnesn@linux.ibm.com>
> ---
> arch/powerpc/kernel/cputable.c | 4 +++-
> 1 file changed, 3 insertions(+), 1 deletion(-)
>
> diff --git a/arch/powerpc/kernel/cputable.c b/arch/powerpc/kernel/cputable.c
> index e745abc5457a..245be4fafe13 100644
> --- a/arch/powerpc/kernel/cputable.c
> +++ b/arch/powerpc/kernel/cputable.c
> @@ -2193,11 +2193,13 @@ static struct cpu_spec * __init setup_cpu_spec(unsigned long offset,
> * oprofile_cpu_type already has a value, then we are
> * possibly overriding a real PVR with a logical one,
> * and, in that case, keep the current value for
> - * oprofile_cpu_type.
> + * oprofile_cpu_type. Futhermore, let's ensure that the
> + * fix for the PMAO bug is enabled on compatibility mode.
> */
> if (old.oprofile_cpu_type != NULL) {
> t->oprofile_cpu_type = old.oprofile_cpu_type;
> t->oprofile_type = old.oprofile_type;
> + t->cpu_features |= old.cpu_features & CPU_FTR_PMAO_BUG;
> }
> }
>
Looks good to me.
Reviewed-by: Leonardo Bras <leonardo@linux.ibm.com>
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2020-02-27 15:33 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-27 13:47 [PATCH, v2] powerpc: fix hardware PMU exception bug on PowerVM compatibility mode systems Desnes A. Nunes do Rosario
2020-02-27 15:25 ` Leonardo Bras [this message]
2020-03-06 0:11 ` 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=65b583ab89ebff348f5e464740da863a8f7f22b5.camel@linux.ibm.com \
--to=leonardo@linux.ibm.com \
--cc=desnesn@linux.ibm.com \
--cc=gromero@linux.ibm.com \
--cc=linuxppc-dev@lists.ozlabs.org \
/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).