Intel-XE Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "Dixit, Ashutosh" <ashutosh.dixit@intel.com>
To: Vinay Belgaumkar <vinay.belgaumkar@intel.com>
Cc: intel-xe@lists.freedesktop.org,
	Riana Tauro <riana.tauro@intel.com>,
	Lucas De Marchi <lucas.demarchi@intel.com>,
	Rodrigo Vivi <rodrigo.vivi@intel.com>
Subject: Re: [PATCH v4] drm/xe/pmu: Add GT frequency events
Date: Mon, 24 Mar 2025 17:18:58 -0700	[thread overview]
Message-ID: <87jz8e9d3h.wl-ashutosh.dixit@intel.com> (raw)
In-Reply-To: <20250324232402.46481-1-vinay.belgaumkar@intel.com>

On Mon, 24 Mar 2025 16:24:02 -0700, Vinay Belgaumkar wrote:
>
> @@ -266,11 +274,24 @@ static u64 __xe_pmu_event_read(struct perf_event *event)
>	case XE_PMU_EVENT_ENGINE_ACTIVE_TICKS:
>	case XE_PMU_EVENT_ENGINE_TOTAL_TICKS:
>		return read_engine_events(gt, event);
> +	case XE_PMU_EVENT_GT_ACTUAL_FREQUENCY:
> +		return xe_guc_pc_get_act_freq(&gt->uc.guc.pc);
> +	case XE_PMU_EVENT_GT_REQUESTED_FREQUENCY:
> +		if (!xe_guc_pc_get_cur_freq(&gt->uc.guc.pc, &cur_gt_freq))

This is unconditionally taking the forcewake and waking the card up just to
get the sample. Do we really want to do that?

So if we don't do that, both the actual and requested freq will be 0 if gt
is in C6.

> +			return cur_gt_freq;

  reply	other threads:[~2025-03-25  0:19 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-03-24 23:24 [PATCH v4] drm/xe/pmu: Add GT frequency events Vinay Belgaumkar
2025-03-25  0:18 ` Dixit, Ashutosh [this message]
2025-03-25  2:37   ` Belgaumkar, Vinay
2025-03-25 17:15     ` Dixit, Ashutosh
2025-03-25 20:33       ` Belgaumkar, Vinay
2025-03-25 21:53         ` Dixit, Ashutosh
2025-03-25 22:01           ` Belgaumkar, Vinay
2025-03-25 22:45             ` Dixit, Ashutosh
2025-03-25 23:02               ` Belgaumkar, Vinay
2025-03-26  4:09               ` Lucas De Marchi
2025-03-26  4:14                 ` Lucas De Marchi
2025-03-26 15:02                   ` Dixit, Ashutosh
2025-03-26 15:34                     ` Lucas De Marchi
2025-03-26 22:02                   ` Belgaumkar, Vinay
2025-03-26 22:38                     ` Dixit, Ashutosh
2025-03-25  0:29 ` ✓ CI.Patch_applied: success for drm/xe/pmu: Add GT frequency events (rev6) Patchwork
2025-03-25  0:29 ` ✗ CI.checkpatch: warning " Patchwork
2025-03-25  0:30 ` ✓ CI.KUnit: success " Patchwork
2025-03-25  0:47 ` ✓ CI.Build: " Patchwork
2025-03-25  0:49 ` ✓ CI.Hooks: " Patchwork
2025-03-25  0:50 ` ✓ CI.checksparse: " Patchwork
2025-03-25  1:11 ` ✓ Xe.CI.BAT: " Patchwork
2025-03-25  6:04 ` ✗ 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=87jz8e9d3h.wl-ashutosh.dixit@intel.com \
    --to=ashutosh.dixit@intel.com \
    --cc=intel-xe@lists.freedesktop.org \
    --cc=lucas.demarchi@intel.com \
    --cc=riana.tauro@intel.com \
    --cc=rodrigo.vivi@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