From: Robert Richter <rric@kernel.org>
To: Anton Blanchard <anton@samba.org>
Cc: oprofile-list@lists.sf.net, paulus@samba.org,
linuxppc-dev@lists.ozlabs.org
Subject: Re: [PATCH 1/2] oprofile: Disable oprofile NMI timer on ppc64
Date: Thu, 9 Apr 2015 07:43:52 +0200 [thread overview]
Message-ID: <20150409054352.GK4201@rric.localhost> (raw)
In-Reply-To: <1428547976-24890-1-git-send-email-anton@samba.org>
On 09.04.15 12:52:55, Anton Blanchard wrote:
> We want to enable the hard lockup detector on ppc64, but right now
> that enables the oprofile NMI timer too.
>
> We'd prefer not to enable the oprofile NMI timer, it adds another
> element to our PMU testing and it requires us to increase our
> exported symbols (eg cpu_khz).
>
> Modify the config entry for OPROFILE_NMI_TIMER to disable it on PPC64.
>
> Signed-off-by: Anton Blanchard <anton@samba.org>
Acked-by: Robert Richter <rric@kernel.org>
Please pass this patch along with patch 2 of this series (ppc tree or
so).
Thanks,
-Robert
> ---
> arch/Kconfig | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/arch/Kconfig b/arch/Kconfig
> index 05d7a8a..0cc605d 100644
> --- a/arch/Kconfig
> +++ b/arch/Kconfig
> @@ -32,7 +32,7 @@ config HAVE_OPROFILE
>
> config OPROFILE_NMI_TIMER
> def_bool y
> - depends on PERF_EVENTS && HAVE_PERF_EVENTS_NMI
> + depends on PERF_EVENTS && HAVE_PERF_EVENTS_NMI && !PPC64
>
> config KPROBES
> bool "Kprobes"
> --
> 2.1.0
>
prev parent reply other threads:[~2015-04-09 5:44 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-09 2:52 [PATCH 1/2] oprofile: Disable oprofile NMI timer on ppc64 Anton Blanchard
2015-04-09 2:52 ` [PATCH 2/2] powerpc: Add ppc64 hard lockup detector support Anton Blanchard
2015-04-09 23:48 ` Scott Wood
2015-04-09 5:43 ` Robert Richter [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=20150409054352.GK4201@rric.localhost \
--to=rric@kernel.org \
--cc=anton@samba.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=oprofile-list@lists.sf.net \
--cc=paulus@samba.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).