From: "Zhang, Rui" <rui.zhang@intel.com>
To: "alexander.shishkin@linux.intel.com"
<alexander.shishkin@linux.intel.com>,
"dave.hansen@linux.intel.com" <dave.hansen@linux.intel.com>,
"Hunter, Adrian" <adrian.hunter@intel.com>,
"mingo@redhat.com" <mingo@redhat.com>,
"irogers@google.com" <irogers@google.com>,
"tglx@linutronix.de" <tglx@linutronix.de>,
"gustavoars@kernel.org" <gustavoars@kernel.org>,
"kan.liang@linux.intel.com" <kan.liang@linux.intel.com>,
"kees@kernel.org" <kees@kernel.org>,
"mark.rutland@arm.com" <mark.rutland@arm.com>,
"peterz@infradead.org" <peterz@infradead.org>,
"Dhananjay.Ugwekar@amd.com" <Dhananjay.Ugwekar@amd.com>,
"bp@alien8.de" <bp@alien8.de>,
"acme@kernel.org" <acme@kernel.org>,
"jolsa@kernel.org" <jolsa@kernel.org>,
"x86@kernel.org" <x86@kernel.org>,
"namhyung@kernel.org" <namhyung@kernel.org>
Cc: "ravi.bangoria@amd.com" <ravi.bangoria@amd.com>,
"kprateek.nayak@amd.com" <kprateek.nayak@amd.com>,
"gautham.shenoy@amd.com" <gautham.shenoy@amd.com>,
"linux-perf-users@vger.kernel.org"
<linux-perf-users@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-hardening@vger.kernel.org"
<linux-hardening@vger.kernel.org>,
"sandipan.das@amd.com" <sandipan.das@amd.com>,
"ananth.narayan@amd.com" <ananth.narayan@amd.com>,
"linux-pm@vger.kernel.org" <linux-pm@vger.kernel.org>
Subject: Re: [PATCH 6/6] perf/x86/rapl: Add per-core energy counter support for AMD CPUs
Date: Tue, 11 Jun 2024 08:30:03 +0000 [thread overview]
Message-ID: <d7f1d65c7e8872dee2a97ee47be191496d048d1d.camel@intel.com> (raw)
In-Reply-To: <20240610100751.4855-7-Dhananjay.Ugwekar@amd.com>
> @@ -345,9 +353,14 @@ static int rapl_pmu_event_init(struct perf_event
> *event)
> u64 cfg = event->attr.config & RAPL_EVENT_MASK;
> int bit, ret = 0;
> struct rapl_pmu *rapl_pmu;
> + struct rapl_pmus *curr_rapl_pmus;
>
> /* only look at RAPL events */
> - if (event->attr.type != rapl_pmus->pmu.type)
> + if (event->attr.type == rapl_pmus->pmu.type)
> + curr_rapl_pmus = rapl_pmus;
> + else if (rapl_pmus_per_core && event->attr.type ==
> rapl_pmus_per_core->pmu.type)
> + curr_rapl_pmus = rapl_pmus_per_core;
> + else
> return -ENOENT;
can we use container_of(event->pmu, struct rapl_pmus, pmu)?
>
> /* check only supported bits are set */
> @@ -374,9 +387,14 @@ static int rapl_pmu_event_init(struct perf_event
> *event)
> return -EINVAL;
>
> /* must be done before validate_group */
> - rapl_pmu = cpu_to_rapl_pmu(event->cpu);
> + if (curr_rapl_pmus == rapl_pmus_per_core)
> + rapl_pmu = curr_rapl_pmus-
> >rapl_pmu[topology_core_id(event->cpu)];
> + else
> + rapl_pmu = curr_rapl_pmus-
> >rapl_pmu[get_rapl_pmu_idx(event->cpu)];
> +
> if (!rapl_pmu)
> return -EINVAL;
Current code has PERF_EV_CAP_READ_ACTIVE_PKG flag set.
Can you help me understand why it does not affect the new per-core pmu?
> +
> event->cpu = rapl_pmu->cpu;
> event->pmu_private = rapl_pmu;
> event->hw.event_base = rapl_msrs[bit].msr;
> @@ -408,17 +426,38 @@ static struct attribute_group
> rapl_pmu_attr_group = {
> .attrs = rapl_pmu_attrs,
> };
>
> +static ssize_t rapl_get_attr_per_core_cpumask(struct device *dev,
> + struct device_attribute
> *attr, char *buf)
> +{
> + return cpumap_print_to_pagebuf(true, buf,
> &rapl_pmus_per_core->cpumask);
> +}
> +
> +static struct device_attribute dev_attr_per_core_cpumask =
> __ATTR(cpumask, 0444,
> +
> rapl_get_attr_per_core_cpumask,
> +
> NULL);
DEVICE_ATTR
> +
> +static struct attribute *rapl_pmu_per_core_attrs[] = {
> + &dev_attr_per_core_cpumask.attr,
> + NULL,
> +};
> +
> +static struct attribute_group rapl_pmu_per_core_attr_group = {
> + .attrs = rapl_pmu_per_core_attrs,
> +};
> +
> RAPL_EVENT_ATTR_STR(energy-cores, rapl_cores, "event=0x01");
> RAPL_EVENT_ATTR_STR(energy-pkg , rapl_pkg, "event=0x02");
> RAPL_EVENT_ATTR_STR(energy-ram , rapl_ram, "event=0x03");
> RAPL_EVENT_ATTR_STR(energy-gpu , rapl_gpu, "event=0x04");
> RAPL_EVENT_ATTR_STR(energy-psys, rapl_psys, "event=0x05");
> +RAPL_EVENT_ATTR_STR(energy-per-core, rapl_per_core, "event=0x06");
energy-per-core is for a separate pmu, so the event id does not need to
be 6. The same applies to PERF_RAPL_PERCORE.
>
> static struct rapl_model model_amd_hygon = {
> - .events = BIT(PERF_RAPL_PKG),
> + .events = BIT(PERF_RAPL_PKG) |
> + BIT(PERF_RAPL_PERCORE),
> .msr_power_unit = MSR_AMD_RAPL_POWER_UNIT,
> .rapl_msrs = amd_rapl_msrs,
> + .per_core = true,
> };
can we use bit PERF_RAPL_PERCORE to check per_core pmu suppot?
Just FYI, arch/x86/events/intel/cstate.c handles package/module/core
scope cstate pmus. It uses a different approach in the probing part,
which IMO is clearer.
thanks,
rui
next prev parent reply other threads:[~2024-06-11 8:30 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-10 10:07 [PATCH 0/6] Add per-core RAPL energy counter support for AMD CPUs Dhananjay Ugwekar
2024-06-10 10:07 ` [PATCH 1/6] perf/x86/rapl: Fix the energy-pkg event " Dhananjay Ugwekar
2024-06-11 5:35 ` Zhang, Rui
2024-06-11 14:17 ` Dhananjay Ugwekar
2024-06-10 10:07 ` [PATCH 2/6] perf/x86/rapl: Rename rapl_pmu variables Dhananjay Ugwekar
2024-06-11 5:43 ` Zhang, Rui
2024-06-11 8:33 ` Dhananjay Ugwekar
2024-06-10 10:07 ` [PATCH 3/6] perf/x86/rapl: Make rapl_model struct global Dhananjay Ugwekar
2024-06-10 10:07 ` [PATCH 4/6] perf/x86/rapl: Move cpumask variable to rapl_pmus struct Dhananjay Ugwekar
2024-06-10 10:07 ` [PATCH 5/6] perf/x86/rapl: Add wrapper for online/offline functions Dhananjay Ugwekar
2024-06-10 10:07 ` [PATCH 6/6] perf/x86/rapl: Add per-core energy counter support for AMD CPUs Dhananjay Ugwekar
2024-06-11 8:30 ` Zhang, Rui [this message]
2024-06-13 6:39 ` Dhananjay Ugwekar
2024-06-10 14:28 ` [PATCH 0/6] Add per-core RAPL " Oleksandr Natalenko
2024-06-10 15:17 ` Dhananjay Ugwekar
2024-06-10 18:08 ` Oleksandr Natalenko
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=d7f1d65c7e8872dee2a97ee47be191496d048d1d.camel@intel.com \
--to=rui.zhang@intel.com \
--cc=Dhananjay.Ugwekar@amd.com \
--cc=acme@kernel.org \
--cc=adrian.hunter@intel.com \
--cc=alexander.shishkin@linux.intel.com \
--cc=ananth.narayan@amd.com \
--cc=bp@alien8.de \
--cc=dave.hansen@linux.intel.com \
--cc=gautham.shenoy@amd.com \
--cc=gustavoars@kernel.org \
--cc=irogers@google.com \
--cc=jolsa@kernel.org \
--cc=kan.liang@linux.intel.com \
--cc=kees@kernel.org \
--cc=kprateek.nayak@amd.com \
--cc=linux-hardening@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=mingo@redhat.com \
--cc=namhyung@kernel.org \
--cc=peterz@infradead.org \
--cc=ravi.bangoria@amd.com \
--cc=sandipan.das@amd.com \
--cc=tglx@linutronix.de \
--cc=x86@kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).