From: Mike Travis <travis@sgi.com>
To: Ingo Molnar <mingo@elte.hu>
Cc: Thomas Gleixner <tglx@linutronix.de>,
"H. Peter Anvin" <hpa@zytor.com>,
Andrew Morton <akpm@linux-foundation.org>,
linux-kernel@vger.kernel.org
Subject: [PATCH 0/4] x86: add cpus_scnprintf function v2
Date: Fri, 04 Apr 2008 18:24:47 -0700 [thread overview]
Message-ID: <20080405012447.440875000@polaris-admin.engr.sgi.com> (raw)
* Add a new cpus_scnprintf and a sysctl flag to control how cpumask sets
are printed. The default (1) is to use the current cpumask_scnprintf.
If kernel.compat_cpus_printf is '0', then cpulist_scnprintf is used.
In addition, a nodes_scnprintf function is provided for compatibilty.
* This is introduced with a CONFIG_KERN_COMPAT_CPUSET_PRINTF flag which
currently is only defined for X86_64_SMP architecture. For all other
architectures the current cpumask_scnprintf() is used.
* Add usage information to Documentation/sysctl/kernel.txt for the
/proc/sys/kernel/compat_cpus_printf flag.
* Add cpu_sysdev_class functions to display the
cpu_online_map
cpu_present_map
cpu_possible_map
cpu_system_map
* Modify usages of cpumask_scnprintf to use the new cpus_scnprintf where
appropriate. The list of files affected are:
arch/x86/kernel/cpu/intel_cacheinfo.c
drivers/base/node.c
drivers/base/topology.c
drivers/pci/pci-sysfs.c
drivers/pci/probe.c
kernel/irq/proc.c
kernel/profile.c
kernel/sched_stats.h
kernel/sysctl.c
kernel/sysctl_check.c
kernel/trace/trace.c
Note that kernel/sched.c is not in this patchset as it has many other changes,
so the change to use cpus_scnprintf is in a following patchset.
For inclusion in x86/latest.
Based on:
git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux-2.6.git
+ x86/latest .../x86/linux-2.6-x86.git
+ sched-devel/latest .../mingo/linux-2.6-sched-devel.git
Signed-off-by: Mike Travis <travis@sgi.com>
---
v2:
Renamed cpuset_scnprintf() to cpus_scnprintf to avoid confusion with
"cpusets", and changed the other names to match.
Added a sentinel character for the cpulist type output so scripts can
be written to handle both cases.
Added warning in the Documentation/sysctl/kernel.txt that changing this
option may break scripts and programs that rely on the current format.
Also provided example on how to process the output.
Added information to Documentation/scheduler/sched-stats.txt about
change in version number because of new cpus_scnprintf function.
--
next reply other threads:[~2008-04-05 1:25 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-05 1:24 Mike Travis [this message]
2008-04-05 1:24 ` [PATCH 1/4] " Mike Travis
2008-04-05 1:24 ` [PATCH 2/4] x86: modify show_shared_cpu_map in intel_cacheinfo v2 Mike Travis
2008-04-07 13:57 ` Bert Wesarg
2008-04-07 18:45 ` Mike Travis
2008-04-05 1:24 ` [PATCH 3/4] cpumask: use new cpus_scnprintf function v2 Mike Travis
2008-04-05 1:24 ` [PATCH 4/4] cpumask: add show cpu map functions Mike Travis
2008-04-07 8:04 ` [PATCH 0/4] x86: add cpus_scnprintf function v2 Paul Jackson
2008-04-07 8:16 ` Ingo Molnar
2008-04-07 8:44 ` Paul Jackson
2008-04-07 18:42 ` Mike Travis
2008-04-10 15:30 ` Paul Jackson
2008-04-07 14:07 ` Bert Wesarg
2008-04-07 18:22 ` Mike Travis
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=20080405012447.440875000@polaris-admin.engr.sgi.com \
--to=travis@sgi.com \
--cc=akpm@linux-foundation.org \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--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
all inboxes | Powered by JetHome®