ChanServ changed the topic of #linux-msm to:
jn has joined #linux-msm
jnn has quit [Ping timeout: 480 seconds]
marvin24_ has joined #linux-msm
marvin24 has quit [Ping timeout: 480 seconds]
junari has joined #linux-msm
junari has quit [Ping timeout: 480 seconds]
<strongtz[m]> I have a feeling that there are severe performance issues in recent -next tree :(
<strongtz[m]> performance just got worse from next-20231129 to next-20240102, then to next-20240313
<strongtz[m]> on next-20240313 some heavy tasks (such as 7zip benchmark) will always be assigned to A510 cores sometimes, leaving the a710/a715 cores idle
<strongtz[m]> and without entirely disabling cpuidle, I even experience Watchdog detected hard LOCKUP with the device acting as a furnace
<strongtz[m]> but ofc it's probably not an issue with msm drivers, and not much people care about performance I guess
kralya[m] has joined #linux-msm
<aka_[m]> lumag: should clocks be ordered by clock-names in alphabetical order?
kralya[m] has quit [autokilled: Spambot. Mail support@oftc.net if you think this is in error. (2024-03-17 20:38:00)]
telent has quit [Quit: Ping timeout (120 seconds)]
telent has joined #linux-msm