Badari Pulavarty <[email protected]> wrote:
>
> > You probably covered this, but just to make sure, if you're on a
> > pentium4 machine, I usually boot w/ "idle=poll" to see proper idle
> > reporting because otherwise the chip will throttle itself back and
> > idle time will be skewed -- at least on oprofile.
> >
>
> My machine is AMD64.
I'd expect the problem to which Sonny refers will occur on many
architectures.
IIRC, the problem is that many (or all) of the counters which oprofile uses
are turned off when the CPU does a halt. So the profiler ends up thinking
that zero time is spent in the idle handler. The net effect is that if
your workload spends 90% of its time idle then all the other profiler hits
are exaggerated by a factor of ten. Making the CPU busywait in idle()
fixes this.
But you're using the old /proc/profile profiler which uses a free-running
timer which doesn't get stopped by halt, so it is unaffected by this.
-
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/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
| |
 |