Date: Mon, 4 Jun 2007 21:40:38 +0200
From: Ingo Molnar <mingo@elte.hu>
To: Matt Mackall <mpm@selenic.com>
Cc: Rusty Russell <rusty@rustcorp.com.au>, akpm@linux-foundation.org,
       Linux-kernel@vger.kernel.org
Subject: Re: Interesting interaction between lguest and CFS
Message-ID: <20070604194038.GA15782@elte.hu>
References: <20070604173710.GR11166@waste.org> <20070604181151.GA1745@elte.hu> <20070604184224.GH11115@waste.org> <20070604191229.GA12444@elte.hu> <20070604192755.GI11115@waste.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20070604192755.GI11115@waste.org>
User-Agent: Mutt/1.5.14 (2007-02-12)
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 831
Lines: 22


* Matt Mackall <mpm@selenic.com> 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 majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/