From: Peter Zijlstra <peterz@infradead.org>
To: Ravi Bangoria <ravi.bangoria@amd.com>
Cc: acme@kernel.org, mingo@redhat.com, mark.rutland@arm.com,
jolsa@kernel.org, namhyung@kernel.org, tglx@linutronix.de,
bp@alien8.de, irogers@google.com, yao.jin@linux.intel.com,
james.clark@arm.com, leo.yan@linaro.org,
kan.liang@linux.intel.com, ak@linux.intel.com,
eranian@google.com, like.xu.linux@gmail.com, x86@kernel.org,
linux-perf-users@vger.kernel.org, linux-kernel@vger.kernel.org,
sandipan.das@amd.com, ananth.narayan@amd.com,
kim.phillips@amd.com, rrichter@amd.com, santosh.shukla@amd.com
Subject: Re: [PATCH 1/6] perf/amd/ibs: Add support for L3 miss filtering
Date: Tue, 26 Apr 2022 12:07:07 +0200 [thread overview]
Message-ID: <20220426100707.GP2731@worktop.programming.kicks-ass.net> (raw)
In-Reply-To: <20220425044323.2830-2-ravi.bangoria@amd.com>
On Mon, Apr 25, 2022 at 10:13:18AM +0530, Ravi Bangoria wrote:
> IBS L3 miss filtering works by tagging an instruction on IBS counter
> overflow and generating an NMI if the tagged instruction causes an L3
> miss. Samples without an L3 miss are discarded and counter is reset
> with random value (between 1-15 for fetch pmu and 1-127 for op pmu).
> This helps in reducing sampling overhead when user is interested only
> in such samples. One of the use case of such filtered samples is to
> feed data to page-migration daemon in tiered memory systems.
>
> Add support for L3 miss filtering in IBS driver via new pmu attribute
> "l3missonly". Example usage:
>
> # perf record -a -e ibs_op/l3missonly=1/ --raw-samples sleep 5
>
> Signed-off-by: Ravi Bangoria <ravi.bangoria@amd.com>
> ---
> arch/x86/events/amd/ibs.c | 42 ++++++++++++++++++++++---------
> arch/x86/include/asm/perf_event.h | 3 +++
> 2 files changed, 33 insertions(+), 12 deletions(-)
>
> diff --git a/arch/x86/events/amd/ibs.c b/arch/x86/events/amd/ibs.c
> index 9739019d4b67..a5303d62060c 100644
> --- a/arch/x86/events/amd/ibs.c
> +++ b/arch/x86/events/amd/ibs.c
> @@ -520,16 +520,12 @@ static void perf_ibs_read(struct perf_event *event) { }
>
> PMU_FORMAT_ATTR(rand_en, "config:57");
> PMU_FORMAT_ATTR(cnt_ctl, "config:19");
> +PMU_EVENT_ATTR_STRING(l3missonly, fetch_l3missonly, "config:59");
> +PMU_EVENT_ATTR_STRING(l3missonly, op_l3missonly, "config:16");
>
> -static struct attribute *ibs_fetch_format_attrs[] = {
> - &format_attr_rand_en.attr,
> - NULL,
> -};
> -
> -static struct attribute *ibs_op_format_attrs[] = {
> - NULL, /* &format_attr_cnt_ctl.attr if IBS_CAPS_OPCNT */
> - NULL,
> -};
> +/* size = nr attrs plus NULL at the end */
> +static struct attribute *ibs_fetch_format_attrs[3];
> +static struct attribute *ibs_op_format_attrs[3];
>
> static struct perf_ibs perf_ibs_fetch = {
> .pmu = {
> @@ -759,9 +755,9 @@ static __init int perf_ibs_pmu_init(struct perf_ibs *perf_ibs, char *name)
> return ret;
> }
>
> -static __init void perf_event_ibs_init(void)
> +static __init void perf_ibs_fetch_prepare(void)
> {
> - struct attribute **attr = ibs_op_format_attrs;
> + struct attribute **format_attrs = perf_ibs_fetch.format_attrs;
>
> /*
> * Some chips fail to reset the fetch count when it is written; instead
> @@ -773,11 +769,22 @@ static __init void perf_event_ibs_init(void)
> if (boot_cpu_data.x86 == 0x19 && boot_cpu_data.x86_model < 0x10)
> perf_ibs_fetch.fetch_ignore_if_zero_rip = 1;
>
> + *format_attrs++ = &format_attr_rand_en.attr;
> + if (ibs_caps & IBS_CAPS_ZEN4IBSEXTENSIONS) {
> + perf_ibs_fetch.config_mask |= IBS_FETCH_L3MISSONLY;
> + *format_attrs++ = &fetch_l3missonly.attr.attr;
> + }
> +
> perf_ibs_pmu_init(&perf_ibs_fetch, "ibs_fetch");
> +}
> +
> +static __init void perf_ibs_op_prepare(void)
> +{
> + struct attribute **format_attrs = perf_ibs_op.format_attrs;
>
> if (ibs_caps & IBS_CAPS_OPCNT) {
> perf_ibs_op.config_mask |= IBS_OP_CNT_CTL;
> - *attr++ = &format_attr_cnt_ctl.attr;
> + *format_attrs++ = &format_attr_cnt_ctl.attr;
> }
>
> if (ibs_caps & IBS_CAPS_OPCNTEXT) {
> @@ -786,7 +793,18 @@ static __init void perf_event_ibs_init(void)
> perf_ibs_op.cnt_mask |= IBS_OP_MAX_CNT_EXT_MASK;
> }
>
> + if (ibs_caps & IBS_CAPS_ZEN4IBSEXTENSIONS) {
> + perf_ibs_op.config_mask |= IBS_OP_L3MISSONLY;
> + *format_attrs++ = &op_l3missonly.attr.attr;
> + }
> +
> perf_ibs_pmu_init(&perf_ibs_op, "ibs_op");
> +}
Right, so Greg told us to stop doing silly things like this and use
.is_visible, also see commits like:
b7c9b3927337 ("perf/x86/intel: Use ->is_visible callback for default group")
There's quite a bit of that in the intel driver and some in the x86
core code too. Please have a look.
next prev parent reply other threads:[~2022-04-26 10:29 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-25 4:43 [PATCH 0/6] perf/amd: Zen4 IBS extensions support Ravi Bangoria
2022-04-25 4:43 ` [PATCH 1/6] perf/amd/ibs: Add support for L3 miss filtering Ravi Bangoria
2022-04-26 9:18 ` Robert Richter
2022-04-26 11:25 ` Ravi Bangoria
2022-04-26 10:07 ` Peter Zijlstra [this message]
2022-04-26 11:30 ` Ravi Bangoria
2022-04-25 4:43 ` [PATCH 2/6] perf/amd/ibs: Advertise zen4_ibs_extensions as pmu capability attribute Ravi Bangoria
2022-04-26 9:57 ` Robert Richter
2022-04-26 11:40 ` Ravi Bangoria
2022-04-25 4:43 ` [PATCH 3/6] perf/tool/amd/ibs: Warn about sampling period skew Ravi Bangoria
2022-04-26 10:09 ` Robert Richter
2022-04-26 11:43 ` Ravi Bangoria
2022-04-25 4:43 ` [PATCH 4/6] perf/tool: Parse non-cpu pmu capabilities Ravi Bangoria
2022-04-26 10:37 ` Robert Richter
2022-04-26 11:53 ` Ravi Bangoria
2022-04-25 4:43 ` [PATCH 5/6] perf/tool/amd/ibs: Support new IBS bits in raw trace dump Ravi Bangoria
2022-04-26 11:27 ` Robert Richter
2022-04-26 13:34 ` Ravi Bangoria
2022-04-25 4:43 ` [PATCH 6/6] perf/tool/amd/ibs: Fix comment Ravi Bangoria
2022-04-26 11:27 ` Robert Richter
2022-04-25 20:32 ` [PATCH 0/6] perf/amd: Zen4 IBS extensions support Peter Zijlstra
2022-04-26 7:00 ` Ravi Bangoria
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=20220426100707.GP2731@worktop.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=acme@kernel.org \
--cc=ak@linux.intel.com \
--cc=ananth.narayan@amd.com \
--cc=bp@alien8.de \
--cc=eranian@google.com \
--cc=irogers@google.com \
--cc=james.clark@arm.com \
--cc=jolsa@kernel.org \
--cc=kan.liang@linux.intel.com \
--cc=kim.phillips@amd.com \
--cc=leo.yan@linaro.org \
--cc=like.xu.linux@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=mingo@redhat.com \
--cc=namhyung@kernel.org \
--cc=ravi.bangoria@amd.com \
--cc=rrichter@amd.com \
--cc=sandipan.das@amd.com \
--cc=santosh.shukla@amd.com \
--cc=tglx@linutronix.de \
--cc=x86@kernel.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.