On Sun, 2006-10-08 at 23:38 +0200, Thomas Gleixner wrote: > > I don't see that behaviour on my machines and nobody complains about > that. I don't care about stale comments. Point me to a bug report > instead of your perception of what's optimal and not. Let both do this. Lets discuss empirical behavior. Otherwise we aren't making any progress. > Working is not necessary optimal, but your vision of optimal is not > necessarily working either. I'm looking for the TSC issue you mentioned.. I tested it as best I could, so I need more information to say it's not working. Daniel - 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:
- Re: + clocksource-increase-initcall-priority.patch added to -mm tree
- From: Thomas Gleixner <[email protected]>
- Re: + clocksource-increase-initcall-priority.patch added to -mm tree
- References:
- Re: + clocksource-increase-initcall-priority.patch added to -mm tree
- From: Thomas Gleixner <[email protected]>
- Re: + clocksource-increase-initcall-priority.patch added to -mm tree
- From: Thomas Gleixner <[email protected]>
- Re: + clocksource-increase-initcall-priority.patch added to -mm tree
- From: Daniel Walker <[email protected]>
- Re: + clocksource-increase-initcall-priority.patch added to -mm tree
- From: Thomas Gleixner <[email protected]>
- Re: + clocksource-increase-initcall-priority.patch added to -mm tree
- From: Daniel Walker <[email protected]>
- Re: + clocksource-increase-initcall-priority.patch added to -mm tree
- From: Thomas Gleixner <[email protected]>
- Re: + clocksource-increase-initcall-priority.patch added to -mm tree
- From: Daniel Walker <[email protected]>
- Re: + clocksource-increase-initcall-priority.patch added to -mm tree
- From: Thomas Gleixner <[email protected]>
- Re: + clocksource-increase-initcall-priority.patch added to -mm tree
- From: Daniel Walker <[email protected]>
- Re: + clocksource-increase-initcall-priority.patch added to -mm tree
- From: Thomas Gleixner <[email protected]>
- Re: + clocksource-increase-initcall-priority.patch added to -mm tree
- From: Daniel Walker <[email protected]>
- Re: + clocksource-increase-initcall-priority.patch added to -mm tree
- From: Thomas Gleixner <[email protected]>
- Re: + clocksource-increase-initcall-priority.patch added to -mm tree
- From: Daniel Walker <[email protected]>
- Re: + clocksource-increase-initcall-priority.patch added to -mm tree
- From: Thomas Gleixner <[email protected]>
- Re: + clocksource-increase-initcall-priority.patch added to -mm tree
- From: Daniel Walker <[email protected]>
- Re: + clocksource-increase-initcall-priority.patch added to -mm tree
- From: Thomas Gleixner <[email protected]>
- Re: + clocksource-increase-initcall-priority.patch added to -mm tree
- Prev by Date: Re: + clocksource-add-generic-sched_clock.patch added to -mm tree
- Next by Date: drivers/char/specialix.c: broken baud conversion
- Previous by thread: Re: + clocksource-increase-initcall-priority.patch added to -mm tree
- Next by thread: Re: + clocksource-increase-initcall-priority.patch added to -mm tree
- Index(es):