From: john stultz <johnstul@us.ibm.com>
To: lkml <linux-kernel@vger.kernel.org>
Cc: h.lambermont@aramiska.net
Subject: [RFC][PATCH] linux-2.5.70_btime-fix_A0
Date: 03 Jun 2003 16:00:59 -0700 [thread overview]
Message-ID: <1054681259.32091.783.camel@w-jstultz2.beaverton.ibm.com> (raw)
All,
Since jiffies didn't necessarily start incrementing at a second
boundary, jiffies/HZ doesn't increment at the same moment as
xtime.tv_sec. This causes one second wobbles in the calculation of btime
(xtime.tv_sec - jiffies/HZ).
This fix increases the precision of the calculation so the usec
component of xtime is used as well. Additionally it fixes some of the
non-atomic reading of time values.
This is a fix for bugme bug #764.
http://bugme.osdl.org/show_bug.cgi?id=764
Let me know if you have any comments
thanks
-john
--- 1.77/fs/proc/proc_misc.c Sun May 25 14:08:09 2003
+++ edited/fs/proc/proc_misc.c Tue Jun 3 15:52:41 2003
@@ -378,8 +378,22 @@
{
int i, len;
extern unsigned long total_forks;
- u64 jif = get_jiffies_64() - INITIAL_JIFFIES;
+ u64 jif;
unsigned int sum = 0, user = 0, nice = 0, system = 0, idle = 0, iowait = 0;
+ struct timeval now;
+ unsigned long seq;
+
+ /* Atomically read jiffies and time of day */
+ do {
+ seq = read_seqbegin(&xtime_lock);
+
+ jif = get_jiffies_64() - INITIAL_JIFFIES;
+ do_gettimeofday(&now);
+ } while (read_seqretry(&xtime_lock, seq));
+
+ /* calc # of seconds since boot time */
+ jif = ((u64)now.tv_sec * HZ) + (now.tv_usec/(1000000/HZ)) - jif;
+ do_div(jif, HZ);
for (i = 0 ; i < NR_CPUS; i++) {
int j;
@@ -419,7 +433,6 @@
len += sprintf(page + len, " %u", kstat_irqs(i));
#endif
- do_div(jif, HZ);
len += sprintf(page + len,
"\nctxt %lu\n"
"btime %lu\n"
@@ -427,7 +440,7 @@
"procs_running %lu\n"
"procs_blocked %lu\n",
nr_context_switches(),
- xtime.tv_sec - (unsigned long) jif,
+ (unsigned long)jif,
total_forks,
nr_running(),
nr_iowait());
next reply other threads:[~2003-06-03 22:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-03 23:00 john stultz [this message]
2003-06-04 2:25 ` jw schultz
2003-06-04 18:20 ` john stultz
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=1054681259.32091.783.camel@w-jstultz2.beaverton.ibm.com \
--to=johnstul@us.ibm.com \
--cc=h.lambermont@aramiska.net \
--cc=linux-kernel@vger.kernel.org \
/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®