From: "Liang, Kan" <kan.liang@linux.intel.com>
To: Jiri Olsa <jolsa@redhat.com>
Cc: acme@kernel.org, mingo@redhat.com, peterz@infradead.org,
linux-kernel@vger.kernel.org, mark.rutland@arm.com,
namhyung@kernel.org, ravi.bangoria@linux.ibm.com,
yao.jin@linux.intel.com, ak@linux.intel.com
Subject: Re: [PATCH 4/5] perf metricgroup: Support metric constraint
Date: Thu, 20 Feb 2020 11:14:09 -0500 [thread overview]
Message-ID: <fea147db-2af3-e9ec-fb23-f9db8cf1c77a@linux.intel.com> (raw)
In-Reply-To: <20200220113530.GA565976@krava>
On 2/20/2020 6:35 AM, Jiri Olsa wrote:
> On Wed, Feb 19, 2020 at 11:08:39AM -0800, kan.liang@linux.intel.com wrote:
>
> SNIP
>
>> +static bool violate_nmi_constraint;
>> +
>> +static bool metricgroup__has_constraint(struct pmu_event *pe)
>> +{
>> + if (!pe->metric_constraint)
>> + return false;
>> +
>> + if (!strcmp(pe->metric_constraint, "NO_NMI_WATCHDOG") &&
>> + sysctl__nmi_watchdog_enabled()) {
>> + pr_warning("Splitting metric group %s into standalone metrics.\n",
>> + pe->metric_name);
>> + violate_nmi_constraint = true;
>
> no static flags plz.. can't you just print that rest of the warning in here?
>
Because we only want to print the NMI watchdog warning once.
If there are more than one metric groups with constraint, the warning
may be printed several times. For example,
$ perf stat -M Page_Walks_Utilization,Page_Walks_Utilization
Splitting metric group Page_Walks_Utilization into standalone metrics.
Try disabling the NMI watchdog to comply NO_NMI_WATCHDOG metric
constraint:
echo 0 > /proc/sys/kernel/nmi_watchdog
perf stat ...
echo 1 > /proc/sys/kernel/nmi_watchdog
Splitting metric group Page_Walks_Utilization into standalone metrics.
Try disabling the NMI watchdog to comply NO_NMI_WATCHDOG metric
constraint:
echo 0 > /proc/sys/kernel/nmi_watchdog
perf stat ...
echo 1 > /proc/sys/kernel/nmi_watchdog
Is it OK?
If it's OK, I think we can remove the flag.
Thanks,
Kan
> jirka
>
>> + return true;
>> + }
>> +
>> + return false;
>> +}
>> +
>> static int metricgroup__add_metric(const char *metric, struct strbuf *events,
>> struct list_head *group_list)
>> {
>> @@ -460,7 +490,10 @@ static int metricgroup__add_metric(const char *metric, struct strbuf *events,
>> if (events->len > 0)
>> strbuf_addf(events, ",");
>>
>> - metricgroup__add_metric_weak_group(events, ids, idnum);
>> + if (metricgroup__has_constraint(pe))
>> + metricgroup__add_metric_non_group(events, ids, idnum);
>> + else
>> + metricgroup__add_metric_weak_group(events, ids, idnum);
>>
>> eg = malloc(sizeof(struct egroup));
>> if (!eg) {
>> @@ -544,6 +577,13 @@ int metricgroup__parse_groups(const struct option *opt,
>> strbuf_release(&extra_events);
>> ret = metricgroup__setup_events(&group_list, perf_evlist,
>> metric_events);
>> +
>> + if (violate_nmi_constraint) {
>> + pr_warning("Try disabling the NMI watchdog to comply NO_NMI_WATCHDOG metric constraint:\n"
>> + " echo 0 > /proc/sys/kernel/nmi_watchdog\n"
>> + " perf stat ...\n"
>> + " echo 1 > /proc/sys/kernel/nmi_watchdog\n");
>> + }
>> out:
>> metricgroup__free_egroups(&group_list);
>> return ret;
>> --
>> 2.7.4
>>
>
next prev parent reply other threads:[~2020-02-20 16:14 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-19 19:08 [PATCH 0/5] Support metric group constraint kan.liang
2020-02-19 19:08 ` [PATCH 1/5] perf jevents: Support metric constraint kan.liang
2020-02-19 19:08 ` [PATCH 2/5] perf metricgroup: Factor out metricgroup__add_metric_weak_group() kan.liang
2020-02-19 19:08 ` [PATCH 3/5] perf util: Factor out sysctl__nmi_watchdog_enabled() kan.liang
2020-02-19 19:08 ` [PATCH 4/5] perf metricgroup: Support metric constraint kan.liang
2020-02-20 11:35 ` Jiri Olsa
2020-02-20 16:14 ` Liang, Kan [this message]
2020-02-21 13:09 ` Jiri Olsa
2020-02-21 14:30 ` Liang, Kan
2020-02-21 14:48 ` Jiri Olsa
2020-02-21 15:42 ` Liang, Kan
2020-02-19 19:08 ` [PATCH 5/5] perf vendor events: Add NO_NMI_WATCHDOG " kan.liang
2020-02-20 11:39 ` [PATCH 0/5] Support metric group constraint Jiri Olsa
2020-02-20 16:03 ` Liang, Kan
2020-02-20 16:43 ` Andi Kleen
2020-02-20 19:25 ` Liang, Kan
2020-02-21 13:18 ` Jiri Olsa
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=fea147db-2af3-e9ec-fb23-f9db8cf1c77a@linux.intel.com \
--to=kan.liang@linux.intel.com \
--cc=acme@kernel.org \
--cc=ak@linux.intel.com \
--cc=jolsa@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=mingo@redhat.com \
--cc=namhyung@kernel.org \
--cc=peterz@infradead.org \
--cc=ravi.bangoria@linux.ibm.com \
--cc=yao.jin@linux.intel.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
Powered by JetHome