Intel-XE Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Steven Rostedt <rostedt@goodmis.org>
To: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
Cc: intel-gfx@lists.freedesktop.org, intel-xe@lists.freedesktop.org,
	Jani Nikula <jani.nikula@linux.intel.com>,
	Joonas Lahtinen <joonas.lahtinen@linux.intel.com>,
	Rodrigo Vivi <rodrigo.vivi@intel.com>,
	Thomas Gleixner <tglx@linutronix.de>,
	Tvrtko Ursulin <tursulin@ursulin.net>
Subject: Re: [PATCH 05/10] drm/i915: skip DRM_I915_LOW_LEVEL_TRACEPOINTS with NOTRACE
Date: Mon, 8 Apr 2024 13:06:50 -0400	[thread overview]
Message-ID: <20240408130650.6f9c1e1c@rorschach.local.home> (raw)
In-Reply-To: <20240405142737.920626-6-bigeasy@linutronix.de>

On Fri,  5 Apr 2024 16:18:23 +0200
Sebastian Andrzej Siewior <bigeasy@linutronix.de> wrote:

> The order of the header files is important. If this header file is
> included after tracepoint.h was included then the NOTRACE here becomes a
> nop. Currently this happens for two .c files which use the tracepoitns
> behind DRM_I915_LOW_LEVEL_TRACEPOINTS.

The NOTRACE should not be included in the individual trace files.

Can you show where this is an issue. I think this is fixing the symptom
and not the bug itself.

-- Steve


> 
> Cc: Steven Rostedt <rostedt@goodmis.org>
> Signed-off-by: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
> Signed-off-by: Thomas Gleixner <tglx@linutronix.de>
> ---
>  drivers/gpu/drm/i915/i915_trace.h | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/drivers/gpu/drm/i915/i915_trace.h b/drivers/gpu/drm/i915/i915_trace.h
> index c54653cf72c95..3c51620d011b1 100644
> --- a/drivers/gpu/drm/i915/i915_trace.h
> +++ b/drivers/gpu/drm/i915/i915_trace.h
> @@ -326,7 +326,7 @@ DEFINE_EVENT(i915_request, i915_request_add,
>  	     TP_ARGS(rq)
>  );
>  
> -#if defined(CONFIG_DRM_I915_LOW_LEVEL_TRACEPOINTS)
> +#if defined(CONFIG_DRM_I915_LOW_LEVEL_TRACEPOINTS) && !defined(NOTRACE)
>  DEFINE_EVENT(i915_request, i915_request_guc_submit,
>  	     TP_PROTO(struct i915_request *rq),
>  	     TP_ARGS(rq)


  reply	other threads:[~2024-04-08 17:06 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-05 14:18 [PATCH 00/10] drm/i915: PREEMPT_RT related fixups Sebastian Andrzej Siewior
2024-04-05 14:18 ` [PATCH 01/10] drm/i915: Use preempt_disable/enable_rt() where recommended Sebastian Andrzej Siewior
2024-04-05 14:18 ` [PATCH 02/10] drm/i915: Don't disable interrupts on PREEMPT_RT during atomic updates Sebastian Andrzej Siewior
2024-04-05 14:18 ` [PATCH 03/10] drm/i915: Don't check for atomic context on PREEMPT_RT Sebastian Andrzej Siewior
2024-04-05 14:18 ` [PATCH 04/10] drm/i915: Disable tracing points " Sebastian Andrzej Siewior
2024-04-05 14:18 ` [PATCH 05/10] drm/i915: skip DRM_I915_LOW_LEVEL_TRACEPOINTS with NOTRACE Sebastian Andrzej Siewior
2024-04-08 17:06   ` Steven Rostedt [this message]
2024-04-09 11:06     ` Sebastian Andrzej Siewior
2024-04-09 15:55       ` Steven Rostedt
2024-04-10 11:08         ` Sebastian Andrzej Siewior
2024-04-10 14:09           ` Steven Rostedt
2024-04-05 14:18 ` [PATCH 06/10] drm/i915/gt: Queue and wait for the irq_work item Sebastian Andrzej Siewior
2024-04-05 14:18 ` [PATCH 07/10] drm/i915/gt: Use spin_lock_irq() instead of local_irq_disable() + spin_lock() Sebastian Andrzej Siewior
2024-04-05 14:18 ` [PATCH 08/10] drm/i915: Drop the irqs_disabled() check Sebastian Andrzej Siewior
2024-04-05 14:18 ` [PATCH 09/10] drm/i915/guc: Consider also RCU depth in busy loop Sebastian Andrzej Siewior
2024-06-11 22:18   ` Rodrigo Vivi
2024-04-05 14:18 ` [PATCH 10/10] Revert "drm/i915: Depend on !PREEMPT_RT." Sebastian Andrzej Siewior
2024-04-05 17:16 ` ✗ CI.Patch_applied: failure for drm/i915: PREEMPT_RT related fixups Patchwork
2024-04-10 11:58 ` ✗ CI.Patch_applied: failure for drm/i915: PREEMPT_RT related fixups. (rev2) Patchwork
2024-06-05 10:01 ` [PATCH 00/10] drm/i915: PREEMPT_RT related fixups Sebastian Andrzej Siewior
2024-06-11 13:06   ` Tvrtko Ursulin
2024-06-11 15:14     ` Sebastian Andrzej Siewior
2024-06-11 22:25       ` Rodrigo Vivi
2024-06-13  8:36         ` Sebastian Andrzej Siewior

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=20240408130650.6f9c1e1c@rorschach.local.home \
    --to=rostedt@goodmis.org \
    --cc=bigeasy@linutronix.de \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=intel-xe@lists.freedesktop.org \
    --cc=jani.nikula@linux.intel.com \
    --cc=joonas.lahtinen@linux.intel.com \
    --cc=rodrigo.vivi@intel.com \
    --cc=tglx@linutronix.de \
    --cc=tursulin@ursulin.net \
    /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