Messages in this thread |  | | | Date | Thu, 19 Jul 2007 18:16:43 +0200 | | From | Ingo Molnar <> | | Subject | Re: [patch] sched: implement cpu_clock(cpu) high-speed time source, take #2 |
| |
* Jeremy Fitzhardinge <jeremy@goop.org> wrote:
> > how about the patch below instead? (which, unlike the first one, > > happens to build and boot ;-) > > Yes, that should be fine if its just based on sched_clock. Presumably > that means that any architecture (eg, s390) which chooses to implement > sched_clock as unstolen time will get good behaviour from softlockup > as well as the scheduler.
yeah, that's the idea.
> How does this interact with the sched_clock changes Andi just posted?
those changes pose no problem, and they are largely orthogonal. Andi's changes should improve the quality of sched_clock() on some boxes that encounter a cpu frequency transition that makes the TSC readout unreliable.
Ingo - 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/
|  |