On Thu, 15 Nov 2007, Micah Dowty wrote:
> For reference, the exact test I used with git-bisect is attached. The
> C program (priosched) starts two busy-looping threads and a
> high-priority high-frequency thread which uses relatively little
> CPU. The Python program repeatedly starts the C program, runs it for a
> half second, and measures the resulting imbalance in CPU usage. On
> kernels prior to the above commit, this reports values within about
> 10% of 1.0. On later kernels, it crashes within a couple iterations
> due to a divide-by-zero error :)
The kernel crashes? Sounds like your application crashes with a divide by
zero?
-
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]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]