| commit | f3d73707a1e84f0687a05144b70b660441e999c7 | |
| author | Arjan van de Ven <arjan@linux.intel.com> | |
| Thu, 7 Dec 2006 01:14:12 +0000 (7 02:14 +0100) | ||
| committer | Andi Kleen <andi@basil.nowhere.org> | |
| Thu, 7 Dec 2006 01:14:12 +0000 (7 02:14 +0100) | ||
| tree | d95d69b985cd8cd3f99a74350e99f7ef83b8f9b3 | treesnapshot (tar.gz zip) |
| parent | e496a0da7f8110054d0ad4039245b0f49f9540f5 | commitdiff |
[PATCH] x86-64: Mark rdtsc as sync only for netburst, not for core2
On the Core2 cpus, the rdtsc instruction is not serializing (as defined
in the architecture reference since rdtsc exists) and due to the deep
speculation of these cores, it's possible that you can observe time go
backwards between cores due to this speculation. Since the kernel
already deals with this with the SYNC_RDTSC flag, the solution is
simple, only assume that the instruction is serializing on family 15...
The price one pays for this is a slightly slower gettimeofday (by a
dozen or two cycles), but that increase is quite small to pay for a
really-going-forward tsc counter.
Signed-off-by: Arjan van de Ven <arjan@linux.intel.com>
Signed-off-by: Andi Kleen <ak@suse.de>
On the Core2 cpus, the rdtsc instruction is not serializing (as defined
in the architecture reference since rdtsc exists) and due to the deep
speculation of these cores, it's possible that you can observe time go
backwards between cores due to this speculation. Since the kernel
already deals with this with the SYNC_RDTSC flag, the solution is
simple, only assume that the instruction is serializing on family 15...
The price one pays for this is a slightly slower gettimeofday (by a
dozen or two cycles), but that increase is quite small to pay for a
really-going-forward tsc counter.
Signed-off-by: Arjan van de Ven <arjan@linux.intel.com>
Signed-off-by: Andi Kleen <ak@suse.de>
| arch/x86_64/kernel/setup.c | diffblobblamehistory |