Re: [RT] read_tsc: ACK! TSC went backward! Unsynced TSCs?
From: Andi Kleen (ak_at_suse.de)
Date: 11/29/05
- Previous message: Stephen Frost: "Re: Linux 2.6.15-rc3"
- In reply to: thockin_at_hockin.org: "Re: [RT] read_tsc: ACK! TSC went backward! Unsynced TSCs?"
- Next in thread: Dave Jones: "Re: [RT] read_tsc: ACK! TSC went backward! Unsynced TSCs?"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Date: Tue, 29 Nov 2005 17:48:58 +0100 To: thockin@hockin.org
On Tue, Nov 29, 2005 at 08:52:19AM -0800, thockin@hockin.org wrote:
> On Tue, Nov 29, 2005 at 07:06:24AM -0700, Andi Kleen wrote:
> > But I'm surprised you're saying 2.6.11 broke. At least 2.6.11 64bit should
> > have always used HPET in this case. I only broke it around 2.6.13
> > where I added an overeager optimization for single socket DC on my side based
> > on a misunderstanding. Earlier and later kernels should have been ok.
>
> we didn't have HPET enabled in BIOS until recently. Turning that on made
> all the TSC gettimeofday() crap disappear. Now to find and kill any
> straggling users of rdtsc
The newer kernels work around this too by using pmtimer when needed.
Of course it's slow.
Regarding straggling users of rdtsc - one way would be to optionally
trap them and log them in the kernel. That would work in ring 3 at least.
-Andi
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
- Previous message: Stephen Frost: "Re: Linux 2.6.15-rc3"
- In reply to: thockin_at_hockin.org: "Re: [RT] read_tsc: ACK! TSC went backward! Unsynced TSCs?"
- Next in thread: Dave Jones: "Re: [RT] read_tsc: ACK! TSC went backward! Unsynced TSCs?"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Relevant Pages
|
|