Intel-GFX Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Tvrtko Ursulin <tvrtko.ursulin@linux.intel.com>
To: Andi Shyti <andi.shyti@linux.intel.com>,
	intel-gfx@lists.freedesktop.org,
	 dri-devel@lists.freedesktop.org
Cc: Chris Wilson <chris.p.wilson@intel.com>
Subject: Re: [Intel-gfx] [PATCH] drm/i915/trace: Removed unused frequency trace
Date: Tue, 11 Oct 2022 15:23:23 +0100	[thread overview]
Message-ID: <2c6001fe-a8bf-8bf0-7452-51420f117282@linux.intel.com> (raw)
In-Reply-To: <20221011135940.367048-1-andi.shyti@linux.intel.com>


On 11/10/2022 14:59, Andi Shyti wrote:
> Commit 3e7abf814193 ("drm/i915: Extract GT render power state management")
> removes the "trace_intel_gpu_freq_change()" trace points but
> their definition was left without users. Remove it.
> 
> Suggested-by: Tvrtko Ursulin <tvrtko.ursulin@linux.intel.com>
> Signed-off-by: Andi Shyti <andi.shyti@linux.intel.com>
> Cc: Chris Wilson <chris@chris-wilson.co.uk>
> ---
>   drivers/gpu/drm/i915/i915_trace.h | 15 ---------------
>   1 file changed, 15 deletions(-)
> 
> diff --git a/drivers/gpu/drm/i915/i915_trace.h b/drivers/gpu/drm/i915/i915_trace.h
> index 37b5c9e9d260..c70a02517e02 100644
> --- a/drivers/gpu/drm/i915/i915_trace.h
> +++ b/drivers/gpu/drm/i915/i915_trace.h
> @@ -671,21 +671,6 @@ TRACE_EVENT_CONDITION(i915_reg_rw,
>   		(u32)(__entry->val >> 32))
>   );
>   
> -TRACE_EVENT(intel_gpu_freq_change,
> -	    TP_PROTO(u32 freq),
> -	    TP_ARGS(freq),
> -
> -	    TP_STRUCT__entry(
> -			     __field(u32, freq)
> -			     ),
> -
> -	    TP_fast_assign(
> -			   __entry->freq = freq;
> -			   ),
> -
> -	    TP_printk("new_freq=%u", __entry->freq)
> -);
> -
>   /**
>    * DOC: i915_ppgtt_create and i915_ppgtt_release tracepoints
>    *

Reviewed-by: Tvrtko Ursulin <tvrtko.ursulin@intel.com>

Regards,

Tvrtko

  reply	other threads:[~2022-10-11 14:23 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-11 13:59 [Intel-gfx] [PATCH] drm/i915/trace: Removed unused frequency trace Andi Shyti
2022-10-11 14:23 ` Tvrtko Ursulin [this message]
2022-10-11 16:02 ` [Intel-gfx] ✗ Fi.CI.SPARSE: warning for " Patchwork
2022-10-11 16:24 ` [Intel-gfx] ✓ Fi.CI.BAT: success " Patchwork
2022-10-11 20:02 ` [Intel-gfx] ✗ Fi.CI.IGT: failure " Patchwork
2022-10-11 22:17   ` Andi Shyti

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=2c6001fe-a8bf-8bf0-7452-51420f117282@linux.intel.com \
    --to=tvrtko.ursulin@linux.intel.com \
    --cc=andi.shyti@linux.intel.com \
    --cc=chris.p.wilson@intel.com \
    --cc=dri-devel@lists.freedesktop.org \
    --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