All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mike Galbraith <efault@gmx.de>
To: Gene Heskett <gene.heskett@gmail.com>
Cc: Jordi Pujol <jordipujolp@gmail.com>, LKML <linux-kernel@vger.kernel.org>
Subject: Re: Galbraith patch
Date: Fri, 19 Nov 2010 09:21:08 -0700	[thread overview]
Message-ID: <1290183668.24581.16.camel@maggy.simson.net> (raw)
In-Reply-To: <201011191005.12189.gene.heskett@gmail.com>

On Fri, 2010-11-19 at 10:05 -0500, Gene Heskett wrote:
> On Friday, November 19, 2010, Jordi Pujol wrote:
> >Hello,
> >
> >it requires a little modification,
> >
> >CONFIG_SCHED_DEBUG should not be a condition to create autogroup in
> >structure task_group
> >
> >remove
> >    && defined(CONFIG_SCHED_DEBUG)
> >in the following conditional:
> >
> >+++ linux-2.6.36/kernel/sched.c
> >@@ -78,6 +78,7 @@
> >
> > #include "sched_cpupri.h"
> > #include "workqueue_sched.h"
> >+#include "sched_autogroup.h"
> >
> > #define CREATE_TRACE_POINTS
> > #include <trace/events/sched.h>
> >@@ -268,6 +269,10 @@ struct task_group {
> > 	struct task_group *parent;
> > 	struct list_head siblings;
> > 	struct list_head children;
> >+
> >+#if (defined(CONFIG_SCHED_AUTOGROUP) && defined(CONFIG_SCHED_DEBUG))
> >+	struct autogroup *autogroup;
> >+#endif
> > };
> >
> >Kind,
> >
> >Jordi Pujol
> 
> Thanks Jordi, but my last attempted build, using only the last 2 patches 
> that Mike posted on a fresh unpack of 2.6.36, couldn't get past stage 2 of 
> the modules build, it kept squawking about all the IR control stuff that is 
> not even configured to be built.

No idea what's going on with that.  Maybe you should wait until I get
the /proc display/tweak interface cobbled together and post a checked
over patch instead of hasty WIP snapshot.

> I wonder how long it will take to get work this into mainline?

If it goes in at all, it won't be before .38.

> Along the same line, how does this compare to CK's bfs patch?

Like apple vs orange.

	-Mike


  reply	other threads:[~2010-11-19 16:21 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-11-17 18:35 Galbraith patch Gilberto Nunes
2010-11-17 18:58 ` Dhaval Giani
2010-11-17 18:59   ` Dhaval Giani
2010-11-17 19:00   ` Dhaval Giani
2010-11-17 19:22     ` Gilberto Nunes
     [not found]     ` <1290021497.4887.24.camel@note-311a>
2010-11-17 23:21       ` Mike Galbraith
2010-11-17 23:36         ` Gilberto Nunes
2010-11-18 15:43         ` Gilberto Nunes
2010-11-18 16:06           ` Mike Galbraith
2010-11-18 16:40             ` Gilberto Nunes
2010-11-18 18:40             ` Thomas Backlund
2010-11-18 19:35               ` Gene Heskett
2010-11-18 20:10                 ` Mike Galbraith
2010-11-18 21:29                   ` Gene Heskett
2010-11-18 20:00               ` Mike Galbraith
2010-11-18 21:16                 ` Thomas Backlund
2010-11-18 21:36                   ` Gene Heskett
2010-11-18 21:28                 ` Gene Heskett
2010-11-18 22:29                   ` Thomas Backlund
2010-11-19 14:09                   ` Jordi Pujol
2010-11-19 15:05                     ` Gene Heskett
2010-11-19 16:21                       ` Mike Galbraith [this message]
2010-11-20  0:05                         ` Gene Heskett
2010-11-19 16:49                       ` Jordi Pujol
2010-11-19 17:11                         ` Gilberto Nunes
2010-11-19 16:09                     ` Mike Galbraith
2010-11-18 19:32             ` Gene Heskett

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=1290183668.24581.16.camel@maggy.simson.net \
    --to=efault@gmx.de \
    --cc=gene.heskett@gmail.com \
    --cc=jordipujolp@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    /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.