* Ingo Molnar <[email protected]> wrote:
> * William Weston <[email protected]> wrote:
>
> > Attached are two typical traces and the .config from my Xeon/HT box,
> > currently running -50-06 with a normal desktop workload (X, wmaker,
> > ten dockapps, several xterms, and firefox).
>
> the second trace seems to be a cross-CPU wakeup bug. It's not
> completely clear from the trace what happened - but we measured the
> latency of a task (wmcube-3191), where the wakeup happened on CPU#0
> and wmcube-3191 was queued to CPU#1 which was idle at that time. The
> bug is that it wasnt until timestamp 306us that this actually happened
> - and CPU#1 was just idling around in default_idle() for no good
> reason. CPU#1 should have run wmcube-3191 at around timestamp 13us.
ok, managed to reproduce it on a HT box, and it turned out to be a bug
in the SMT scheduler: the dependent sleeper logic incorrectly delayed
high-prio tasks, causing these latencies. I fixed it in the -50-10
kernel - could you redo your tests with that kernel (or later versions)?
Ingo
-
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]