Messages in this thread |  | | Date | Tue, 6 Feb 2007 21:52:31 +0100 | From | Ingo Molnar <> | Subject | Re: 2.6.20-rc6-mm3 |
| |
* Daniel Walker <dwalker@mvista.com> wrote:
> On Tue, 2007-02-06 at 21:20 +0100, Thomas Gleixner wrote: > > On Tue, 2007-02-06 at 11:55 -0800, Daniel Walker wrote: > > > > What kind of artificial problem are you creating here ? > > > > > > I'm not trying to create anything .. However, as I said before > > > the /proc/interrupts "timer" entry doesn't work the same as it has in > > > other kernels. > > > > Yes, it is different. Why are you insisting, that something is a problem > > just because it is different ? > > In this case "different" goes into userspace .. So different could > mean userspace regression, which is something that we don't want. I > have no idea if any apps use /proc/interrupts , but it's possible > since it's been around for a long time.
Well, if you enable dynticks you should expect the number of timer irqs to go down. There's no problem here.
> The reason that I'm bringing it up at all is because people have ask > me "Why isn't my timer ticking??"
it's quite easy to explain: because of the new dynticks feature. Both 'timer' and 'LOC' counts go way down.
> It might be nicer to list all the registered clock event sources in > /proc/interrupts, with more descriptive names ..
they are already listed in /proc/interrupts, depending on how they use interrupts. For a more complete list of in-use clockevent drivers see /proc/timer_info. But it would be wrong to touch /proc/interrupts to create some special-case for clockevents.
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/
|  |