All of lore.kernel.org
 help / color / mirror / Atom feed
From: Matt Mackall <mpm@selenic.com>
To: Ingo Molnar <mingo@elte.hu>
Cc: Rusty Russell <rusty@rustcorp.com.au>,
	akpm@linux-foundation.org, Linux-kernel@vger.kernel.org
Subject: Re: Interesting interaction between lguest and CFS
Date: Mon, 4 Jun 2007 14:59:51 -0500	[thread overview]
Message-ID: <20070604195951.GJ11115@waste.org> (raw)
In-Reply-To: <20070604194038.GA15782@elte.hu>

On Mon, Jun 04, 2007 at 09:40:38PM +0200, Ingo Molnar wrote:
> 
> * 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?)

I sent you the stats for:

- both lguest processes
- the bash which started lguest (which I suspect you don't actually
  want)
- the gnome-terminal that lguest was running inside of
  (keystrokes to the shell in lguest go through that terminal)

The last is probably not very interesting either, as gnome-terminal is
a single process with multiple windows and none of the other windows
were affected.

So I sent you everything but the stats for the CPU hog.

I suggest you try this yourself - lguest is incredibly easy to get up
and running. It's also quite useful: I can test-boot kernels with it
in less than a second, or about 10x faster than basic qemu, and 100x
faster than a real boot. And as it uses a pty as console, you can do
things like pipe it through grep.

You'll need the following tab-damaged patch for rc3-mm1:

--- mm.orig/arch/i386/kernel/sched-clock.c      2007-06-04 12:15:51.000000000 -0500
+++ mm/arch/i386/kernel/sched-clock.c   2007-06-04 12:15:57.000000000
-0500
@@ -133,7 +133,7 @@ static void resync_freq(void *arg)
        struct sc_data *sc = &__get_cpu_var(sc_data);
 
        sc->sync_base = jiffies;
-       if (!cpu_has_tsc) {
+       if (!cpu_has_tsc || tsc_disable) {
                sc->unstable = 1;
                return;
        }

-- 
Mathematics is the supreme nostalgia of our time.

  reply	other threads:[~2007-06-04 20:00 UTC|newest]

Thread overview: 38+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-06-04 17:37 Interesting interaction between lguest and CFS Matt Mackall
2007-06-04 17:54 ` Ingo Molnar
2007-06-04 18:41   ` Matt Mackall
2007-06-05  7:19     ` Ingo Molnar
2007-06-05 14:03       ` Matt Mackall
2007-06-05 15:14         ` Dmitry Adamushko
2007-06-05 15:41           ` Dmitry Adamushko
2007-06-05 19:50             ` Ingo Molnar
2007-06-06 20:23               ` Matt Mackall
2007-06-08  9:34                 ` Ingo Molnar
2007-06-08 10:18                   ` Ingo Molnar
2007-06-04 18:11 ` Ingo Molnar
2007-06-04 18:42   ` Matt Mackall
2007-06-04 19:12     ` Ingo Molnar
2007-06-04 19:27       ` Matt Mackall
2007-06-04 19:40         ` Ingo Molnar
2007-06-04 19:59           ` Matt Mackall [this message]
2007-06-04 20:13             ` Ingo Molnar
2007-06-04 20:20               ` Ingo Molnar
2007-06-04 20:15   ` James Morris
2007-06-04 20:24     ` Ingo Molnar
2007-06-04 22:58 ` Olof Johansson
2007-06-05  1:02   ` Rusty Russell
2007-06-05  1:24     ` Stephen Rothwell
2007-06-05  2:23     ` Olof Johansson
2007-06-05  0:18 ` Rusty Russell
2007-06-05  2:31   ` Rusty Russell
2007-06-05  4:18     ` Matt Mackall
2007-06-05  4:37       ` Rusty Russell
2007-06-05 13:49         ` Matt Mackall
2007-06-05 19:38           ` Ingo Molnar
2007-06-05 10:43       ` Ingo Molnar
2007-06-05 19:08         ` Ingo Molnar
2007-06-06 20:19           ` Matt Mackall
2007-06-05  2:34   ` Matt Mackall
2007-06-05  7:10   ` Ingo Molnar
2007-06-05  9:23 ` Ingo Molnar
2007-06-05 14:06   ` Matt Mackall

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20070604195951.GJ11115@waste.org \
    --to=mpm@selenic.com \
    --cc=Linux-kernel@vger.kernel.org \
    --cc=akpm@linux-foundation.org \
    --cc=mingo@elte.hu \
    --cc=rusty@rustcorp.com.au \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.