Today i tried with 2.6.36, and obviously the results are the same, so i'm still using 2.6.33.
For me disabling a core or the hyperthreading is not an option due to the higher power consumption and the shorter battery life.
If i understood properly, the issue still appears to be unresolved and the hypothesis made doesn't seems to be able to make anything really useful.
I understood thet the new code is looking forward to provide a "gain" in performance, but now my proposal is to do some kind of workaround for the specific chipsets that expose the problem so that at least their users will be able to upgrade to newer kernels without suffernig any performance "loss".
Could such a thing be done in the video driver itself or does it requires patches or special config options of the kernel (?).
Today i tried with 2.6.36, and obviously the results are the same, so i'm still using 2.6.33.
For me disabling a core or the hyperthreading is not an option due to the higher power consumption and the shorter battery life.
If i understood properly, the issue still appears to be unresolved and the hypothesis made doesn't seems to be able to make anything really useful.
I understood thet the new code is looking forward to provide a "gain" in performance, but now my proposal is to do some kind of workaround for the specific chipsets that expose the problem so that at least their users will be able to upgrade to newer kernels without suffernig any performance "loss".
Could such a thing be done in the video driver itself or does it requires patches or special config options of the kernel (?).