Maybe it works already somehow with some config - but it happens when some task is running in LP mode - lets say xz decompression, which takes 1 core. It is not enough to make a high load system-wise so it just comtinue running on LP core utilizing it 100% and pushing it to freq. limit. So it would be a nice improvement if such tasks that occupies 1 core with 100% load to be migrated to a certain P-core so it will run faster. Not to activate all P-cores and let the small tasks to start eating battery, but just migrate the heavy task there.
Another suggestion - make the app. list to push certain apps (lets say the xz mentioned aleady or gcc or llvm) to use different cpu affinity than the other ones.
Just some ideas of an improvement....
Maybe it works already somehow with some config - but it happens when some task is running in LP mode - lets say xz decompression, which takes 1 core. It is not enough to make a high load system-wise so it just comtinue running on LP core utilizing it 100% and pushing it to freq. limit. So it would be a nice improvement if such tasks that occupies 1 core with 100% load to be migrated to a certain P-core so it will run faster. Not to activate all P-cores and let the small tasks to start eating battery, but just migrate the heavy task there.
Another suggestion - make the app. list to push certain apps (lets say the xz mentioned aleady or gcc or llvm) to use different cpu affinity than the other ones.
Just some ideas of an improvement....