From: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
To: "Ville Syrjälä" <ville.syrjala@linux.intel.com>
Cc: Ben Hutchings <ben@decadent.org.uk>,
linux-rt-users@vger.kernel.org, intel-gfx@lists.freedesktop.org,
Debian kernel maintainers <debian-kernel@lists.debian.org>
Subject: Re: PREEMPT_RT vs i915
Date: Thu, 10 Jul 2025 17:20:08 +0200 [thread overview]
Message-ID: <20250710152008.ZyaHjC3w@linutronix.de> (raw)
In-Reply-To: <aG_VzpXaYRCQQGYt@intel.com>
On 2025-07-10 18:04:42 [+0300], Ville Syrjälä wrote:
>
> When this was last discussed I suggested that there should be a
> versions of the tracepoint macros that do the sampling outside
> the lock, but that wasn't deemed acceptable for whatever reason.
> I don't even know why the current macros are doing the
> sampling while holding the lock...
Any objections to me sending the batch and we figure out later how get
the tracepoints for i915 enabled again on RT?
It would be an improvement because you could take a vanilla kernel and
enable PREEMPT_RT and you would only miss the tracepoints while now you
can't enable i915 at all and XE either doesn't compile or spills
warnings at runtime due to the code it shares with i915.
Sebastian
next prev parent reply other threads:[~2025-07-10 15:20 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-08 19:35 PREEMPT_RT vs i915 Ben Hutchings
2025-07-09 17:30 ` Ville Syrjälä
2025-07-09 19:44 ` Sebastian Andrzej Siewior
2025-07-09 20:09 ` Ville Syrjälä
2025-07-09 22:04 ` Matthew Brost
2025-07-10 6:30 ` Sebastian Andrzej Siewior
2025-07-10 15:21 ` Ville Syrjälä
2025-07-10 18:04 ` Matthew Brost
2025-07-10 18:15 ` Ville Syrjälä
2025-07-10 4:52 ` Mike Galbraith
2025-07-10 15:50 ` Ville Syrjälä
2025-07-11 2:36 ` Mike Galbraith
2025-07-11 3:33 ` Mike Galbraith
2025-07-11 8:05 ` block: lockdep splat with RT config v6.15+ Mike Galbraith
2025-07-11 8:59 ` Sebastian Andrzej Siewior
2025-07-11 9:03 ` Mike Galbraith
2025-07-10 6:41 ` PREEMPT_RT vs i915 Sebastian Andrzej Siewior
2025-07-10 15:04 ` Ville Syrjälä
2025-07-10 15:20 ` Sebastian Andrzej Siewior [this message]
2025-07-11 12:35 ` Maarten Lankhorst
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=20250710152008.ZyaHjC3w@linutronix.de \
--to=bigeasy@linutronix.de \
--cc=ben@decadent.org.uk \
--cc=debian-kernel@lists.debian.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=linux-rt-users@vger.kernel.org \
--cc=ville.syrjala@linux.intel.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