linux-kernel - RE: [tip:sched/urgent] sched: Print sched_group::__cpu_power in sched_domain

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <57C9024A16AD2D4C97DC78E552063EA39B3CF29A@orsmsx505.amr.corp.intel.com>
Date:	Tue, 14 Apr 2009 09:29:53 -0700
From:	"Luck, Tony" <tony.luck@...el.com>
To:	"ego@...ibm.com" <ego@...ibm.com>, Ingo Molnar <mingo@...e.hu>
CC:	"mingo@...hat.com" <mingo@...hat.com>,
	"hpa@...or.com" <hpa@...or.com>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	"a.p.zijlstra@...llo.nl" <a.p.zijlstra@...llo.nl>,
	"tglx@...utronix.de" <tglx@...utronix.de>,
	"linux-tip-commits@...r.kernel.org" 
	<linux-tip-commits@...r.kernel.org>
Subject: RE: [tip:sched/urgent] sched: Print sched_group::__cpu_power in
	sched_domain_debug

-               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

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/