On Mon, 16 May 2005, john stultz wrote: > Since its possible to do jitter compensation within the itc timesource > driver (and within the fastcall code to preserve the existing > performance), would it be reasonable to deffer making the jitter > compensation code generic until another timesource needs it? It should > be a fairly simple change. Well looks that we will start out with the new time subsystem by putting some hacks in. I need to check in the funky routine (for setting up the fastcall configuration) if the function pointer passed == jitter-compensated-itc and depending on that set a special flag that makes the asm code do jitter compensation. > Or is this just something I'm being hard-headed about? Looks like it. Its not that difficult. Add a jitter compensation flag to timesource. Check on retrieving from a timesource if its less than last if flag is set. Pass the field to the funky function to setup the vsyscalls. Maybe add a general flags field? There may be other things that need to be added in the future. - 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/
- References:
- [RFC][PATCH (1/7)] new timeofday subsystem (v A5)
- From: john stultz <[email protected]>
- [RFC][PATCH (2/7)] new timeofday i386 arch specific changes (v A5)
- From: john stultz <[email protected]>
- [RFC][PATCH (3/7)] new timeofday x86-64 specific changes (v A5)
- From: john stultz <[email protected]>
- [RFC][PATCH (4/7)] new timeofday i386 and x86-64 timesources (v A5)
- From: john stultz <[email protected]>
- [RFC][PATCH (5/7)] new timeofday ia64,ppc32,ppc64 and s390 arch specific hooks (v A5)
- From: john stultz <[email protected]>
- IA64 implementation of timesource for new time of day subsystem
- From: Christoph Lameter <[email protected]>
- Re: IA64 implementation of timesource for new time of day subsystem
- From: john stultz <[email protected]>
- Re: IA64 implementation of timesource for new time of day subsystem
- From: Christoph Lameter <[email protected]>
- Re: IA64 implementation of timesource for new time of day subsystem
- From: john stultz <[email protected]>
- Re: IA64 implementation of timesource for new time of day subsystem
- From: Christoph Lameter <[email protected]>
- Re: IA64 implementation of timesource for new time of day subsystem
- From: David Mosberger <[email protected]>
- Re: IA64 implementation of timesource for new time of day subsystem
- From: john stultz <[email protected]>
- Re: IA64 implementation of timesource for new time of day subsystem
- From: Christoph Lameter <[email protected]>
- Re: IA64 implementation of timesource for new time of day subsystem
- From: john stultz <[email protected]>
- Re: IA64 implementation of timesource for new time of day subsystem
- From: David Mosberger <[email protected]>
- Re: IA64 implementation of timesource for new time of day subsystem
- From: john stultz <[email protected]>
- [RFC][PATCH (1/7)] new timeofday subsystem (v A5)
- Prev by Date: Re: ext2 optimal partition size
- Next by Date: Re: NUMA aware slab allocator V3
- Previous by thread: Re: IA64 implementation of timesource for new time of day subsystem
- Next by thread: Re: IA64 implementation of timesource for new time of day subsystem
- Index(es):