linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Stewart Smith <stewart@linux.vnet.ibm.com>
To: Anju T Sudhakar <anju@linux.vnet.ibm.com>,
	Michael Ellerman <mpe@ellerman.id.au>
Cc: linuxppc-dev@lists.ozlabs.org, linux-kernel@vger.kernel.org,
	maddy@linux.vnet.ibm.com, hemant@linux.vnet.ibm.com
Subject: Re: [PATCH] powerpc/powernv: Add kernel cmdline parameter to disable imc
Date: Thu, 12 Oct 2017 18:51:51 +1100	[thread overview]
Message-ID: <87sheoby7c.fsf@linux.vnet.ibm.com> (raw)
In-Reply-To: <06fe39eb-d5fe-4472-56b4-f66390d7fad9@linux.vnet.ibm.com>

Anju T Sudhakar <anju@linux.vnet.ibm.com> writes:
> On Wednesday 11 October 2017 01:55 AM, Stewart Smith wrote:
>> Michael Ellerman <mpe@ellerman.id.au> writes:
>>> Anju T Sudhakar <anju@linux.vnet.ibm.com> writes:
>>>
>>>> Add a kernel command line parameter option to disable In-Memory Collec=
tion
>>>> (IMC) counters and add documentation. This helps in debug.
>>> I'd really rather we didn't. Do we *really* need this?
>>>
>>> We don't have command line parameters to disable any of the other ~20
>>> PMUs, why is this one special?
>
> This one is really helpful in debugging, incase if we want to proceed=20
> without nest counters=C2=A0 OR
> core counters . But if we have the facility to do the same from=20
> petitboot, its fine.

https://patchwork.ozlabs.org/patch/824497/ (skiboot patch) should do the
same thing, right? That means we come up with them off (as we should
have from the start) and if you don't use the PMUs then the ucode won't
be started.

--=20
Stewart Smith
OPAL Architect, IBM.

  reply	other threads:[~2017-10-12  7:52 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-10-09  6:46 [PATCH] powerpc/powernv: Add kernel cmdline parameter to disable imc Anju T Sudhakar
2017-10-10  9:02 ` Michael Ellerman
2017-10-10 20:25   ` Stewart Smith
2017-10-11  8:56     ` Anju T Sudhakar
2017-10-12  7:51       ` Stewart Smith [this message]
2017-10-12  8:05         ` Madhavan Srinivasan
2017-10-12 12:05       ` 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=87sheoby7c.fsf@linux.vnet.ibm.com \
    --to=stewart@linux.vnet.ibm.com \
    --cc=anju@linux.vnet.ibm.com \
    --cc=hemant@linux.vnet.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=maddy@linux.vnet.ibm.com \
    --cc=mpe@ellerman.id.au \
    /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).