mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Sébastien Dugué" <sebastien.dugue@bull.net>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: Thomas Gleixner <tglx@linutronix.de>, Ingo Molnar <mingo@elte.hu>,
	linux-kernel <linux-kernel@vger.kernel.org>,
	Linux RT Users <linux-rt-users@vger.kernel.org>,
	Darren Hart <dvhltc@us.ibm.com>,
	john stultz <johnstul@us.ibm.com>,
	Jean Pierre Dion <jean-pierre.dion@bull.net>,
	Gilles Carry <Gilles.Carry@ext.bull.net>
Subject: Re: [Patch RT] Fix CFS load balancing for RT tasks
Date: Thu, 12 Jul 2007 08:56:53 +0200	[thread overview]
Message-ID: <20070712085653.0bb0064d@frecb000686.frec.bull.fr> (raw)
In-Reply-To: <Pine.LNX.4.58.0707111341190.18766@gandalf.stny.rr.com>

On Wed, 11 Jul 2007 13:41:55 -0400 (EDT) Steven Rostedt <rostedt@goodmis.org> wrote:

> > On Wed, 2007-07-11 at 16:47 +0200, Sébastien Dugué wrote:
> > >
> > >   P.S. Thanks to Steven Rostedt for logdev which is proving invaluable in
> > >        cases like this.
> > >
> 
> Great to hear!!!
> 
> I'll be uploading a new version of Logdev in a week or so.
> 
> Thanks for the feedback.
> 
> -- Steve
> 

  Great! It's quite a nice and lightweight tool which I think will become
one of my top tools for kernel debugging.

  Just one suggestion, maybe, would be to add to the readme file the
order in which the patches should apply along with a short description
of what functionality they provide (or maybe document the patches and add a
series file).

  Anyway, thanks for that great tool.

  Sébastien.

  reply	other threads:[~2007-07-12  6:59 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-07-11 14:47 Sébastien Dugué
2007-07-11 17:06 ` Thomas Gleixner
2007-07-11 17:41   ` Steven Rostedt
2007-07-12  6:56     ` Sébastien Dugué [this message]
2007-07-12  6:28   ` Sébastien Dugué
2007-07-12 16:41 ` Josh Triplett
2007-07-12 17:13   ` Josh Triplett
2007-07-13  7:01     ` Sébastien Dugué
2007-07-13  6:54   ` Sébastien Dugué

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=20070712085653.0bb0064d@frecb000686.frec.bull.fr \
    --to=sebastien.dugue@bull.net \
    --cc=Gilles.Carry@ext.bull.net \
    --cc=dvhltc@us.ibm.com \
    --cc=jean-pierre.dion@bull.net \
    --cc=johnstul@us.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-rt-users@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=rostedt@goodmis.org \
    --cc=tglx@linutronix.de \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®