From: Jiri Olsa <jolsa@redhat.com>
To: Jin Yao <yao.jin@linux.intel.com>
Cc: acme@kernel.org, jolsa@kernel.org, peterz@infradead.org,
mingo@redhat.com, alexander.shishkin@linux.intel.com,
Linux-kernel@vger.kernel.org, ak@linux.intel.com,
kan.liang@intel.com, yao.jin@intel.com
Subject: Re: [PATCH v3] perf pmu: Validate raw event with sysfs exported format bits
Date: Mon, 8 Mar 2021 11:35:00 +0100 [thread overview]
Message-ID: <YEX91MTGMU41zeuF@krava> (raw)
In-Reply-To: <20210308031506.23019-1-yao.jin@linux.intel.com>
On Mon, Mar 08, 2021 at 11:15:06AM +0800, Jin Yao wrote:
SNIP
> diff --git a/tools/perf/util/pmu.c b/tools/perf/util/pmu.c
> index 44ef28302fc7..03ab1e6d0418 100644
> --- a/tools/perf/util/pmu.c
> +++ b/tools/perf/util/pmu.c
> @@ -1812,3 +1812,39 @@ int perf_pmu__caps_parse(struct perf_pmu *pmu)
>
> return nr_caps;
> }
> +
> +void perf_pmu__warn_invalid_config(struct perf_pmu *pmu, __u64 config,
> + char *name)
> +{
> + struct perf_pmu_format *format;
> + __u64 masks = 0, bits;
> + char buf[100];
> + unsigned int i;
> +
> + list_for_each_entry(format, &pmu->format, list) {
> + /*
> + * Skip extra configs such as config1/config2.
> + */
> + if (format->value > 0)
> + continue;
sorry I did not notice before, but could you please use more direct
approach like:
if (format->value == PERF_PMU_FORMAT_VALUE_CONFIG) {
break;
}
this will be more obvious, also no need for the comment.. I spent some
time looking what's the value for ;-)
thanks,
jirka
> +
> + for_each_set_bit(i, format->bits, PERF_PMU_FORMAT_BITS)
> + masks |= 1ULL << i;
> + }
> +
> + /*
> + * Kernel doesn't export any valid format bits.
> + */
> + if (masks == 0)
> + return;
> +
> + bits = config & ~masks;
> + if (bits == 0)
> + return;
> +
> + bitmap_scnprintf((unsigned long *)&bits, sizeof(bits) * 8, buf, sizeof(buf));
> +
> + pr_warning("WARNING: event '%s' not valid (bits %s of config "
> + "'%llx' not supported by kernel)!\n",
> + name ?: "N/A", buf, config);
> +}
> diff --git a/tools/perf/util/pmu.h b/tools/perf/util/pmu.h
> index 8164388478c6..160b0f561771 100644
> --- a/tools/perf/util/pmu.h
> +++ b/tools/perf/util/pmu.h
> @@ -123,4 +123,7 @@ int perf_pmu__convert_scale(const char *scale, char **end, double *sval);
>
> int perf_pmu__caps_parse(struct perf_pmu *pmu);
>
> +void perf_pmu__warn_invalid_config(struct perf_pmu *pmu, __u64 config,
> + char *name);
> +
> #endif /* __PMU_H */
> --
> 2.17.1
>
next prev parent reply other threads:[~2021-03-08 10:35 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-08 3:15 [PATCH v3] perf pmu: Validate raw event with sysfs exported format bits Jin Yao
2021-03-08 10:35 ` Jiri Olsa [this message]
2021-03-08 12:57 ` Jin, Yao
2021-03-08 13:14 ` Jiri Olsa
2021-03-09 3:00 ` Jin, Yao
2021-03-09 21:44 ` 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=YEX91MTGMU41zeuF@krava \
--to=jolsa@redhat.com \
--cc=Linux-kernel@vger.kernel.org \
--cc=acme@kernel.org \
--cc=ak@linux.intel.com \
--cc=alexander.shishkin@linux.intel.com \
--cc=jolsa@kernel.org \
--cc=kan.liang@intel.com \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=yao.jin@intel.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