public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Peter Zijlstra <peterz@infradead.org>
To: kan.liang@intel.com
Cc: mingo@redhat.com, acme@kernel.org,
	alexander.shishkin@linux.intel.com, ak@linux.intel.com,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/1] perf/core: fix implicitly enable dynamic interrupt throttle
Date: Thu, 12 May 2016 11:31:27 +0200	[thread overview]
Message-ID: <20160512093127.GI3190@twins.programming.kicks-ass.net> (raw)
In-Reply-To: <1462260366-3160-1-git-send-email-kan.liang@intel.com>

On Tue, May 03, 2016 at 12:26:06AM -0700, kan.liang@intel.com wrote:
> From: Kan Liang <kan.liang@intel.com>
> 
> This patch fixes an issue which was introduced from 'commit 91a612eea9a3
> ("perf/core: Fix dynamic interrupt throttle")'
> The old patch unconditionally sets the perf_sample_allowed_ns value to
> !0. But that could trigger an issue in the following corner case.
> The user can disable the dynamic interrupt throttle mechanism by setting
> perf_cpu_time_max_percent to 0. Then they changes
> perf_event_max_sample_rate.
> For this case, the mechanism will be enabled implicitly, because
> perf_sample_allowed_ns becomes !0.
> 
> This patch only updates the perf_sample_allowed_ns when the dynamic
> interrupt throttle mechanism is enabled.
> 
> Signed-off-by: Kan Liang <kan.liang@intel.com>
> ---
>  kernel/events/core.c | 8 ++++++++
>  1 file changed, 8 insertions(+)
> 
> diff --git a/kernel/events/core.c b/kernel/events/core.c
> index 4e2ebf6..4042a3d 100644
> --- a/kernel/events/core.c
> +++ b/kernel/events/core.c
> @@ -375,6 +375,14 @@ static void update_perf_cpu_limits(void)
>  {
>  	u64 tmp = perf_sample_period_ns;
>  
> +	/*
> +	 * Don't update the perf_sample_allowed_ns,
> +	 * if the dynamic interrupt throttle mechanism is disabled.
> +	 */
> +	if (sysctl_perf_cpu_time_max_percent == 100 ||
> +	    sysctl_perf_cpu_time_max_percent == 0)
> +		return;
> +


Hmm, would it not be nicer to simply reject the write instead of
silently ignoring it?

---
 kernel/events/core.c | 7 +++++++
 1 file changed, 7 insertions(+)

diff --git a/kernel/events/core.c b/kernel/events/core.c
index 050a290c72c7..0a51a568d4eb 100644
--- a/kernel/events/core.c
+++ b/kernel/events/core.c
@@ -396,6 +396,13 @@ int perf_proc_update_handler(struct ctl_table *table, int write,
 	if (ret || !write)
 		return ret;
 
+	/*
+	 * If the throttling is disabled; don't allow the write.
+	 */
+	if (sysctl_perf_cpu_time_max_percent == 100 ||
+	    sysctl_perf_cpu_time_max_percent == 0)
+		return -EINVAL;
+
 	max_samples_per_tick = DIV_ROUND_UP(sysctl_perf_event_sample_rate, HZ);
 	perf_sample_period_ns = NSEC_PER_SEC / sysctl_perf_event_sample_rate;
 	update_perf_cpu_limits();

  reply	other threads:[~2016-05-12  9:31 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-05-03  7:26 [PATCH 1/1] perf/core: fix implicitly enable dynamic interrupt throttle kan.liang
2016-05-12  9:31 ` Peter Zijlstra [this message]
2016-05-12 13:26   ` Liang, Kan
2016-06-03 10:50 ` [tip:perf/core] perf/core: Fix " tip-bot for Kan Liang

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=20160512093127.GI3190@twins.programming.kicks-ass.net \
    --to=peterz@infradead.org \
    --cc=acme@kernel.org \
    --cc=ak@linux.intel.com \
    --cc=alexander.shishkin@linux.intel.com \
    --cc=kan.liang@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.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