* [tip:sched/urgent] sched: Avoid printing sched_group::__cpu_power for default case
2009-04-14 3:39 ` Gautham R Shenoy
@ 2009-04-14 12:03 ` tip-bot for Gautham R Shenoy
2009-04-14 16:29 ` [tip:sched/urgent] sched: Print sched_group::__cpu_power in sched_domain_debug Luck, Tony
` (2 subsequent siblings)
3 siblings, 0 replies; 13+ messages in thread
From: tip-bot for Gautham R Shenoy @ 2009-04-14 12:03 UTC (permalink / raw)
To: linux-tip-commits; +Cc: linux-kernel, ego, hpa, mingo, tony.luck, tglx, mingo
Commit-ID: fa0dacb0eec2f531e457058c05e3fe8b7606ed08
Gitweb: http://git.kernel.org/tip/fa0dacb0eec2f531e457058c05e3fe8b7606ed08
Author: Gautham R Shenoy <ego@in.ibm.com>
AuthorDate: Tue, 14 Apr 2009 09:09:36 +0530
Committer: Ingo Molnar <mingo@elte.hu>
CommitDate: Tue, 14 Apr 2009 14:01:00 +0200
sched: Avoid printing sched_group::__cpu_power for default case
Impact: reduce syslog clutter
Commit 46e0bb9c12f4 ("sched: Print sched_group::__cpu_power
in sched_domain_debug") produces a messy dmesg output while
attempting to print the sched_group::__cpu_power for each
group in the sched_domain hierarchy.
Fix this by avoid printing the __cpu_power for default cases.
(i.e, __cpu_power == SCHED_LOAD_SCALE).
Reported-by: Tony Luck <tony.luck@intel.com>
Signed-off-by: Gautham R Shenoy <ego@in.ibm.com>
Cc: a.p.zijlstra@chello.nl
LKML-Reference: <20090414033936.GA534@in.ibm.com>
Signed-off-by: Ingo Molnar <mingo@elte.hu>
---
kernel/sched.c | 5 +++--
1 files changed, 3 insertions(+), 2 deletions(-)
diff --git a/kernel/sched.c b/kernel/sched.c
index e90e70e..ebd574c 100644
--- a/kernel/sched.c
+++ b/kernel/sched.c
@@ -7367,8 +7367,9 @@ static int sched_domain_debug_one(struct sched_domain *sd, int cpu, int level,
cpumask_or(groupmask, groupmask, sched_group_cpus(group));
cpulist_scnprintf(str, sizeof(str), sched_group_cpus(group));
- printk(KERN_CONT " %s (__cpu_power = %d)", str,
- group->__cpu_power);
+ if (group->__cpu_power != SCHED_LOAD_SCALE)
+ printk(KERN_CONT " %s (__cpu_power = %d)", str,
+ group->__cpu_power);
group = group->next;
} while (group != sd->groups);
^ permalink raw reply related [flat|nested] 13+ messages in thread* RE: [tip:sched/urgent] sched: Print sched_group::__cpu_power in sched_domain_debug
2009-04-14 3:39 ` Gautham R Shenoy
2009-04-14 12:03 ` [tip:sched/urgent] sched: Avoid printing sched_group::__cpu_power for default case tip-bot for Gautham R Shenoy
@ 2009-04-14 16:29 ` Luck, Tony
2009-04-14 17:06 ` Gautham R Shenoy
2009-04-14 18:42 ` [tip:sched/urgent] sched: Avoid printing sched_group::__cpu_power for default case tip-bot for Gautham R Shenoy
2009-04-16 22:48 ` tip-bot for Gautham R Shenoy
3 siblings, 1 reply; 13+ messages in thread
From: Luck, Tony @ 2009-04-14 16:29 UTC (permalink / raw)
To: ego@in.ibm.com, Ingo Molnar
Cc: mingo@redhat.com, hpa@zytor.com, linux-kernel@vger.kernel.org,
a.p.zijlstra@chello.nl, tglx@linutronix.de,
linux-tip-commits@vger.kernel.org
- printk(KERN_CONT " %s (__cpu_power = %d)", str,
- group->__cpu_power);
+ if (group->__cpu_power != SCHED_LOAD_SCALE)
+ printk(KERN_CONT " %s (__cpu_power = %d)", str,
+ group->__cpu_power);
Much quieter ... but perhaps a little too quiet?
Is this what you want? Now the console output looks like this:
CPU0 attaching sched-domain:
domain 0: span 0-15 level CPU
groups:
CPU1 attaching sched-domain:
domain 0: span 0-15 level CPU
groups:
CPU2 attaching sched-domain:
domain 0: span 0-15 level CPU
groups:
...
instead of the original:
CPU0 attaching sched-domain:
domain 0: span 0-15 level CPU
groups: 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15
CPU1 attaching sched-domain:
domain 0: span 0-15 level CPU
groups: 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 0
CPU2 attaching sched-domain:
domain 0: span 0-15 level CPU
groups: 2 3 4 5 6 7 8 9 10 11 12 13 14 15 0 1
...
Either we don't need the empty "groups:" line, or we should
still list the cpus in the group? I'm not really sure what
information you are trying to convey here.
-Tony
^ permalink raw reply [flat|nested] 13+ messages in thread
* Re: [tip:sched/urgent] sched: Print sched_group::__cpu_power in sched_domain_debug
2009-04-14 16:29 ` [tip:sched/urgent] sched: Print sched_group::__cpu_power in sched_domain_debug Luck, Tony
@ 2009-04-14 17:06 ` Gautham R Shenoy
2009-04-14 17:18 ` Luck, Tony
0 siblings, 1 reply; 13+ messages in thread
From: Gautham R Shenoy @ 2009-04-14 17:06 UTC (permalink / raw)
To: Luck, Tony
Cc: Ingo Molnar, mingo@redhat.com, hpa@zytor.com,
linux-kernel@vger.kernel.org, a.p.zijlstra@chello.nl,
tglx@linutronix.de, linux-tip-commits@vger.kernel.org
On Tue, Apr 14, 2009 at 09:29:53AM -0700, Luck, Tony wrote:
> - printk(KERN_CONT " %s (__cpu_power = %d)", str,
> - group->__cpu_power);
> + if (group->__cpu_power != SCHED_LOAD_SCALE)
> + printk(KERN_CONT " %s (__cpu_power = %d)", str,
> + group->__cpu_power);
>
> Much quieter ... but perhaps a little too quiet?
> Is this what you want? Now the console output looks like this:
>
> CPU0 attaching sched-domain:
> domain 0: span 0-15 level CPU
> groups:
> CPU1 attaching sched-domain:
> domain 0: span 0-15 level CPU
> groups:
> CPU2 attaching sched-domain:
> domain 0: span 0-15 level CPU
> groups:
> ...
>
> instead of the original:
>
> CPU0 attaching sched-domain:
> domain 0: span 0-15 level CPU
> groups: 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15
> CPU1 attaching sched-domain:
> domain 0: span 0-15 level CPU
> groups: 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 0
> CPU2 attaching sched-domain:
> domain 0: span 0-15 level CPU
> groups: 2 3 4 5 6 7 8 9 10 11 12 13 14 15 0 1
> ...
>
> Either we don't need the empty "groups:" line, or we should
> still list the cpus in the group? I'm not really sure what
> information you are trying to convey here.
We should be listing the cpus in the group. We should not be listing the
__cpu_power of the group, if the __cpu_power has the default value. In
the patch that I sent this morning, I made a mistake by making dependent
the printing of both cpus as well as __cpu_power, on the if
condition which checks if __cpu_power is default or not.
if (group->__cpu_power != SCHED_LOAD_SCALE)
printk(KERN_CONT " %s (__cpu_power = %d)", str,
group->__cpu_power);
Unfortunately for me, it's not the first goof up I've been involved in
today. Please find the updated patch below.
---->
sched: Avoid printing sched_group::__cpu_power for default case.
From: Gautham R Shenoy <ego@in.ibm.com>
The following commit produces a messy dmesg output while attempting to print
the sched_group::__cpu_power for each group in the sched_domain hierarchy.
commit 46e0bb9c12f4bab539736f1714cbf16600f681ec
Author: Gautham R Shenoy <ego@in.ibm.com>
Date: Mon Mar 30 10:25:20 2009 +0530
sched: Print sched_group::__cpu_power in sched_domain_debug
Fix this by avoid printing the __cpu_power for default cases.
(i.e, __cpu_power == SCHED_LOAD_SCALE).
Reported-by: Tony Luck <tony.luck@intel.com>
Signed-off-by: Gautham R Shenoy <ego@in.ibm.com>
---
kernel/sched.c | 4 +++-
1 files changed, 3 insertions(+), 1 deletions(-)
diff --git a/kernel/sched.c b/kernel/sched.c
index 681d4ae..db2df70 100644
--- a/kernel/sched.c
+++ b/kernel/sched.c
@@ -7467,7 +7467,9 @@ static int sched_domain_debug_one(struct sched_domain *sd, int cpu, int level,
cpumask_or(groupmask, groupmask, sched_group_cpus(group));
cpulist_scnprintf(str, sizeof(str), sched_group_cpus(group));
- printk(KERN_CONT " %s (__cpu_power = %d)", str,
+ printk(KERN_CONT " %s", str);
+ if (group->__cpu_power != SCHED_LOAD_SCALE)
+ printk(KERN_CONT " (__cpu_power = %d)",
group->__cpu_power);
group = group->next;
--
Thanks and Regards
gautham
^ permalink raw reply related [flat|nested] 13+ messages in thread* RE: [tip:sched/urgent] sched: Print sched_group::__cpu_power in sched_domain_debug
2009-04-14 17:06 ` Gautham R Shenoy
@ 2009-04-14 17:18 ` Luck, Tony
2009-04-14 18:40 ` Ingo Molnar
0 siblings, 1 reply; 13+ messages in thread
From: Luck, Tony @ 2009-04-14 17:18 UTC (permalink / raw)
To: ego@in.ibm.com
Cc: Ingo Molnar, mingo@redhat.com, hpa@zytor.com,
linux-kernel@vger.kernel.org, a.p.zijlstra@chello.nl,
tglx@linutronix.de, linux-tip-commits@vger.kernel.org
- printk(KERN_CONT " %s (__cpu_power = %d)", str,
+ printk(KERN_CONT " %s", str);
+ if (group->__cpu_power != SCHED_LOAD_SCALE)
+ printk(KERN_CONT " (__cpu_power = %d)",
group->__cpu_power);
That looks better.
Acked-by: Tony Luck <tony.luck@intel.com>
-Tony
^ permalink raw reply [flat|nested] 13+ messages in thread* Re: [tip:sched/urgent] sched: Print sched_group::__cpu_power in sched_domain_debug
2009-04-14 17:18 ` Luck, Tony
@ 2009-04-14 18:40 ` Ingo Molnar
0 siblings, 0 replies; 13+ messages in thread
From: Ingo Molnar @ 2009-04-14 18:40 UTC (permalink / raw)
To: Luck, Tony
Cc: ego@in.ibm.com, mingo@redhat.com, hpa@zytor.com,
linux-kernel@vger.kernel.org, a.p.zijlstra@chello.nl,
tglx@linutronix.de, linux-tip-commits@vger.kernel.org
* Luck, Tony <tony.luck@intel.com> wrote:
> - printk(KERN_CONT " %s (__cpu_power = %d)", str,
> + printk(KERN_CONT " %s", str);
> + if (group->__cpu_power != SCHED_LOAD_SCALE)
> + printk(KERN_CONT " (__cpu_power = %d)",
> group->__cpu_power);
>
> That looks better.
>
> Acked-by: Tony Luck <tony.luck@intel.com>
Thanks, picked up this variant!
Ingo
^ permalink raw reply [flat|nested] 13+ messages in thread
* [tip:sched/urgent] sched: Avoid printing sched_group::__cpu_power for default case
2009-04-14 3:39 ` Gautham R Shenoy
2009-04-14 12:03 ` [tip:sched/urgent] sched: Avoid printing sched_group::__cpu_power for default case tip-bot for Gautham R Shenoy
2009-04-14 16:29 ` [tip:sched/urgent] sched: Print sched_group::__cpu_power in sched_domain_debug Luck, Tony
@ 2009-04-14 18:42 ` tip-bot for Gautham R Shenoy
2009-04-16 22:48 ` tip-bot for Gautham R Shenoy
3 siblings, 0 replies; 13+ messages in thread
From: tip-bot for Gautham R Shenoy @ 2009-04-14 18:42 UTC (permalink / raw)
To: linux-tip-commits; +Cc: linux-kernel, ego, hpa, mingo, tony.luck, tglx, mingo
Commit-ID: 728fc565bdfc98dc7086fdcccb3f1e1edf195b20
Gitweb: http://git.kernel.org/tip/728fc565bdfc98dc7086fdcccb3f1e1edf195b20
Author: Gautham R Shenoy <ego@in.ibm.com>
AuthorDate: Tue, 14 Apr 2009 09:09:36 +0530
Committer: Ingo Molnar <mingo@elte.hu>
CommitDate: Tue, 14 Apr 2009 20:39:40 +0200
sched: Avoid printing sched_group::__cpu_power for default case
Impact: reduce syslog clutter
Commit 46e0bb9c12f4 ("sched: Print sched_group::__cpu_power
in sched_domain_debug") produces a messy dmesg output while
attempting to print the sched_group::__cpu_power for each
group in the sched_domain hierarchy.
Fix this by avoid printing the __cpu_power for default cases.
(i.e, __cpu_power == SCHED_LOAD_SCALE).
Reported-by: Tony Luck <tony.luck@intel.com>
Signed-off-by: Gautham R Shenoy <ego@in.ibm.com>
Fixed-by: Tony Luck <tony.luck@intel.com>
Cc: a.p.zijlstra@chello.nl
LKML-Reference: <20090414033936.GA534@in.ibm.com>
Signed-off-by: Ingo Molnar <mingo@elte.hu>
---
kernel/sched.c | 8 ++++++--
1 files changed, 6 insertions(+), 2 deletions(-)
diff --git a/kernel/sched.c b/kernel/sched.c
index e90e70e..b902e58 100644
--- a/kernel/sched.c
+++ b/kernel/sched.c
@@ -7367,8 +7367,12 @@ static int sched_domain_debug_one(struct sched_domain *sd, int cpu, int level,
cpumask_or(groupmask, groupmask, sched_group_cpus(group));
cpulist_scnprintf(str, sizeof(str), sched_group_cpus(group));
- printk(KERN_CONT " %s (__cpu_power = %d)", str,
- group->__cpu_power);
+
+ printk(KERN_CONT " %s", str);
+ if (group->__cpu_power != SCHED_LOAD_SCALE) {
+ printk(KERN_CONT " (__cpu_power = %d)",
+ group->__cpu_power);
+ }
group = group->next;
} while (group != sd->groups);
^ permalink raw reply related [flat|nested] 13+ messages in thread* [tip:sched/urgent] sched: Avoid printing sched_group::__cpu_power for default case
2009-04-14 3:39 ` Gautham R Shenoy
` (2 preceding siblings ...)
2009-04-14 18:42 ` [tip:sched/urgent] sched: Avoid printing sched_group::__cpu_power for default case tip-bot for Gautham R Shenoy
@ 2009-04-16 22:48 ` tip-bot for Gautham R Shenoy
3 siblings, 0 replies; 13+ messages in thread
From: tip-bot for Gautham R Shenoy @ 2009-04-16 22:48 UTC (permalink / raw)
To: linux-tip-commits; +Cc: linux-kernel, ego, hpa, mingo, tony.luck, tglx, mingo
Commit-ID: 381512cf3d27f63f7a45b1bbe7d2d609c2ea3b74
Gitweb: http://git.kernel.org/tip/381512cf3d27f63f7a45b1bbe7d2d609c2ea3b74
Author: Gautham R Shenoy <ego@in.ibm.com>
AuthorDate: Tue, 14 Apr 2009 09:09:36 +0530
Committer: Ingo Molnar <mingo@elte.hu>
CommitDate: Fri, 17 Apr 2009 00:46:05 +0200
sched: Avoid printing sched_group::__cpu_power for default case
Commit 46e0bb9c12f4 ("sched: Print sched_group::__cpu_power
in sched_domain_debug") produces a messy dmesg output while
attempting to print the sched_group::__cpu_power for each
group in the sched_domain hierarchy.
Fix this by avoid printing the __cpu_power for default cases.
(i.e, __cpu_power == SCHED_LOAD_SCALE).
[ Impact: reduce syslog clutter ]
Reported-by: Tony Luck <tony.luck@intel.com>
Signed-off-by: Gautham R Shenoy <ego@in.ibm.com>
Fixed-by: Tony Luck <tony.luck@intel.com>
Cc: a.p.zijlstra@chello.nl
LKML-Reference: <20090414033936.GA534@in.ibm.com>
Signed-off-by: Ingo Molnar <mingo@elte.hu>
---
kernel/sched.c | 8 ++++++--
1 files changed, 6 insertions(+), 2 deletions(-)
diff --git a/kernel/sched.c b/kernel/sched.c
index e90e70e..b902e58 100644
--- a/kernel/sched.c
+++ b/kernel/sched.c
@@ -7367,8 +7367,12 @@ static int sched_domain_debug_one(struct sched_domain *sd, int cpu, int level,
cpumask_or(groupmask, groupmask, sched_group_cpus(group));
cpulist_scnprintf(str, sizeof(str), sched_group_cpus(group));
- printk(KERN_CONT " %s (__cpu_power = %d)", str,
- group->__cpu_power);
+
+ printk(KERN_CONT " %s", str);
+ if (group->__cpu_power != SCHED_LOAD_SCALE) {
+ printk(KERN_CONT " (__cpu_power = %d)",
+ group->__cpu_power);
+ }
group = group->next;
} while (group != sd->groups);
^ permalink raw reply related [flat|nested] 13+ messages in thread