Intel-GFX Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "Nilawar, Badal" <badal.nilawar@intel.com>
To: Ashutosh Dixit <ashutosh.dixit@intel.com>,
	<intel-gfx@lists.freedesktop.org>
Subject: Re: [Intel-gfx] [PATCH] drm/i915/pmu: Drop redundant IS_VALLEYVIEW check in __get_rc6()
Date: Mon, 14 Mar 2022 10:59:18 +0530	[thread overview]
Message-ID: <63a70152-3153-a4eb-28c3-9d43a049ba57@intel.com> (raw)
In-Reply-To: <20220311200027.33701-1-ashutosh.dixit@intel.com>



On 12-03-2022 01:30, Ashutosh Dixit wrote:
> Because VLV_GT_RENDER_RC6 == GEN6_GT_GFX_RC6, the IS_VALLEYVIEW() check is
> not needed. Neither is the check present in other code paths which call
> intel_rc6_residency_ns() (in functions gen6_drpc(), rc6_residency() and
> rc6_residency_ms_show()).
> 
> Signed-off-by: Ashutosh Dixit <ashutosh.dixit@intel.com>
> ---
>   drivers/gpu/drm/i915/i915_pmu.c | 5 +----
>   1 file changed, 1 insertion(+), 4 deletions(-)
> 
> diff --git a/drivers/gpu/drm/i915/i915_pmu.c b/drivers/gpu/drm/i915/i915_pmu.c
> index cfc21042499d..3e3b09588fd3 100644
> --- a/drivers/gpu/drm/i915/i915_pmu.c
> +++ b/drivers/gpu/drm/i915/i915_pmu.c
> @@ -148,10 +148,7 @@ static u64 __get_rc6(struct intel_gt *gt)
>   	struct drm_i915_private *i915 = gt->i915;
>   	u64 val;
>   
> -	val = intel_rc6_residency_ns(&gt->rc6,
> -				     IS_VALLEYVIEW(i915) ?
> -				     VLV_GT_RENDER_RC6 :
> -				     GEN6_GT_GFX_RC6);
> +	val = intel_rc6_residency_ns(&gt->rc6, GEN6_GT_GFX_RC6);
This change looks fine.
Reviewed-by: Badal Nilawar <badal.nilawar@intel.com>
>   
>   	if (HAS_RC6p(i915))
>   		val += intel_rc6_residency_ns(&gt->rc6, GEN6_GT_GFX_RC6p);

  parent reply	other threads:[~2022-03-14  5:29 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-11 20:00 [Intel-gfx] [PATCH] drm/i915/pmu: Drop redundant IS_VALLEYVIEW check in __get_rc6() Ashutosh Dixit
2022-03-11 21:55 ` [Intel-gfx] ✓ Fi.CI.BAT: success for " Patchwork
2022-03-11 23:51 ` [Intel-gfx] ✓ Fi.CI.IGT: " Patchwork
2022-03-14  5:29 ` Nilawar, Badal [this message]
2022-03-14  9:33 ` [Intel-gfx] [PATCH] " Jani Nikula
  -- strict thread matches above, loose matches on Subject: below --
2022-03-14 16:13 Ashutosh Dixit

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=63a70152-3153-a4eb-28c3-9d43a049ba57@intel.com \
    --to=badal.nilawar@intel.com \
    --cc=ashutosh.dixit@intel.com \
    --cc=intel-gfx@lists.freedesktop.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