From: Jens Axboe <axboe@kernel.dk>
To: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
Cc: Steven Rostedt <rostedt@goodmis.org>,
Peter Zijlstra <peterz@infradead.org>,
Daniel Wagner <wagi@monom.org>,
Thomas Gleixner <tglx@linutronix.de>,
LKML <linux-kernel@vger.kernel.org>,
linux-rt-users@vger.kernel.org
Subject: Re: [ANNOUNCE] v5.14-rc4-rt4
Date: Wed, 4 Aug 2021 10:57:11 -0600 [thread overview]
Message-ID: <71d37a7d-af53-945e-0c49-3cb902487df4@kernel.dk> (raw)
In-Reply-To: <20210804164735.sq6sjejusa37abkw@linutronix.de>
On 8/4/21 10:47 AM, Sebastian Andrzej Siewior wrote:
> On 2021-08-04 10:22:59 [-0600], Jens Axboe wrote:
>>
>> In that regard, I do still consider those patches out-of-tree, which
>> they are. And while I'm more sympathetic to them compared to other
>> out-of-tree code as there's a long term plan to get it all in, it's
>> still out-of-tree. Best solution here is probably to just carry that
>> particular change in the RT patchset for now.
>
> So today in the morning I learned that there is a memory allocation in
> an IRQ-off section and now, a patch later, it is almost gone. So that
> makes me actually happy :)
1 out of 2 is better than 0 ;-)
> The spin_lock_irq() vs local_irq_disable() + spin_lock() is documented
> in Documentation/locking/locktypes.rst.
> That said I have no problem by carrying that patch in the RT-patchset
> and revisit it later.
Right, I suspect that was added as a pre RT patch dump at some point.
It's a newer thing. Is it actually possible to set PREEMPT_RT in the
mainline kernel? Looks like it depends on ARCH_SUPPORTS_RT and nobody
sets that.
So I agree that just carrying your solution in the RT patchset is fine
for now, we can revisit later.
--
Jens Axboe
next prev parent reply other threads:[~2021-08-04 16:57 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-02 16:27 [ANNOUNCE] v5.14-rc4-rt4 Sebastian Andrzej Siewior
2021-08-04 8:24 ` Daniel Wagner
2021-08-04 10:43 ` Sebastian Andrzej Siewior
2021-08-04 10:48 ` Sebastian Andrzej Siewior
2021-08-04 11:00 ` Sebastian Andrzej Siewior
2021-08-04 13:17 ` Peter Zijlstra
2021-08-04 13:32 ` Jens Axboe
2021-08-04 14:23 ` Jens Axboe
2021-08-04 15:33 ` Sebastian Andrzej Siewior
2021-08-04 15:39 ` Jens Axboe
2021-08-04 15:47 ` Sebastian Andrzej Siewior
2021-08-04 15:49 ` Jens Axboe
2021-08-04 15:57 ` Sebastian Andrzej Siewior
2021-08-04 16:05 ` Jens Axboe
2021-08-04 16:20 ` Sebastian Andrzej Siewior
2021-08-04 16:20 ` Jens Axboe
2021-08-04 16:20 ` Steven Rostedt
2021-08-04 16:22 ` Jens Axboe
2021-08-04 16:47 ` Sebastian Andrzej Siewior
2021-08-04 16:57 ` Jens Axboe [this message]
2021-08-04 17:02 ` Sebastian Andrzej Siewior
2021-08-10 7:40 ` Sebastian Andrzej Siewior
2021-08-10 11:22 ` [PATCH] io-wq: remove GFP_ATOMIC allocation off schedule out path kernel test robot
2021-08-10 15:22 ` kernel test robot
2021-08-04 16:17 ` [ANNOUNCE] v5.14-rc4-rt4 Steven Rostedt
2021-08-04 16:22 ` Sebastian Andrzej Siewior
2021-08-04 16:25 ` Steven Rostedt
2021-08-04 16:31 ` Sebastian Andrzej Siewior
2021-08-04 16:47 ` Steven Rostedt
2021-08-04 16:57 ` 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=71d37a7d-af53-945e-0c49-3cb902487df4@kernel.dk \
--to=axboe@kernel.dk \
--cc=bigeasy@linutronix.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rt-users@vger.kernel.org \
--cc=peterz@infradead.org \
--cc=rostedt@goodmis.org \
--cc=tglx@linutronix.de \
--cc=wagi@monom.org \
/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).