Skip to contentSkip to conversation

Actions for fixing repeated unpin_current_cpu() WARNING

4.4.y-cip-rt [email protected] 1 participant 1 message Mar 17, 2025 1 message not in the archive

lore
Share & tools
lore

A message that is not in the archive (sent off-list or not yet received): [email protected]

#1 lore raw

Hello Pavel,

Sorry to bother you, but I'd like to know your plan about how to apply the patches[2]. (i.e. about the following questions)

Quoted 3 lines

Do we need to apply the patch to introduce "system_scheduling"[4] to 4.4.y-cip (non RT) first? [...]
Should it be applied to 4.4.y-cip-rt only?

It seems the next 4.4.y-cip & -rt release is planned in April. It's great if the patches can be included in the next release.

Best regards,
Kazu

Quoted 36 lines

Hello Ulrich, Pavel,

Pavel and I have been discussing how we can fix the issue [1] that unpin_current_cpu() WARNING occurs repeatedly while kernel booting. This issue happens with 4.4.y-cip-rt (In RT kernel, v4.9-rt or older) and not with 4.19.y-cip-rt or newer.

I created two patch series[2][3] (two different solutions for resolving [1]), then they were shared in linux-rt-devel lists for review.
The both were acknowledged "as OK" there.
Pavel selected the shorter patch series[2] and we want to apply it to 4.4 CIP tree.

Here are requests from my side:

To Ulrich,
Could you review the patch series [2] ?
Details of the issue and how each patch is made and work are written in commit messages. The WARNING has not occurred in 20,000 reboots in both cases[2][3].
Feel free to ask questions, request to improve patches, etc.

To Pavel,
Do we need to apply the patch to introduce "system_scheduling"[4] to 4.4.y-cip (non RT) first? Its original implementation (i.e. SYSTEM_SCHEDULING introduction) happened in the mainline, but our custom patch[4] does not make any sense for 4.4.y-cip.
Should it be applied to 4.4.y-cip-rt only?
The second patch to fix the issue[5] must be applied to 4.4.y-cip-rt only because the original change was made in v4.14-rt branch and not in mainline.

[1] https://lists.cip-project.org/g/cip-dev/topic/108515524
[2] https://lore.kernel.org/linux-rt-devel/1738629964-11977-1-git-send-email-kazuhiro3.hayashi@toshiba.co.jp/T/
[3] https://lore.kernel.org/linux-rt-devel/1739170545-25011-1-git-send-email-kazuhiro3.hayashi@toshiba.co.jp/T/
[4] https://lore.kernel.org/linux-rt-devel/1738629964-11977-2-git-send-email-kazuhiro3.hayashi@toshiba.co.jp/
[5] https://lore.kernel.org/linux-rt-devel/1738629964-11977-3-git-send-email-kazuhiro3.hayashi@toshiba.co.jp/

Best regards,
Kazu