(In reply to comment #13)
> 2.6.33 doesn't support vblank events, so you wouldn't be able to run the code
> that exposes this problem. I'm sure the interrupt issue still exists on 2.6.33
> though, you just don't see it because you're not running code that's sensitive
> to interrupt latency.
Please, excuse in advance my ignorance and probably the stupid question, but what are the advantages (if any) on running that code?
I'm asking because i didn't noticed any performance or tearing difference with 2.6.35+processor.max_cstate=1 compared to 2.6.33.
(In reply to comment #13)
> 2.6.33 doesn't support vblank events, so you wouldn't be able to run the code
> that exposes this problem. I'm sure the interrupt issue still exists on 2.6.33
> though, you just don't see it because you're not running code that's sensitive
> to interrupt latency.
Please, excuse in advance my ignorance and probably the stupid question, but what are the advantages (if any) on running that code? processor. max_cstate= 1 compared to 2.6.33.
I'm asking because i didn't noticed any performance or tearing difference with 2.6.35+