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: Wed, 9 Jul 2025 21:44:43 +0200 [thread overview]
Message-ID: <20250709194443.lkevdn6m@linutronix.de> (raw)
In-Reply-To: <aG6nMhimN1lWKAEP@intel.com>
On 2025-07-09 20:30:26 [+0300], Ville Syrjälä wrote:
> >
> > It seems like the critical uncore lock is currently held in a lot of
> > places and potentially for a long time.
>
> It shouldn't be held for that long. I think it should just be
> a raw spinlock.
What about I resubmit the series and we look again? I don't think the
lock should be made raw just to be done with it.
Sebastian
next prev parent reply other threads:[~2025-07-09 19:44 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 [this message]
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
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=20250709194443.lkevdn6m@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