Intel-GFX Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "Ville Syrjälä" <ville.syrjala@linux.intel.com>
To: Chris Wilson <chris@chris-wilson.co.uk>
Cc: Daniel Vetter <daniel.vetter@intel.com>, intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH] drm/i915: Remove unused i915_flip tracepoints
Date: Tue, 8 May 2018 18:35:18 +0300	[thread overview]
Message-ID: <20180508153518.GJ23723@intel.com> (raw)
In-Reply-To: <20180508151552.31024-1-chris@chris-wilson.co.uk>

On Tue, May 08, 2018 at 04:15:52PM +0100, Chris Wilson wrote:
> The i915_flip* tracepoints are no longer in use since the removal of CS
> flip in commit 8b5d27b911d7 ("drm/i915: Remove intel_flip_work
> infrastructure")
> 
> References: 8b5d27b911d7 ("drm/i915: Remove intel_flip_work infrastructure")
> Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>
> Cc: Maarten Lankhorst <maarten.lankhorst@linux.intel.com>
> Cc: Ville Syrjälä <ville.syrjala@linux.intel.com>
> Cc: Daniel Vetter <daniel.vetter@intel.com>

Reviewed-by: Ville Syrjälä <ville.syrjala@linux.intel.com>

> ---
>  drivers/gpu/drm/i915/i915_trace.h | 36 -------------------------------
>  1 file changed, 36 deletions(-)
> 
> diff --git a/drivers/gpu/drm/i915/i915_trace.h b/drivers/gpu/drm/i915/i915_trace.h
> index 77ee5e53eb32..8cc3a256f29d 100644
> --- a/drivers/gpu/drm/i915/i915_trace.h
> +++ b/drivers/gpu/drm/i915/i915_trace.h
> @@ -834,42 +834,6 @@ DEFINE_EVENT(i915_request, i915_request_wait_end,
>  	    TP_ARGS(rq)
>  );
>  
> -TRACE_EVENT(i915_flip_request,
> -	    TP_PROTO(int plane, struct drm_i915_gem_object *obj),
> -
> -	    TP_ARGS(plane, obj),
> -
> -	    TP_STRUCT__entry(
> -		    __field(int, plane)
> -		    __field(struct drm_i915_gem_object *, obj)
> -		    ),
> -
> -	    TP_fast_assign(
> -		    __entry->plane = plane;
> -		    __entry->obj = obj;
> -		    ),
> -
> -	    TP_printk("plane=%d, obj=%p", __entry->plane, __entry->obj)
> -);
> -
> -TRACE_EVENT(i915_flip_complete,
> -	    TP_PROTO(int plane, struct drm_i915_gem_object *obj),
> -
> -	    TP_ARGS(plane, obj),
> -
> -	    TP_STRUCT__entry(
> -		    __field(int, plane)
> -		    __field(struct drm_i915_gem_object *, obj)
> -		    ),
> -
> -	    TP_fast_assign(
> -		    __entry->plane = plane;
> -		    __entry->obj = obj;
> -		    ),
> -
> -	    TP_printk("plane=%d, obj=%p", __entry->plane, __entry->obj)
> -);
> -
>  TRACE_EVENT_CONDITION(i915_reg_rw,
>  	TP_PROTO(bool write, i915_reg_t reg, u64 val, int len, bool trace),
>  
> -- 
> 2.17.0

-- 
Ville Syrjälä
Intel
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx

  reply	other threads:[~2018-05-08 15:35 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-08 15:15 [PATCH] drm/i915: Remove unused i915_flip tracepoints Chris Wilson
2018-05-08 15:35 ` Ville Syrjälä [this message]
2018-05-08 20:50   ` Chris Wilson
2018-05-08 16:46 ` ✗ Fi.CI.CHECKPATCH: warning for " Patchwork
2018-05-08 17:03 ` ✓ Fi.CI.BAT: success " Patchwork
2018-05-08 20:18 ` ✗ Fi.CI.IGT: 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=20180508153518.GJ23723@intel.com \
    --to=ville.syrjala@linux.intel.com \
    --cc=chris@chris-wilson.co.uk \
    --cc=daniel.vetter@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