From: Bharata B Rao <bharata@linux.vnet.ibm.com>
To: Yong Zhang <yong.zhang0@gmail.com>
Cc: linux-kernel@vger.kernel.org, Mike Galbraith <efault@gmx.de>,
Peter Zijlstra <a.p.zijlstra@chello.nl>,
Ingo Molnar <mingo@elte.hu>
Subject: Re: [PATCH -tip 1/2] sched: Reinstate group names in /proc/sched_debug.
Date: Tue, 11 Jan 2011 15:43:46 +0530 [thread overview]
Message-ID: <20110111101346.GG4772@in.ibm.com> (raw)
In-Reply-To: <AANLkTi=kEFcJ183xUCXGL=QqPLnOYBNtpQ=i5F9kTwK4@mail.gmail.com>
On Tue, Jan 11, 2011 at 09:53:05AM +0800, Yong Zhang wrote:
> On Mon, Jan 10, 2011 at 1:15 PM, Bharata B Rao
> <bharata@linux.vnet.ibm.com> wrote:
> > sched: Reinstate group names in /proc/sched_debug.
> >
> > Displaying of group names in /proc/sched_debug was dropped in autogroup
> > patches. Add group names while displaying cfs_rq and tasks information.
> >
> > Signed-off-by: Bharata B Rao <bharata@linux.vnet.ibm.com>
> > ---
> > @@ -144,7 +167,11 @@ void print_cfs_rq(struct seq_file *m, in
> > struct sched_entity *last;
> > unsigned long flags;
> >
> > +#if defined(CONFIG_CGROUP_SCHED) && defined(CONFIG_FAIR_GROUP_SCHED)
>
> defined(CONFIG_CGROUP_SCHED) is not necessary here,
> CONFIG_[FAIR|RT]_GROUP_SCHED always imply CONFIG_CGROUP_SCHED
Took care of this in my latest post.
Thanks,
Bharata.
next prev parent reply other threads:[~2011-01-11 10:13 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-10 5:14 [PATCH -tip 0/2] sched: Get group names back in /proc/sched_debug Bharata B Rao
2011-01-10 5:15 ` [PATCH -tip 1/2] sched: Reinstate group names " Bharata B Rao
2011-01-11 1:53 ` Yong Zhang
2011-01-11 10:13 ` Bharata B Rao [this message]
2011-01-10 5:16 ` [PATCH -tip 2/2] sched: Display autogroup " Bharata B Rao
2011-01-10 9:38 ` Mike Galbraith
2011-01-10 10:09 ` Bharata B Rao
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=20110111101346.GG4772@in.ibm.com \
--to=bharata@linux.vnet.ibm.com \
--cc=a.p.zijlstra@chello.nl \
--cc=efault@gmx.de \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=yong.zhang0@gmail.com \
/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.