On Tuesday 06 February 2007 3:40 pm, Daniel Walker wrote:
quoted text
> 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.
> 
> The reason that I'm bringing it up at all is because people have ask me
> "Why isn't my timer ticking??"

Because there are two clock sources in the machine and it's using the other 
one, so the interrupt isn't firing?

Are you saying that the /proc statistics aren't accurate, or that you 
previously misunderstood what it was actually measuring and you'd now like it 
to lie?

quoted text
> > Uurg. /proc/interrupts has nothing to do with timers. It's interrupts
> > statistics. See LOC entry for the lapic ones.
> 
> Your saying we can't remove it tho, if /proc/interrupts is not related
> to timers why does the entry exist at all ?

I didn't think Thomas even touched the /proc/interrupts reporting code.  It's 
still accurate.  The patch changed the usage of timers, /proc/interrupts is 
accurately showing the change, and you're surprised that what it was 
measuring wasn't what you thought it was measuring all along.

This ain't jiffies.  This is how often the PIT fired.  They are not the same 
thing.

Rob
-- 
"Perfection is reached, not when there is no longer anything to add, but
when there is no longer anything to take away." - Antoine de Saint-Exupery
-
unsubscribe notice
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/