|Subject:||Re: [Qemu-devel] QEMU/MIPS & dyntick kernel|
|From:||Avi Kivity <email@example.com>|
|Date:||Tue, 02 Oct 2007 22:27:07 +0200|
|User-agent:||Thunderbird 126.96.36.199 (X11/20070727)|
Aurelien Jarno wrote:
Hi, As announced by Ralf Baechle, dyntick is now available on MIPS. I gave a try on QEMU/MIPS, and unfortunately it doesn't work correctly.In some cases the kernel schedules an event very near in the future, which means the timer is scheduled a few cycles only from its currentvalue. Unfortunately under QEMU, the timer runs too fast compared to the speed at which instructions are execution.
Sounds like a kernel bug. Can't there conceivably exist real hardware (or a real timeout) that exhibits the same timing?
Especially today with variable clock frequencies, I don't see how the kernel can rely on exact timing.
-- Any sufficiently difficult bug is indistinguishable from a feature.
|<Prev in Thread]||Current Thread||[Next in Thread>|
|Previous by Date:||Re: [PATCH][2/4] move Cobalt UART base definition to arch/mips/cobalt/console.c, Ralf Baechle|
|Next by Date:||Re: [Qemu-devel] QEMU/MIPS & dyntick kernel, Aurelien Jarno|
|Previous by Thread:||QEMU/MIPS & dyntick kernel, Aurelien Jarno|
|Next by Thread:||Re: [Qemu-devel] QEMU/MIPS & dyntick kernel, Aurelien Jarno|
|Indexes:||[Date] [Thread] [Top] [All Lists]|