* Matt Mackall <[EMAIL PROTECTED]> wrote:
> > ah, so both the shell and the 'competing' CPU hog was running within
> > the same lguest instance?
>
> No.
>
> The CPU hog is running in the host. A single instance of lguest using
> busybox is started in another shell. When it reaches a shell prompt,
> -that- shell is occassionally unresponsive for long stretches.
so the shell within lguest is affected by the CPU hog outside? Could you
send me the sched-debug stats of the CPU hog and of the lguest host
process as well? (or were those amongst the ones you already sent?)
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/
