From: Jani Nikula <jani.nikula@linux.intel.com>
To: Maarten Lankhorst <dev@lankhorst.se>,
intel-gfx@lists.freedesktop.org, intel-xe@lists.freedesktop.org
Cc: Sebastian Andrzej Siewior <bigeasy@linutronix.de>,
Maarten Lankhorst <dev@lankhorst.se>,
Tvrtko Ursulin <tvrtko.ursulin@igalia.com>,
Luca Abeni <lucabe72@gmail.com>,
Steven Rostedt <rostedt@goodmis.org>
Subject: Re: [PATCH 1/2] drm/i915: Disable tracepoints for PREEMPT_RT
Date: Fri, 29 Aug 2025 14:15:24 +0300 [thread overview]
Message-ID: <f1c033468a41cfb891e907981118e1a34b71d6a4@intel.com> (raw)
In-Reply-To: <20250828090944.101069-1-dev@lankhorst.se>
On Thu, 28 Aug 2025, Maarten Lankhorst <dev@lankhorst.se> wrote:
> 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_intel_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.
>
> [mlankhorst]
> The original patch was insufficient, and since the tracing
> infrastructure does not allow for partial disabling of tracepoints.
>
> Completely disable tracing for the entire i915 driver in PREEMPT_RT,
> a separate fix for display tracepoints on xe is added to make those
> work.
>
> Cc: Tvrtko Ursulin <tvrtko.ursulin@igalia.com>
> Reported-by: Luca Abeni <lucabe72@gmail.com>
> Cc: Steven Rostedt <rostedt@goodmis.org>
> Co-developed-by: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
> Signed-off-by: Maarten Lankhorst <dev@lankhorst.se>
> ---
> drivers/gpu/drm/i915/Makefile | 5 +++++
> 1 file changed, 5 insertions(+)
>
> diff --git a/drivers/gpu/drm/i915/Makefile b/drivers/gpu/drm/i915/Makefile
> index 8535434430728..ba825d7f6ddf5 100644
> --- a/drivers/gpu/drm/i915/Makefile
> +++ b/drivers/gpu/drm/i915/Makefile
> @@ -13,6 +13,11 @@ subdir-ccflags-$(CONFIG_DRM_I915_WERROR) += -Werror
> # drivers. Define I915 when building i915.
> subdir-ccflags-y += -DI915
>
> +# Disable tracepoints on i915 for PREEMPT_RT, unfortunately
> +# it's an all or nothing flag. You cannot selectively disable
> +# only some tracepoints.
Should probably be a FIXME.
Acked-by: Jani Nikula <jani.nikula@intel.com>
> +subdir-ccflags-$(CONFIG_PREEMPT_RT) += -DNOTRACE
> +
> subdir-ccflags-y += -I$(src)
>
> # Please keep these build lists sorted!
--
Jani Nikula, Intel
prev parent reply other threads:[~2025-08-29 11:15 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-28 9:09 [PATCH 1/2] drm/i915: Disable tracepoints for PREEMPT_RT Maarten Lankhorst
2025-08-28 9:09 ` [PATCH 2/2] drm/i915/display: Make tracepoints work correctly on xe with PREEMPT_RT Maarten Lankhorst
2025-08-29 11:14 ` Jani Nikula
2025-08-29 11:55 ` Maarten Lankhorst
2025-08-29 12:32 ` Jani Nikula
2025-08-29 13:18 ` Maarten Lankhorst
2025-08-29 12:08 ` Sebastian Andrzej Siewior
2025-08-29 12:37 ` Maarten Lankhorst
2025-08-29 13:11 ` Sebastian Andrzej Siewior
2025-08-28 16:19 ` ✓ i915.CI.BAT: success for series starting with [1/2] drm/i915: Disable tracepoints for PREEMPT_RT Patchwork
2025-08-28 21:46 ` ✗ i915.CI.Full: failure " Patchwork
2025-08-29 11:15 ` Jani Nikula [this message]
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=f1c033468a41cfb891e907981118e1a34b71d6a4@intel.com \
--to=jani.nikula@linux.intel.com \
--cc=bigeasy@linutronix.de \
--cc=dev@lankhorst.se \
--cc=intel-gfx@lists.freedesktop.org \
--cc=intel-xe@lists.freedesktop.org \
--cc=lucabe72@gmail.com \
--cc=rostedt@goodmis.org \
--cc=tvrtko.ursulin@igalia.com \
/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;
as well as URLs for NNTP newsgroup(s).