From: Andrew Morton <akpm@linux-foundation.org>
To: Tomas Janousek <tjanouse@redhat.com>
Cc: john stultz <johnstul@us.ibm.com>,
linux-kernel@vger.kernel.org, tsmetana@redhat.com,
riel@redhat.com
Subject: Re: [PATCH] Use boot based time for process start time and boot time in /proc
Date: Thu, 10 May 2007 16:40:47 -0700 [thread overview]
Message-ID: <20070510164047.263a9524.akpm@linux-foundation.org> (raw)
In-Reply-To: <f3c12bbf0772543db18c7a5251ce92f4f4f6758e.1178816485.git.tomi@nomi.cz>
On Thu, 10 May 2007 19:10:42 +0200
Tomas Janousek <tjanouse@redhat.com> wrote:
> Commit 411187fb05cd11676b0979d9fbf3291db69dbce2 caused boot time to move and
> process start times to become invalid after suspend. Using boot based time for
> those restores the old behaviour and fixes the issue.
>
> ..
>
> @@ -445,12 +445,14 @@ static int show_stat(struct seq_file *p, void *v)
> unsigned long jif;
> cputime64_t user, nice, system, idle, iowait, irq, softirq, steal;
> u64 sum = 0;
> + struct timespec boottime;
>
> user = nice = system = idle = iowait =
> irq = softirq = steal = cputime64_zero;
> - jif = - wall_to_monotonic.tv_sec;
> - if (wall_to_monotonic.tv_nsec)
> - --jif;
> + getboottime(&boottime);
> + jif = boottime.tv_sec;
> + if (boottime.tv_nsec)
> + ++jif;
>
Is the switch from --jif to ++jif a functional change? If so, how come?
> for_each_possible_cpu(i) {
> int j;
> diff --git a/include/linux/sched.h b/include/linux/sched.h
> index 40645b4..386ff51 100644
> --- a/include/linux/sched.h
> +++ b/include/linux/sched.h
> @@ -918,7 +918,7 @@ struct task_struct {
> unsigned int rt_priority;
> cputime_t utime, stime;
> unsigned long nvcsw, nivcsw; /* context switch counts */
> - struct timespec start_time;
> + struct timespec start_time, real_start_time;
no, please prefer to do
struct timespec start_time;
struct timespec real_start_time;
which gives a nice place to add a comment documenting the field.
Please document fields.
What is the difference between start_time and real_start_time?
next prev parent reply other threads:[~2007-05-10 23:41 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-03 15:03 Broken process startup times after suspend (regression) Tomas Janousek
2007-05-03 19:59 ` john stultz
2007-05-04 16:13 ` Tomas Janousek
2007-05-04 18:18 ` john stultz
2007-05-04 19:09 ` Tomas Janousek
2007-05-10 17:10 ` [PATCH] Introduce boot based time Tomas Janousek
2007-05-10 17:10 ` [PATCH] Use boot based time for process start time and boot time in /proc Tomas Janousek
2007-05-10 18:44 ` john stultz
2007-05-10 23:40 ` Andrew Morton [this message]
2007-05-11 8:45 ` Tomas Janousek
2007-05-11 19:51 ` Andrew Morton
2007-05-11 23:37 ` Tomas Janousek
2007-05-11 8:46 ` Tomas Janousek
2007-05-10 17:10 ` [PATCH] Use boot based time for uptime " Tomas Janousek
2007-05-10 18:47 ` john stultz
2007-05-10 18:42 ` [PATCH] Introduce boot based time john stultz
2007-05-10 19:48 ` Ingo Oeser
2007-05-10 20:00 ` Tomas Janousek
2007-05-10 20:02 ` john stultz
2007-05-10 22:22 ` Ingo Oeser
2007-05-10 23:40 ` Andrew Morton
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=20070510164047.263a9524.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=johnstul@us.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=riel@redhat.com \
--cc=tjanouse@redhat.com \
--cc=tsmetana@redhat.com \
/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