From: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
To: Sean V Kelley <sean.v.kelley@linux.intel.com>
Cc: Clark Williams <clark.williams@gmail.com>,
tglx@linutronix.de, linux-rt-users@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PREEMPT_RT PATCH 2/3] i915: convert all irq_locks spinlocks to raw spinlocks
Date: Fri, 27 Sep 2019 14:29:34 +0200 [thread overview]
Message-ID: <20190927122934.2bz6ysx27ecw2uxa@linutronix.de> (raw)
In-Reply-To: <9EF2695D-3FBD-40E0-BE8A-EB71AF4155A5@linux.intel.com>
On 2019-09-16 14:21:22 [-0700], Sean V Kelley wrote:
> I’ve tested this also on the v5.2.14-rt7 and can confirm that it avoids the need for making the locks raw.
>
> Tested-by: Sean V Kelley <sean.v.kelley@linux.intel.com>
Good. I went for an alternative approach in v5.2.17-rt9. Now I believe
that the three here are obsolete. If not, please give a sign.
> Thanks,
>
> Sean
Sebastian
next prev parent reply other threads:[~2019-09-27 12:29 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-20 0:33 [PREEMPT_RT PATCH 0/3] i915 fixups for lockdep/lockdebugging Clark Williams
2019-08-20 0:33 ` [PREEMPT_RT PATCH 1/3] i915: do not call lockdep_assert_irqs_disabled() on PREEMPT_RT Clark Williams
2019-09-25 16:47 ` Sebastian Andrzej Siewior
2019-08-20 0:33 ` [PREEMPT_RT PATCH 2/3] i915: convert all irq_locks spinlocks to raw spinlocks Clark Williams
2019-09-03 8:03 ` Sebastian Andrzej Siewior
2019-09-03 13:09 ` Sebastian Andrzej Siewior
2019-09-16 21:21 ` Sean V Kelley
2019-09-27 12:29 ` Sebastian Andrzej Siewior [this message]
[not found] ` <CAPAFJkofsYgSOxzM4JDkOV3Ra0C-AEpU2eZJjR9F9e_qv-6=rg@mail.gmail.com>
2019-09-27 15:18 ` Sean V Kelley
2019-08-20 0:33 ` [PREEMPT_RT PATCH 3/3] i915: convert uncore lock to raw spinlock Clark Williams
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=20190927122934.2bz6ysx27ecw2uxa@linutronix.de \
--to=bigeasy@linutronix.de \
--cc=clark.williams@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rt-users@vger.kernel.org \
--cc=sean.v.kelley@linux.intel.com \
--cc=tglx@linutronix.de \
/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).