Incorrect CPU process accounting using CONFIG_HZ=100

[Al Boldi]

Setting CONFIG_HZ=100 results in incorrect CPU process accounting.

This can be seen running top d.1, that shows top, itself, consuming 0ms 
CPUtime.

Will this bug have consequences for sched.c?

Thanks!

--
Al

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/