From: "Belgaumkar, Vinay" <vinay.belgaumkar@intel.com>
To: Ashutosh Dixit <ashutosh.dixit@intel.com>,
<intel-gfx@lists.freedesktop.org>
Cc: dri-devel@lists.freedesktop.org, Rodrigo Vivi <rodrigo.vivi@intel.com>
Subject: Re: [Intel-gfx] [PATCH 3/3] drm/i915/pmu: Use common freq functions with sysfs
Date: Tue, 7 Mar 2023 22:12:49 -0800 [thread overview]
Message-ID: <8b4e02e6-35a0-5262-5f85-5671f4d287b4@intel.com> (raw)
In-Reply-To: <20230308053321.939906-4-ashutosh.dixit@intel.com>
On 3/7/2023 9:33 PM, Ashutosh Dixit wrote:
> Using common freq functions with sysfs in PMU (but without taking
> forcewake) solves the following issues (a) missing support for MTL (b)
For the requested_freq, we read it only if actual_freq is zero below
(meaning, GT is in C6). So then what is the point of reading it without
a force wake? It will also be zero, correct?
Thanks,
Vinay.
> missing support for older generation (prior to Gen6) (c) missing support
> for slpc when freq sampling has to fall back to requested freq. It also
> makes the PMU code future proof where sometimes code has been updated for
> sysfs and PMU has been missed.
>
> Signed-off-by: Ashutosh Dixit <ashutosh.dixit@intel.com>
> ---
> drivers/gpu/drm/i915/gt/intel_rps.c | 10 ----------
> drivers/gpu/drm/i915/gt/intel_rps.h | 1 -
> drivers/gpu/drm/i915/i915_pmu.c | 10 ++++------
> 3 files changed, 4 insertions(+), 17 deletions(-)
>
> diff --git a/drivers/gpu/drm/i915/gt/intel_rps.c b/drivers/gpu/drm/i915/gt/intel_rps.c
> index 49df31927c0e..b03bfbe7ee23 100644
> --- a/drivers/gpu/drm/i915/gt/intel_rps.c
> +++ b/drivers/gpu/drm/i915/gt/intel_rps.c
> @@ -2046,16 +2046,6 @@ void intel_rps_sanitize(struct intel_rps *rps)
> rps_disable_interrupts(rps);
> }
>
> -u32 intel_rps_read_rpstat_fw(struct intel_rps *rps)
> -{
> - struct drm_i915_private *i915 = rps_to_i915(rps);
> - i915_reg_t rpstat;
> -
> - rpstat = (GRAPHICS_VER(i915) >= 12) ? GEN12_RPSTAT1 : GEN6_RPSTAT1;
> -
> - return intel_uncore_read_fw(rps_to_gt(rps)->uncore, rpstat);
> -}
> -
> u32 intel_rps_read_rpstat(struct intel_rps *rps)
> {
> struct drm_i915_private *i915 = rps_to_i915(rps);
> diff --git a/drivers/gpu/drm/i915/gt/intel_rps.h b/drivers/gpu/drm/i915/gt/intel_rps.h
> index a990f985ab23..60ae27679011 100644
> --- a/drivers/gpu/drm/i915/gt/intel_rps.h
> +++ b/drivers/gpu/drm/i915/gt/intel_rps.h
> @@ -53,7 +53,6 @@ u32 intel_rps_get_rp1_frequency(struct intel_rps *rps);
> u32 intel_rps_get_rpn_frequency(struct intel_rps *rps);
> u32 intel_rps_read_punit_req_frequency(struct intel_rps *rps);
> u32 intel_rps_read_rpstat(struct intel_rps *rps);
> -u32 intel_rps_read_rpstat_fw(struct intel_rps *rps);
> void gen6_rps_get_freq_caps(struct intel_rps *rps, struct intel_rps_freq_caps *caps);
> void intel_rps_raise_unslice(struct intel_rps *rps);
> void intel_rps_lower_unslice(struct intel_rps *rps);
> diff --git a/drivers/gpu/drm/i915/i915_pmu.c b/drivers/gpu/drm/i915/i915_pmu.c
> index a76c5ce9513d..1a4c9fed257c 100644
> --- a/drivers/gpu/drm/i915/i915_pmu.c
> +++ b/drivers/gpu/drm/i915/i915_pmu.c
> @@ -392,14 +392,12 @@ frequency_sample(struct intel_gt *gt, unsigned int period_ns)
> * case we assume the system is running at the intended
> * frequency. Fortunately, the read should rarely fail!
> */
> - val = intel_rps_read_rpstat_fw(rps);
> - if (val)
> - val = intel_rps_get_cagf(rps, val);
> - else
> - val = rps->cur_freq;
> + val = intel_rps_read_actual_frequency_fw(rps);
> + if (!val)
> + val = intel_rps_get_requested_frequency_fw(rps),
>
> add_sample_mult(&pmu->sample[__I915_SAMPLE_FREQ_ACT],
> - intel_gpu_freq(rps, val), period_ns / 1000);
> + val, period_ns / 1000);
> }
>
> if (pmu->enable & config_mask(I915_PMU_REQUESTED_FREQUENCY)) {
next prev parent reply other threads:[~2023-03-08 6:12 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-08 5:33 [Intel-gfx] [PATCH 0/3] drm/i915/pmu: Use common freq functions with sysfs Ashutosh Dixit
2023-03-08 5:33 ` [Intel-gfx] [PATCH 1/3] drm/i915/rps: Expose read_actual_frequency_fw for PMU Ashutosh Dixit
2023-03-08 5:33 ` [Intel-gfx] [PATCH 2/3] drm/i915/rps: Expose get_requested_frequency_fw " Ashutosh Dixit
2023-03-08 5:33 ` [Intel-gfx] [PATCH 3/3] drm/i915/pmu: Use common freq functions with sysfs Ashutosh Dixit
2023-03-08 6:12 ` Belgaumkar, Vinay [this message]
2023-03-09 3:53 ` Dixit, Ashutosh
2023-03-08 6:13 ` [Intel-gfx] ✓ Fi.CI.BAT: success for " Patchwork
2023-03-09 18:08 ` [Intel-gfx] ✓ Fi.CI.IGT: " 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=8b4e02e6-35a0-5262-5f85-5671f4d287b4@intel.com \
--to=vinay.belgaumkar@intel.com \
--cc=ashutosh.dixit@intel.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=rodrigo.vivi@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