[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <Z6Nf32YB/J0LMSPw@duo.ucw.cz>
Date: Wed, 5 Feb 2025 13:55:59 +0100
From: Pavel Machek <pavel@...x.de>
To: Sebastian Andrzej Siewior <bigeasy@...utronix.de>
Cc: Kazuhiro Hayashi <kazuhiro3.hayashi@...hiba.co.jp>,
linux-kernel@...r.kernel.org, linux-rt-devel@...ts.linux.dev,
cip-dev@...ts.cip-project.org, tglx@...utronix.de,
rostedt@...dmis.org, linux-rt-users@...r.kernel.org, pavel@...x.de
Subject: Re: [PATCH 4.4 4.9 v1 2/2] mm: slub: allocate_slab() enables IRQ
right after scheduler starts
Hi!
> > An simple option would be to backport the series[3], which is possible
> > and has been verified[4]. However, that series pulls functional
> > changes like SYSTEM_SCHEDULING and adjustments for it,
> > early might_sleep() and smp_processor_id() supports, etc.
> > Therefore, this patch uses an extra (but not mainline) flag
> > "system_scheduling" provided by the prior patch instead of
> > introducing SYSTEM_SCHEDULING, then uses the same condition as
> > newer RT kernels in allocate_slab().
>
> The proposal looks okay. However the verified upstream version not only
> addresses your issue but also makes smp_processor_id() and might_sleep()
> work in the early phase. I would prefer the upstream solution for those
> two reasons.
So... first, thanks for review. This is mostly my fault, Kazuhiro
Hayashi did full backport, but I asked for minimal version.
AFAICT there's no place for stable-rt to apply this, so we'll just be
taking this to our trees in CIP project. (And I prefer smaller
version. Additional checking is nice for development but not so nice
this late in development cycle).
Best regards,
Pavel
--
DENX Software Engineering GmbH, Managing Director: Erika Unter
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Download attachment "signature.asc" of type "application/pgp-signature" (196 bytes)
Powered by blists - more mailing lists