From: Andrew Morton <akpm@linux-foundation.org>
To: "Wang, Yalin" <Yalin.Wang@sonymobile.com>
Cc: "'David Rientjes'" <rientjes@google.com>,
"'heiko.carstens@de.ibm.com'" <heiko.carstens@de.ibm.com>,
"'tglx@linutronix.de'" <tglx@linutronix.de>,
"'linux-kernel@vger.kernel.org'" <linux-kernel@vger.kernel.org>
Subject: Re: [RFC V2] proc: change /proc/stat show
Date: Wed, 18 Mar 2015 15:07:34 -0700 [thread overview]
Message-ID: <20150318150734.f725e75a307601c6214e5b73@linux-foundation.org> (raw)
In-Reply-To: <35FD53F367049845BC99AC72306C23D104A310D42373@CNBJMBX05.corpusers.net>
On Wed, 18 Mar 2015 10:35:39 +0800 "Wang, Yalin" <Yalin.Wang@sonymobile.com> wrote:
> This patch change /proc/stat to show each cpu,
> we show each present cpus instead of eacn online cpu,
> because some cpus are online / offline dynamically,
> we should also show its cputime even it is offline,
> some lib will read this file to detect cpu numbers,
> we should also return the real present cpu numbers,
> not just online cpus.
/proc/cpuinfo also skips offline CPUs.
> --- a/fs/proc/stat.c
> +++ b/fs/proc/stat.c
> @@ -130,7 +130,7 @@ static int show_stat(struct seq_file *p, void *v)
> seq_put_decimal_ull(p, ' ', cputime64_to_clock_t(guest_nice));
> seq_putc(p, '\n');
>
> - for_each_online_cpu(i) {
> + for_each_present_cpu(i) {
> /* Copy values here to work around gcc-2.95.3, gcc-2.96 */
> user = kcpustat_cpu(i).cpustat[CPUTIME_USER];
> nice = kcpustat_cpu(i).cpustat[CPUTIME_NICE];
It's a non-back-compatible userspace interface change and I don't know
what might break as a result. For example, anyone who is using
/proc/stat to find out which CPUs are online will get a surprise!
next prev parent reply other threads:[~2015-03-18 22:07 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-17 9:42 [RFC] " Wang, Yalin
2015-03-17 23:02 ` David Rientjes
2015-03-18 1:55 ` Wang, Yalin
2015-03-18 2:35 ` [RFC V2] " Wang, Yalin
2015-03-18 22:07 ` Andrew Morton [this message]
2015-03-19 7:18 ` Wang, Yalin
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=20150318150734.f725e75a307601c6214e5b73@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=Yalin.Wang@sonymobile.com \
--cc=heiko.carstens@de.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rientjes@google.com \
--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®