public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: George Anzinger <george@mvista.com>
To: john stultz <johnstul@us.ibm.com>
Cc: Tim Schmielau <tim@physik3.uni-rostock.de>,
	Jerome Borsboom <j.borsboom@erasmusmc.nl>,
	lkml <linux-kernel@vger.kernel.org>
Subject: Re: process start time set wrongly at boot for kernel 2.6.9
Date: Wed, 20 Oct 2004 07:51:12 -0700	[thread overview]
Message-ID: <41767B60.4050409@mvista.com> (raw)
In-Reply-To: <1098233967.20778.93.camel@cog.beaverton.ibm.com>

john stultz wrote:
> On Tue, 2004-10-19 at 17:42, Tim Schmielau wrote:
> 
>>On Tue, 19 Oct 2004, john stultz wrote:
>>
>>
>>>On Tue, 2004-10-19 at 11:21, Jerome Borsboom wrote:
>>>
>>>>Starting with kernel 2.6.9 the process start time is set wrongly for 
>>>>processes that get started early in the boot process. Below is a dump from 
>>>>my 'ps' command. Note the start time for processes 1-12. After process 12 
>>>>the start time is set right.
>>>
>>>How reproducible is this? Are the correct and incorrect time values
>>>always off by the same amount? 
>>>
>>>Are you running NTP? I'm curious if you are changing your system time
>>>during boot. 
>>
>>I'd bet that some process early in the boot adjusts your system time.
> 
> 
> He claims that's not the case (you weren't CC'ed on his reply, but its
> on lkml). He believes the time changes before NTP starts up. Might be
> something else, but I'm not sure.
> 
> 
>>Then this is expected behavior. This is why I would have preferred the 
>>simple back-out patch for the boot times problem.
>>
>>I'm sorry I fell of the net for so long and didn't stand up for the 
>>simpler change in this case. Oh well.
>>
>>I'll probably supply a back-out patch for -mm then, after wading through
>>my multi-megabyte email backlog (sorry John, still need to read your time
>>keeping proposal and all its discussion).
> 
> 
> I've begun to agree with you about this issue. It seems that until we
> can catch every use of jiffies for time, doing one by one is going to
> cause consistency problems.  So I'd support the full backout of the
> do_posix_clock_monotonic_gettime changes to the proc interface. 
> 
> George, would you protest this?

It seems to me that if we do that we will stop making any changes at all.  I.e. 
we will not see the rest of the "jiffies for time" code, as it will not "hurt" 
any more.

Also, the orgional change was made for a reason...

-g
> 
> As for the timeofday overhaul, I've had zero time to work on it
> recently. I hate that I dropped code and then went missing for weeks.
> I'll have to see if I can get a few cycles at home to sync up my current
> tree and send it out. 
> 
> thanks
> -john
> 
> 

-- 
George Anzinger   george@mvista.com
High-res-timers:  http://sourceforge.net/projects/high-res-timers/


  parent reply	other threads:[~2004-10-21 13:42 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-10-19 18:21 process start time set wrongly at boot for kernel 2.6.9 Jerome Borsboom
2004-10-19 20:11 ` john stultz
2004-10-20  0:42   ` Tim Schmielau
2004-10-20  0:59     ` john stultz
2004-10-20  3:05       ` gradual timeofday overhaul Tim Schmielau
2004-10-20  7:47         ` Len Brown
2004-10-20 15:09           ` George Anzinger
2004-10-20 15:59             ` Richard B. Johnson
2004-10-20 15:17           ` George Anzinger
2004-10-20 17:09           ` Lee Revell
2004-10-20 21:42             ` Len Brown
2004-10-20 18:13         ` john stultz
2004-10-20 14:51       ` George Anzinger [this message]
2004-10-20 17:42         ` process start time set wrongly at boot for kernel 2.6.9 john stultz
2004-10-20 23:52           ` George Anzinger
2004-10-21  0:25             ` john stultz
2004-10-21  1:04               ` George Anzinger
2004-10-27  7:55   ` Tim Schmielau
  -- strict thread matches above, loose matches on Subject: below --
2004-10-19 21:03 Jerome Borsboom

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=41767B60.4050409@mvista.com \
    --to=george@mvista.com \
    --cc=j.borsboom@erasmusmc.nl \
    --cc=johnstul@us.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=tim@physik3.uni-rostock.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