On Mon, Oct 10, 2005 at 08:19:42PM +0200, Jonas Oreland wrote: > Hi, > > check http://bugzilla.kernel.org/show_bug.cgi?id=5283 Excuse me for possibly dumb question, but is it safe to leave TSCs unsynchronized when using other time source? How will other subsystems e.g. traffic queueing disciplines react? ~ :wq With best regards, Vladimir Savkin. - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
- Follow-Ups:
- References:
- Re: [PATCH] x86-64: Fix bad assumption that dualcore cpus have synced TSCs
- From: "Vladimir B. Savkin" <[email protected]>
- Re: [PATCH] x86-64: Fix bad assumption that dualcore cpus have synced TSCs
- From: Andi Kleen <[email protected]>
- Re: [PATCH] x86-64: Fix bad assumption that dualcore cpus have synced TSCs
- From: "Vladimir B. Savkin" <[email protected]>
- Re: [PATCH] x86-64: Fix bad assumption that dualcore cpus have synced TSCs
- From: john stultz <[email protected]>
- Re: [PATCH] x86-64: Fix bad assumption that dualcore cpus have synced TSCs
- From: "Vladimir B. Savkin" <[email protected]>
- Re: [PATCH] x86-64: Fix bad assumption that dualcore cpus have synced TSCs
- From: Jonas Oreland <[email protected]>
- Re: [PATCH] x86-64: Fix bad assumption that dualcore cpus have synced TSCs
- Prev by Date: [PATCH] DECnet tidy
- Next by Date: Re: [PATCH] ktimers subsystem 2.6.14-rc2-kt5
- Previous by thread: Re: [PATCH] x86-64: Fix bad assumption that dualcore cpus have synced TSCs
- Next by thread: Re: [PATCH] x86-64: Fix bad assumption that dualcore cpus have synced TSCs
- Index(es):