From: tip-bot for Rakib Mullick <rakib.mullick@gmail.com>
To: linux-tip-commits@vger.kernel.org
Cc: linux-kernel@vger.kernel.org, hpa@zytor.com, mingo@redhat.com,
rakib.mullick@gmail.com, peterz@infradead.org,
tglx@linutronix.de, mingo@elte.hu
Subject: [tip:sched/core] sched: Wrap the 'cfs_rq->nr_spread_over' field with CONFIG_SCHED_DEBUG
Date: Fri, 6 May 2011 07:40:03 GMT [thread overview]
Message-ID: <tip-4934a4d3d3fa775601a9f1b35cc0e2aa93f81355@git.kernel.org> (raw)
In-Reply-To: <1304528026.15681.3.camel@localhost.localdomain>
Commit-ID: 4934a4d3d3fa775601a9f1b35cc0e2aa93f81355
Gitweb: http://git.kernel.org/tip/4934a4d3d3fa775601a9f1b35cc0e2aa93f81355
Author: Rakib Mullick <rakib.mullick@gmail.com>
AuthorDate: Wed, 4 May 2011 22:53:46 +0600
Committer: Ingo Molnar <mingo@elte.hu>
CommitDate: Fri, 6 May 2011 09:04:19 +0200
sched: Wrap the 'cfs_rq->nr_spread_over' field with CONFIG_SCHED_DEBUG
cfs_rq->nr_spread_over is only used when CONFIG_SCHED_DEBUG is set.
So wrap it with CONFIG_SCHED_DEBUG.
Signed-off-by: Rakib Mullick <rakib.mullick@gmail.com>
Cc: Peter Zijlstra <peterz@infradead.org>
Link: http://lkml.kernel.org/r/1304528026.15681.3.camel@localhost.localdomain
Signed-off-by: Ingo Molnar <mingo@elte.hu>
---
kernel/sched.c | 2 ++
1 files changed, 2 insertions(+), 0 deletions(-)
diff --git a/kernel/sched.c b/kernel/sched.c
index f11a2a5..3d8a1b2 100644
--- a/kernel/sched.c
+++ b/kernel/sched.c
@@ -328,7 +328,9 @@ struct cfs_rq {
*/
struct sched_entity *curr, *next, *last, *skip;
+#ifdef CONFIG_SCHED_DEBUG
unsigned int nr_spread_over;
+#endif
#ifdef CONFIG_FAIR_GROUP_SCHED
struct rq *rq; /* cpu runqueue to which this cfs_rq is attached */
prev parent reply other threads:[~2011-05-06 7:40 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-04 16:53 [PATCH] sched: Wrap nr_spread_over " Rakib Mullick
2011-05-06 7:40 ` tip-bot for Rakib Mullick [this message]
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=tip-4934a4d3d3fa775601a9f1b35cc0e2aa93f81355@git.kernel.org \
--to=rakib.mullick@gmail.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tip-commits@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=mingo@redhat.com \
--cc=peterz@infradead.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
Powered by JetHome