From: Michael Ellerman <mpe@ellerman.id.au>
To: Anju T Sudhakar <anju@linux.vnet.ibm.com>,
Stewart Smith <stewart@linux.vnet.ibm.com>
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 23:05:36 +1100 [thread overview]
Message-ID: <87r2u8tvu7.fsf@concordia.ellerman.id.au> (raw)
In-Reply-To: <06fe39eb-d5fe-4472-56b4-f66390d7fad9@linux.vnet.ibm.com>
Anju T Sudhakar <anju@linux.vnet.ibm.com> writes:
> Hi mpe, stewart,
>
>
> 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 Collection
>>>> (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
> without nest counters OR
> core counters . But if we have the facility to do the same from
> petitboot, its fine.
I understand it's helpful for debugging.
But we can't afford to have a command line option to disable every
~1K SLOC of code.
If there's a compelling reason why we need to disable IMC *on production
systems* - then a command line option is a possibility. Though really if
there is a compelling reason for that maybe we have bigger problems :)
This is also a very new driver, so we're still finding some bugs, in a
few months it should be more stable and then the command line option
will just be cruft.
cheers
prev parent reply other threads:[~2017-10-12 12:05 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-09 6:46 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
2017-10-12 8:05 ` Madhavan Srinivasan
2017-10-12 12:05 ` 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=87r2u8tvu7.fsf@concordia.ellerman.id.au \
--to=mpe@ellerman.id.au \
--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=stewart@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®