From: Ingo Molnar <mingo@kernel.org>
To: Borislav Petkov <bp@alien8.de>
Cc: Robert Richter <rric@kernel.org>,
Arnaldo Carvalho de Melo <acme@kernel.org>,
Peter Zijlstra <peterz@infradead.org>,
Vince Weaver <vince@deater.net>,
lkml <linux-kernel@vger.kernel.org>
Subject: Re: [RFC PATCH] perf/stat: Add --disable-hwdt
Date: Sat, 11 Feb 2017 18:59:10 +0100 [thread overview]
Message-ID: <20170211175910.GA31544@gmail.com> (raw)
In-Reply-To: <20170211170330.nm2ew4nxwa2mn3fo@pd.tnic>
* Borislav Petkov <bp@alien8.de> wrote:
> Ok,
>
> turns out perf-list(1) already talks about it in the "EVENT GROUPS"
> section. How about this then:
>
> ---
> diff --git a/tools/perf/builtin-stat.c b/tools/perf/builtin-stat.c
> index a02f2e965628..2d18283574db 100644
> --- a/tools/perf/builtin-stat.c
> +++ b/tools/perf/builtin-stat.c
> @@ -146,6 +146,7 @@ static aggr_get_id_t aggr_get_id;
> static bool append_file;
> static const char *output_name;
> static int output_fd;
> +static int print_free_counters_hint;
>
> struct perf_stat {
> bool record;
> @@ -1109,6 +1110,9 @@ static void printout(int id, int nr, struct perf_evsel *counter, double uval,
> counter->supported ? CNTR_NOT_COUNTED : CNTR_NOT_SUPPORTED,
> csv_sep);
>
> + if (counter->supported)
> + print_free_counters_hint = 1;
> +
> fprintf(stat_config.output, "%-*s%s",
> csv_output ? 0 : unit_width,
> counter->unit, csv_sep);
> @@ -1476,7 +1480,13 @@ static void print_footer(void)
> print_noise_pct(stddev_stats(&walltime_nsecs_stats),
> avg_stats(&walltime_nsecs_stats));
> }
> +
> fprintf(output, "\n\n");
> +
> + if (print_free_counters_hint)
> + fprintf(output,
> +"Some events couldn't be scheduled. Consider freeing some counters by disabling the NMI watchdog temporarily, \n"
> +"for example. See perf-list(1) manpage.\n");
So I checked the perf-list manpage and it didn't tell me much about how to disable
the NMI watchdog.
How about a more proactive hint, something like:
To disable the NMI watchdog permanently, do:
sudo echo kernel.nmi_watchdog=0 >> /etc/sysctl.conf
sudo sysctl -p
? (untested!)
Thanks,
Ingo
next prev parent reply other threads:[~2017-02-11 17:59 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-06 12:15 [RFC PATCH] perf/stat: Add --disable-hwdt Borislav Petkov
2017-02-06 12:22 ` Ingo Molnar
2017-02-06 12:41 ` Borislav Petkov
2017-02-06 12:44 ` Ingo Molnar
2017-02-06 12:49 ` Borislav Petkov
2017-02-06 13:18 ` Robert Richter
2017-02-06 13:23 ` Borislav Petkov
2017-02-07 7:25 ` Ingo Molnar
2017-02-07 10:54 ` Borislav Petkov
2017-02-07 15:06 ` Borislav Petkov
2017-02-11 17:03 ` Borislav Petkov
2017-02-11 17:59 ` Ingo Molnar [this message]
2017-02-11 18:32 ` Borislav Petkov
2017-02-11 20:41 ` Ingo Molnar
2017-03-07 7:21 ` [tip:perf/core] perf stat: Issue a HW watchdog disable hint tip-bot for Borislav Petkov
2017-02-06 14:23 ` [RFC PATCH] perf/stat: Add --disable-hwdt Vince Weaver
2017-02-06 17:02 ` Borislav Petkov
2017-02-07 1:08 ` Borislav Petkov
2017-02-07 1:09 ` [PATCH 1/2] tools/lib/api/fs: Add procfs int read/write helpers Borislav Petkov
2017-02-07 1:43 ` Arnaldo Carvalho de Melo
2017-02-07 10:30 ` Borislav Petkov
2017-02-07 15:00 ` Arnaldo Carvalho de Melo
2017-02-07 15:08 ` Borislav Petkov
2017-02-07 15:34 ` Arnaldo Carvalho de Melo
2017-02-07 1:10 ` [PATCH 2/2] perf stat: Disable HW watchdog around a perf stat session Borislav Petkov
2017-02-07 1:45 ` Arnaldo Carvalho de Melo
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=20170211175910.GA31544@gmail.com \
--to=mingo@kernel.org \
--cc=acme@kernel.org \
--cc=bp@alien8.de \
--cc=linux-kernel@vger.kernel.org \
--cc=peterz@infradead.org \
--cc=rric@kernel.org \
--cc=vince@deater.net \
/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