I'm a bit confused, maybe someone can clarify this.
At https://lkml.org/lkml/2011/3/25/54 it is mentioned that there still exists a underlying bug with kvmclock. I assume that this is not fixed in 2.6.38-11.50. Is it fixed in newer kernels? I assume that older kernels (like the one in lucid) are probably also affected by this underlying bug?
I'm a bit confused, maybe someone can clarify this.
At https:/ /lkml.org/ lkml/2011/ 3/25/54 it is mentioned that there still exists a underlying bug with kvmclock. I assume that this is not fixed in 2.6.38-11.50. Is it fixed in newer kernels? I assume that older kernels (like the one in lucid) are probably also affected by this underlying bug?