From: Martin Schwidefsky <schwidefsky@de.ibm.com>
To: Michael Abbott <michael@araneidae.co.uk>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Jan Engelhardt <jengelh@medozas.de>
Subject: Re: [PATCH] Re: /proc/uptime idle counter remains at 0
Date: Mon, 25 May 2009 12:28:20 +0200 [thread overview]
Message-ID: <20090525122820.044e1e35@skybase> (raw)
In-Reply-To: <Pine.LNX.4.64.0905181421300.1088@venus.araneidae.co.uk>
On Mon, 18 May 2009 14:23:03 +0100 (BST)
Michael Abbott <michael@araneidae.co.uk> wrote:
> diff --git a/fs/proc/uptime.c b/fs/proc/uptime.c
> index 0c10a0b..0f43395 100644
> --- a/fs/proc/uptime.c
> +++ b/fs/proc/uptime.c
> @@ -4,13 +4,19 @@
> #include <linux/sched.h>
> #include <linux/seq_file.h>
> #include <linux/time.h>
> +#include <linux/kernel_stat.h>
> #include <asm/cputime.h>
>
> static int uptime_proc_show(struct seq_file *m, void *v)
> {
> struct timespec uptime;
> struct timespec idle;
> - cputime_t idletime = cputime_add(init_task.utime, init_task.stime);
> + int len, i;
> + cputime_t idletime = 0;
> +
> + for_each_possible_cpu(i)
> + idletime = cputime64_add(idletime, kstat_cpu(i).cpustat.idle);
> + idletime = cputime64_to_clock_t(idletime);
>
> do_posix_clock_monotonic_gettime(&uptime);
> monotonic_to_bootbased(&uptime);
I found another problem with this patch: why do you convert the
idletime from cputime_t to clock_t ? The call to cputime_to_timespec
takes a cputime_t and the conversion from cputime to clock_t returns a
value that is way to small on s390. After removing that line it works
for me but I wonder why you added it.
--
blue skies,
Martin.
"Reality continues to ruin my life." - Calvin.
next prev parent reply other threads:[~2009-05-25 10:29 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-18 13:23 [PATCH] Re: /proc/uptime idle counter remains at 0 Michael Abbott
2009-05-18 14:00 ` Martin Schwidefsky
2009-05-25 10:28 ` Martin Schwidefsky [this message]
2009-07-06 15:48 ` Michael Abbott
2009-07-06 15:56 ` Jan Engelhardt
2009-07-06 16:09 ` Michael Abbott
-- strict thread matches above, loose matches on Subject: below --
2009-05-09 8:05 Jan Engelhardt
2009-05-10 17:12 ` Martin Schwidefsky
2009-05-11 0:46 ` Jan Engelhardt
2009-05-11 6:23 ` [PATCH] " Michael Abbott
2009-05-11 7:35 ` Martin Schwidefsky
2009-05-11 7:42 ` Jan Engelhardt
2009-05-11 8:10 ` Martin Schwidefsky
2009-05-11 9:07 ` Michael Abbott
2009-08-14 12:18 ` Michael Abbott
2009-08-17 5:25 ` Amerigo Wang
2009-08-17 6:12 ` Michael Abbott
2009-08-17 6:23 ` Amerigo Wang
2009-08-17 6:58 ` Michael Abbott
2009-08-17 8:23 ` Amerigo Wang
2009-09-09 5:58 ` Andrew Morton
2009-09-09 8:02 ` Martin Schwidefsky
2009-09-10 13:02 ` Johan van Baarlen
2009-09-10 15:37 ` Martin Schwidefsky
2009-09-10 16:27 ` Michael Abbott
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=20090525122820.044e1e35@skybase \
--to=schwidefsky@de.ibm.com \
--cc=jengelh@medozas.de \
--cc=linux-kernel@vger.kernel.org \
--cc=michael@araneidae.co.uk \
/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;
as well as URLs for NNTP newsgroup(s).