> > [ CC Ben from Debian kernel-team ] > > > > Hi Paul, > > > > Thanks for the feedback. > > > > Right now, I installed latest Debian-5.19 kernel to compare the Kconfig values: > > > > [ Debian ] > > $ grep RCU /boot/config-5.19.0-trunk-amd64 | grep -i stall > > CONFIG_RCU_STALL_COMMON=y > > CONFIG_RCU_CPU_STALL_TIMEOUT=21 > > CONFIG_RCU_EXP_CPU_STALL_TIMEOUT=20 > > > > [ Sedat ] > > $ grep RCU /boot/config-5.19.0-2-amd64-clang15-kcfi | grep -i stall > > CONFIG_RCU_STALL_COMMON=y > > CONFIG_RCU_CPU_STALL_TIMEOUT=21 > > CONFIG_RCU_EXP_CPU_STALL_TIMEOUT=20 > > > > My custom kernels take Debian's latest as a base and I adapt it to my needs. > > > > Just checking the Kconfigs... > > > > [ CONFIG_RCU_CPU_STALL_TIMEOUT ] > > > > Help text > > If a given RCU grace period extends more than the specified ***number > > of seconds***, a CPU stall warning is printed. If the RCU grace period > > persists, additional CPU stall warnings are printed at more widely > > spaced intervals. > > > > https://cateee.net/lkddb/web-lkddb/RCU_CPU_STALL_TIMEOUT.html > > > > [ CONFIG_RCU_EXP_CPU_STALL_TIMEOUT ] > > > > Help text > > If a given expedited RCU grace period extends more than the specified > > ***number of milliseconds***, a CPU stall warning is printed. If the > > RCU grace period persists, additional CPU stall warnings are printed > > at more widely spaced intervals. A value of zero says to use the > > RCU_CPU_STALL_TIMEOUT value converted from seconds to milliseconds. > > > > https://cateee.net/lkddb/web-lkddb/RCU_EXP_CPU_STALL_TIMEOUT.html > > > > Conclusion: > > > > CONFIG_RCU_CPU_STALL_TIMEOUT=21 <--- XXX: value in seconds - 21 seconds > > CONFIG_RCU_EXP_CPU_STALL_TIMEOUT=21000 <--- XXX: value in milliseconds > > - 21 x 1000 = 21seconds > > > > ...to match the values are identical? > > > > Or as the CONFIG_RCU_EXP_CPU_STALL_TIMEOUT help-text recommends: > > > > "A value of zero says to use the RCU_CPU_STALL_TIMEOUT value converted > > from seconds to milliseconds." > > > > I will try with my next 5.19 kernel build. > > Good point, zero is the better choice, as it accommodates changes in > the value of CONFIG_RCU_CPU_STALL_TIMEOUT. > > Thanx, Paul I build with... [ diffconfig ] RCU_EXP_CPU_STALL_TIMEOUT 20 -> 21000 ...will observe RCU CPU stallings. Next build I try... CONFIG_RCU_EXP_CPU_STALL_TIMEOUT=0 -Sedat-
