Incorrect CPU process accounting using CONFIG_HZ=100

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 [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

---

• Follow-Ups:
  • Re: Incorrect CPU process accounting using CONFIG_HZ=100
    • From: Jan Engelhardt <[email protected]>

• Prev by Date: Re: [PATCH 2.6.17-rc6-mm2] Fix exit race in per-task-delay-accounting
• Next by Date: [Patch] Dereference in tokenring/olympic.c
• Previous by thread: CONFIG_VGACON_SOFT_SCROLLBACK crashes 2.6.17
• Next by thread: Re: Incorrect CPU process accounting using CONFIG_HZ=100
• Index(es):
  • Date
  • Thread

[Index of Archives]     [Kernel Newbies]     [Netfilter]     [Bugtraq]     [Photo]     [Stuff]     [Gimp]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Video 4 Linux]     [Linux for the blind]     [Linux Resources]