From: Pavel Machek <pavel@denx.de>
To: Kazuhiro Hayashi <kazuhiro3.hayashi@toshiba.co.jp>
Cc: linux-kernel@vger.kernel.org, linux-rt-devel@lists.linux.dev,
cip-dev@lists.cip-project.org, bigeasy@linutronix.de,
tglx@linutronix.de, rostedt@goodmis.org,
linux-rt-users@vger.kernel.org
Subject: Re: [PATCH 4.4 4.9 v1 0/2] Fix repeated WARNING in unpin_current_cpu()
Date: Fri, 2 May 2025 12:19:15 +0200 [thread overview]
Message-ID: <aBScIx13vT5c1i8V@duo.ucw.cz> (raw)
In-Reply-To: <1738629964-11977-1-git-send-email-kazuhiro3.hayashi@toshiba.co.jp>
[-- Attachment #1: Type: text/plain, Size: 1219 bytes --]
Hi!
> This is a patch series for v4.4-rt and v4.9-rt to resolve problem that
> WARNING in unpin_current_cpu() happens repeatedly while kernel is booting.
> Please see commit message of the second patch (2/2) for more details about
> the problem and how it's resolved. The first patch (1/2) is a preparation
> for the fix (2/2), considering compatibility issue in future updates.
>
> As the both v4.4-rt and v4.9-rt have been EOL already, it's not expected
> that this series is applied to the branches anymore.
> On the other hand, the Civil Infrastructure Platform Project (CIP)
> has been maintaining its 4.4 SLTS RT kernel[1][2] based on v4.4-rt,
> and needs to fix the problem above by this series.
>
> It is much appreciated if RT experts could take a look at the series
> and give feedbacks about its way to resolve the problem, which is
> based on the same approach as changes happend around v4.14-rt.
Thanks for patches, and sorry for the delays. 4.4.302-cip98-rt55 is
out, and it should contain your fixes.
Best regards,
Pavel
--
DENX Software Engineering GmbH, Managing Director: Erika Unter
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 195 bytes --]
prev parent reply other threads:[~2025-05-02 10:19 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-04 0:46 Kazuhiro Hayashi
2025-02-04 0:46 ` [PATCH 4.4 4.9 v1 1/2] init: Introduce system_scheduling flag for allocate_slab() Kazuhiro Hayashi
2025-02-04 0:46 ` [PATCH 4.4 4.9 v1 2/2] mm: slub: allocate_slab() enables IRQ right after scheduler starts Kazuhiro Hayashi
2025-02-04 8:18 ` Sebastian Andrzej Siewior
2025-02-05 12:55 ` Pavel Machek
2025-02-10 7:20 ` kazuhiro3.hayashi
2025-02-10 10:18 ` Sebastian Andrzej Siewior
2025-02-12 7:57 ` kazuhiro3.hayashi
2025-05-02 10:19 ` Pavel Machek [this message]
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=aBScIx13vT5c1i8V@duo.ucw.cz \
--to=pavel@denx.de \
--cc=bigeasy@linutronix.de \
--cc=cip-dev@lists.cip-project.org \
--cc=kazuhiro3.hayashi@toshiba.co.jp \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rt-devel@lists.linux.dev \
--cc=linux-rt-users@vger.kernel.org \
--cc=rostedt@goodmis.org \
--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
all inboxes | Powered by JetHome®