LinuxPPC-Dev Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: maddy <maddy@linux.vnet.ibm.com>
To: "Oliver O'Halloran" <oohall@gmail.com>
Cc: linuxppc-dev <linuxppc-dev@lists.ozlabs.org>
Subject: Re: [PATCH] powerpc/perf: Disable trace_imc pmu
Date: Thu, 14 Nov 2019 13:01:13 +0530	[thread overview]
Message-ID: <0710f396-e1c5-3891-0ac1-640f282e112d@linux.vnet.ibm.com> (raw)
In-Reply-To: <CAOSf1CF=6GA_W3PZq4fP9hJrkxc=RuAYUWDpRrTUWjiGTK_Wcw@mail.gmail.com>


On 11/14/19 12:50 PM, Oliver O'Halloran wrote:
> On Thu, Nov 14, 2019 at 6:19 PM Madhavan Srinivasan
> <maddy@linux.vnet.ibm.com> wrote:
>> When a root user or a user with CAP_SYS_ADMIN
>> privilege use trace_imc performance monitoring
>> unit events, to monitor application or KVM threads,
>> may result in a checkstop (System crash). Reason
>> being frequent switch of the "trace/accumulation"
>> mode of In-Memory Collection hardware.
>> This patch disables trace_imc pmu unit, but will
>> be re-enabled at a later stage with a fix patchset.
>> ---
>>   arch/powerpc/platforms/powernv/opal-imc.c | 7 ++++++-
>>   1 file changed, 6 insertions(+), 1 deletion(-)
>>
>> diff --git a/arch/powerpc/platforms/powernv/opal-imc.c b/arch/powerpc/platforms/powernv/opal-imc.c
>> index e04b20625cb9..5790f078771f 100644
>> --- a/arch/powerpc/platforms/powernv/opal-imc.c
>> +++ b/arch/powerpc/platforms/powernv/opal-imc.c
>> @@ -285,7 +285,12 @@ static int opal_imc_counters_probe(struct platform_device *pdev)
>>                          domain = IMC_DOMAIN_THREAD;
>>                          break;
>>                  case IMC_TYPE_TRACE:
>> -                       domain = IMC_DOMAIN_TRACE;
>> +                       /* Using trace_imc events to monitor
>> +                        * application or KVM thread performances
>> +                        * may result in a checkstop (system crash).
>> +                        * So disabling it for now.
>> +                        */
>> +                       domain = -1;
>>                          break;
>>                  default:
>>                          pr_warn("IMC Unknown Device type \n");
>> --
>> 2.21.0
>>
> Does this need a Fixes: tag?
I was thinking of adding this commit as a fixes tag for fix patchset. 
But if thats
not right, i can add the fixes tag along with a request to send to 
Stable and post a v2

Maddy


      reply	other threads:[~2019-11-14  7:33 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-11-14  7:18 [PATCH] powerpc/perf: Disable trace_imc pmu Madhavan Srinivasan
2019-11-14  7:20 ` Oliver O'Halloran
2019-11-14  7:31   ` maddy [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=0710f396-e1c5-3891-0ac1-640f282e112d@linux.vnet.ibm.com \
    --to=maddy@linux.vnet.ibm.com \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=oohall@gmail.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