From: Rodrigo Vivi <rodrigo.vivi@intel.com>
To: Lucas De Marchi <lucas.demarchi@intel.com>
Cc: <intel-xe@lists.freedesktop.org>,
Vinay Belgaumkar <vinay.belgaumkar@intel.com>,
Riana Tauro <riana.tauro@intel.com>,
"Peter Zijlstra" <peterz@infradead.org>,
<linux-perf-users@vger.kernel.org>
Subject: Re: [PATCH v15 3/6] drm/xe/pmu: Extract xe_pmu_event_update()
Date: Thu, 23 Jan 2025 05:20:09 -0500 [thread overview]
Message-ID: <Z5IX2Rixtx6csrKO@intel.com> (raw)
In-Reply-To: <20250123041923.1892837-4-lucas.demarchi@intel.com>
On Wed, Jan 22, 2025 at 08:19:20PM -0800, Lucas De Marchi wrote:
> Like other pmu drivers, keep the update separate from the read so it can
> be called from other methods (like stop()) without side effects.
>
> Signed-off-by: Lucas De Marchi <lucas.demarchi@intel.com>
> ---
> drivers/gpu/drm/xe/xe_pmu.c | 24 +++++++++++++++---------
> 1 file changed, 15 insertions(+), 9 deletions(-)
>
> diff --git a/drivers/gpu/drm/xe/xe_pmu.c b/drivers/gpu/drm/xe/xe_pmu.c
> index df93ba96bdc1e..33598272db6aa 100644
> --- a/drivers/gpu/drm/xe/xe_pmu.c
> +++ b/drivers/gpu/drm/xe/xe_pmu.c
> @@ -117,18 +117,11 @@ static u64 __xe_pmu_event_read(struct perf_event *event)
> return val;
> }
>
> -static void xe_pmu_event_read(struct perf_event *event)
> +static void xe_pmu_event_update(struct perf_event *event)
> {
> - struct xe_device *xe = container_of(event->pmu, typeof(*xe), pmu.base);
> struct hw_perf_event *hwc = &event->hw;
> - struct xe_pmu *pmu = &xe->pmu;
> u64 prev, new;
>
> - if (!pmu->registered) {
> - event->hw.state = PERF_HES_STOPPED;
> - return;
> - }
> -
> prev = local64_read(&hwc->prev_count);
> do {
> new = __xe_pmu_event_read(event);
I really have the feeling that the names are inverted, and that this
function should be the one actually called read, but I double
checked and everybody else is doing the same, so I guess I just need
more coffee...
Reviewed-by: Rodrigo Vivi <rodrigo.vivi@intel.com>
> @@ -137,6 +130,19 @@ static void xe_pmu_event_read(struct perf_event *event)
> local64_add(new - prev, &event->count);
> }
>
> +static void xe_pmu_event_read(struct perf_event *event)
> +{
> + struct xe_device *xe = container_of(event->pmu, typeof(*xe), pmu.base);
> + struct xe_pmu *pmu = &xe->pmu;
> +
> + if (!pmu->registered) {
> + event->hw.state = PERF_HES_STOPPED;
> + return;
> + }
> +
> + xe_pmu_event_update(event);
> +}
> +
> static void xe_pmu_enable(struct perf_event *event)
> {
> /*
> @@ -166,7 +172,7 @@ static void xe_pmu_event_stop(struct perf_event *event, int flags)
>
> if (pmu->registered)
> if (flags & PERF_EF_UPDATE)
> - xe_pmu_event_read(event);
> + xe_pmu_event_update(event);
>
> event->hw.state = PERF_HES_STOPPED;
> }
> --
> 2.48.0
>
next prev parent reply other threads:[~2025-01-23 10:20 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-23 4:19 [PATCH v15 0/6] drm/xe/pmu: PMU interface for Xe Lucas De Marchi
2025-01-23 4:19 ` [PATCH v15 1/6] drm/xe/pmu: Enable PMU interface Lucas De Marchi
2025-01-23 4:19 ` [PATCH v15 2/6] drm/xe/pmu: Assert max gt Lucas De Marchi
2025-01-23 4:19 ` [PATCH v15 3/6] drm/xe/pmu: Extract xe_pmu_event_update() Lucas De Marchi
2025-01-23 10:20 ` Rodrigo Vivi [this message]
2025-01-23 14:59 ` Lucas De Marchi
2025-01-23 15:24 ` Rodrigo Vivi
2025-01-23 4:19 ` [PATCH v15 4/6] drm/xe/pmu: Add attribute skeleton Lucas De Marchi
2025-01-23 10:13 ` Rodrigo Vivi
2025-01-23 13:54 ` Riana Tauro
2025-01-23 14:48 ` Lucas De Marchi
2025-01-23 15:02 ` Riana Tauro
2025-01-23 16:36 ` Lucas De Marchi
2025-01-23 4:19 ` [PATCH v15 5/6] drm/xe/pmu: Get/put runtime pm on event init Lucas De Marchi
2025-01-23 4:19 ` [PATCH v15 6/6] drm/xe/pmu: Add GT C6 events Lucas De Marchi
2025-01-23 4:29 ` ✓ CI.Patch_applied: success for drm/xe/pmu: PMU interface for Xe (rev15) Patchwork
2025-01-23 4:29 ` ✗ CI.checkpatch: warning " Patchwork
2025-01-23 4:30 ` ✓ CI.KUnit: success " Patchwork
2025-01-23 4:47 ` ✓ CI.Build: " Patchwork
2025-01-23 4:49 ` ✓ CI.Hooks: " Patchwork
2025-01-23 4:51 ` ✓ CI.checksparse: " Patchwork
2025-01-23 5:17 ` ✓ Xe.CI.BAT: " Patchwork
2025-01-23 15:16 ` ✗ Xe.CI.Full: failure " Patchwork
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=Z5IX2Rixtx6csrKO@intel.com \
--to=rodrigo.vivi@intel.com \
--cc=intel-xe@lists.freedesktop.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=lucas.demarchi@intel.com \
--cc=peterz@infradead.org \
--cc=riana.tauro@intel.com \
--cc=vinay.belgaumkar@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;
as well as URLs for NNTP newsgroup(s).