From: Ankita Garg <ankita@in.ibm.com>
To: linux-rt-users <linux-rt-users@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>, Ingo Molnar <mingo@elte.hu>,
Gregory Haskins <ghaskins@novell.com>,
Steven Rostedt <rostedt@goodm
Subject: [RT] [PATCH 2/3] Initialize rt.nr_running & rt.nr_unterruptible
Date: Sun, 23 Mar 2008 20:24:41 +0530 [thread overview]
Message-ID: <20080323145441.GD15554@in.ibm.com> (raw)
In-Reply-To: <20080323145029.GB15554@in.ibm.com>
Hi,
o Initialize rt.nr_running and rt.nr_uninterruptible fields explicitly.
Signed-off-by: Ankita Garg <ankita@in.ibm.com>
Index: linux-2.6.24.3/kernel/sched.c
===================================================================
--- linux-2.6.24.3.orig/kernel/sched.c 2008-03-23 19:13:16.000000000 +0530
+++ linux-2.6.24.3/kernel/sched.c 2008-03-23 19:13:40.000000000 +0530
@@ -7333,6 +7333,8 @@
rq->cpu = i;
rq->migration_thread = NULL;
INIT_LIST_HEAD(&rq->migration_queue);
+ rq->rt.nr_running = 0;
+ rq->rt.nr_uninterruptible = 0;
rq->rt.highest_prio = MAX_RT_PRIO;
rq->rt.overloaded = 0;
rq_attach_root(rq, &def_root_domain);
--
Regards,
Ankita Garg (ankita@in.ibm.com)
Linux Technology Center
IBM India Systems & Technology Labs,
Bangalore, India
WARNING: multiple messages have this Message-ID (diff)
From: Ankita Garg <ankita@in.ibm.com>
To: linux-rt-users <linux-rt-users@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>, Ingo Molnar <mingo@elte.hu>,
Gregory Haskins <ghaskins@novell.com>,
Steven Rostedt <rostedt@goodmis.org>,
Peter Zijlstra <a.p.zijlstra@chello.nl>
Subject: [RT] [PATCH 2/3] Initialize rt.nr_running & rt.nr_unterruptible
Date: Sun, 23 Mar 2008 20:24:41 +0530 [thread overview]
Message-ID: <20080323145441.GD15554@in.ibm.com> (raw)
In-Reply-To: <20080323145029.GB15554@in.ibm.com>
Hi,
o Initialize rt.nr_running and rt.nr_uninterruptible fields explicitly.
Signed-off-by: Ankita Garg <ankita@in.ibm.com>
Index: linux-2.6.24.3/kernel/sched.c
===================================================================
--- linux-2.6.24.3.orig/kernel/sched.c 2008-03-23 19:13:16.000000000 +0530
+++ linux-2.6.24.3/kernel/sched.c 2008-03-23 19:13:40.000000000 +0530
@@ -7333,6 +7333,8 @@
rq->cpu = i;
rq->migration_thread = NULL;
INIT_LIST_HEAD(&rq->migration_queue);
+ rq->rt.nr_running = 0;
+ rq->rt.nr_uninterruptible = 0;
rq->rt.highest_prio = MAX_RT_PRIO;
rq->rt.overloaded = 0;
rq_attach_root(rq, &def_root_domain);
--
Regards,
Ankita Garg (ankita@in.ibm.com)
Linux Technology Center
IBM India Systems & Technology Labs,
Bangalore, India
next prev parent reply other threads:[~2008-03-23 14:54 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-23 14:50 [RT] [PATCH 0/3] Few cleanups and RT updates to sched_debug Ankita Garg
2008-03-23 14:52 ` [RT] [PATCH 1/3] Change the names of rt_rq fields for Ankita Garg
2008-03-23 14:52 ` Ankita Garg
2008-03-23 14:54 ` Ankita Garg [this message]
2008-03-23 14:54 ` [RT] [PATCH 2/3] Initialize rt.nr_running & rt.nr_unterruptible Ankita Garg
2008-03-23 15:09 ` [RT] [PATCH 3/3] Update sched_debug with new RT related stats Ankita Garg
2008-03-23 15:09 ` Ankita Garg
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=20080323145441.GD15554@in.ibm.com \
--to=ankita@in.ibm.com \
--cc=ghaskins@novell.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rt-users@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=rostedt@goodm \
/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.