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: Wed, 10 Apr 2024 10:09:08 -0400 [thread overview]
Message-ID: <20240410100908.7d13393c@gandalf.local.home> (raw)
In-Reply-To: <20240410110857.BBV2fQYP@linutronix.de>
On Wed, 10 Apr 2024 13:08:57 +0200
Sebastian Andrzej Siewior <bigeasy@linutronix.de> wrote:
> On 2024-04-09 11:55:33 [-0400], Steven Rostedt wrote:
> > I believe you need to do it in the .c file:
> >
> > Can you try something like this?
> >
> …
> > ?
>
> I tried and nothing changed because the lowlevel config option isn't the
> problem. What about I drop this and replace 4/10 from this series with
> the patch below? After enabling all tracing I don't see any events in
> events/i915.
I don't see anything wrong with this approach.
>
> Sebastian
>
> --------------------->8----------------------------
>
> From: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
> Date: Thu, 6 Dec 2018 09:52:20 +0100
> Subject: [PATCH] drm/i915: Disable tracing points on PREEMPT_RT
>
> Luca Abeni reported this:
> | BUG: scheduling while atomic: kworker/u8:2/15203/0x00000003
> | CPU: 1 PID: 15203 Comm: kworker/u8:2 Not tainted 4.19.1-rt3 #10
> | Call Trace:
> | rt_spin_lock+0x3f/0x50
> | gen6_read32+0x45/0x1d0 [i915]
> | g4x_get_vblank_counter+0x36/0x40 [i915]
> | trace_event_raw_event_i915_pipe_update_start+0x7d/0xf0 [i915]
>
> The tracing events use trace_i915_pipe_update_start() among other events
> use functions acquire spinlock_t locks which are transformed into
> sleeping locks on PREEMPT_RT. A few trace points use
> intel_get_crtc_scanline(), others use ->get_vblank_counter() wich also
> might acquire a sleeping locks on PREEMPT_RT.
> At the time the arguments are evaluated within trace point, preemption
> is disabled and so the locks must not be acquired on PREEMPT_RT.
>
> Based on this I don't see any other way than disable trace points on
> PREMPT_RT.
>
> Reported-by: Luca Abeni <lucabe72@gmail.com>
> Cc: Steven Rostedt <rostedt@goodmis.org>
> Signed-off-by: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
> ---
> drivers/gpu/drm/i915/display/intel_display_trace.h | 4 ++++
> drivers/gpu/drm/i915/i915_trace.h | 4 ++++
> 2 files changed, 8 insertions(+)
>
> diff --git a/drivers/gpu/drm/i915/display/intel_display_trace.h b/drivers/gpu/drm/i915/display/intel_display_trace.h
> index 7862e7cefe027..e4608d855bfba 100644
> --- a/drivers/gpu/drm/i915/display/intel_display_trace.h
> +++ b/drivers/gpu/drm/i915/display/intel_display_trace.h
> @@ -9,6 +9,10 @@
> #if !defined(__INTEL_DISPLAY_TRACE_H__) || defined(TRACE_HEADER_MULTI_READ)
> #define __INTEL_DISPLAY_TRACE_H__
>
> +#ifdef CONFIG_PREEMPT_RT
Hmm, should these be:
#if defined(CONFIG_PREEMPT_RT) && !defined(NOTRACE)
?
because it's not protected due to the TRACE_HEADER_MULTI_READ.
-- Steve
> +#define NOTRACE
> +#endif
> +
> #include <linux/string_helpers.h>
> #include <linux/types.h>
> #include <linux/tracepoint.h>
> diff --git a/drivers/gpu/drm/i915/i915_trace.h b/drivers/gpu/drm/i915/i915_trace.h
> index ce1cbee1b39dd..c54653cf72c95 100644
> --- a/drivers/gpu/drm/i915/i915_trace.h
> +++ b/drivers/gpu/drm/i915/i915_trace.h
> @@ -6,6 +6,10 @@
> #if !defined(_I915_TRACE_H_) || defined(TRACE_HEADER_MULTI_READ)
> #define _I915_TRACE_H_
>
> +#ifdef CONFIG_PREEMPT_RT
> +#define NOTRACE
> +#endif
> +
> #include <linux/stringify.h>
> #include <linux/types.h>
> #include <linux/tracepoint.h>
next prev parent reply other threads:[~2024-04-10 14: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
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 [this message]
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=20240410100908.7d13393c@gandalf.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