From: Tomas Janousek <tjanouse@redhat.com>
To: john stultz <johnstul@us.ibm.com>
Cc: linux-kernel@vger.kernel.org, tsmetana@redhat.com, riel@redhat.com
Subject: Re: Broken process startup times after suspend (regression)
Date: Fri, 4 May 2007 21:09:23 +0200 [thread overview]
Message-ID: <20070504190923.GA24554@redhat.com> (raw)
In-Reply-To: <1178302732.5929.23.camel@localhost.localdomain>
Hi,
On Fri, May 04, 2007 at 11:18:52AM -0700, john stultz wrote:
> > diff --git a/kernel/fork.c b/kernel/fork.c
> > index 6af959c..b10d9b7 100644
> > --- a/kernel/fork.c
> > +++ b/kernel/fork.c
> > @@ -1056,6 +1056,7 @@ static struct task_struct *copy_process(unsigned long clone_flags,
> >
> > p->lock_depth = -1; /* -1 = no lock */
> > do_posix_clock_monotonic_gettime(&p->start_time);
> > + bbtime_get_ts(&p->real_start_time);
> > p->security = NULL;
> > p->io_context = NULL;
> > p->io_wait = NULL;
>
> Since both do_posix_clock_monotonic_gettime and bbtime_get_ts actually
> read the timekeeping hardware (which could cost around 1.5us each), we
> probably will want to optimize this down to a single read, or just avoid
> the hardware read and take lower-granularity xtime value.
>
> However, I'm not sure how fine-grained the start_time values need to be.
We can add a function like monotonic_to_bb probably? Nothing else crossed my
mind.
> > diff --git a/kernel/hrtimer.c b/kernel/hrtimer.c
> > index b74860a..cd744a1 100644
> > --- a/kernel/hrtimer.c
> > +++ b/kernel/hrtimer.c
> > @@ -128,6 +128,33 @@ void ktime_get_ts(struct timespec *ts)
> > }
> > EXPORT_SYMBOL_GPL(ktime_get_ts);
> >
> > +/**
> > + * bbtime_get_ts - get the boot based clock in timespec format
> > + * @ts: pointer to timespec variable
> > + *
> > + * The function calculates the boot based clock from the realtime
> > + * clock, the wall_to_monotonic offset and the total sleep time and
> > + * stores the result in normalized timespec format in the variable
> > + * pointed to by @ts.
>
> You might want to clarify this as being the "monotonic boot time", or
> the time the system has been running including sleep time and that calls
> to settimeofday() will not affect this value.
I just copied the text from the ktime_get_ts, but yes, why not.
> > + */
> > +void bbtime_get_ts(struct timespec *ts)
>
> Any reason you added this in hrtimer.c instead of timer.c? I think
> keeping the new functions closer together would make the subtle
> difference between them more clear, and would allow total_sleep_time to
> be static to one file.
The same as above, I copied the ktime_get_ts and put it under that. Will doing
the diff against -mm solve this automagically? :)
> > @@ -832,6 +836,21 @@ void getnstimeofday(struct timespec *ts)
> > EXPORT_SYMBOL(getnstimeofday);
> >
> > /**
> > + * getboottime - Return the real time of system boot.
> > + * @ts: pointer to the timespec to be set
>
> Might want to clarify this as being the "boot time" based on the current
> CLOCK_REALTIME clock, noting that calls to settimeofday() would affect
> this value.
Ok.
> The only other gotcha is that this patch conflicts with a 2.6.22 queued
> patch in -mm that moves the majority of timekeeping code in
> kernel/timer.c to kernel/time/timekeeping.c
>
> So it might be easiest to re-diff this against -mm and send it to Andrew
> for inclusion along with the cleanups. However, since this is a fix, it
> should have priority over cleanups. I just don't want to upset Andrew's
> tree too much :)
>
> Your thoughts?
I'll look at that and will see.
Thanks for the comments,
--
TJ. (Brno, CZ), BaseOS, Red Hat
next prev parent reply other threads:[~2007-05-04 19:09 UTC|newest]
Thread overview: 23+ 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 [this message]
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
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
-- strict thread matches above, loose matches on Subject: below --
2007-05-06 3:16 Broken process startup times after suspend (regression) Albert Cahalan
2007-05-10 11:36 ` Pavel Machek
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=20070504190923.GA24554@redhat.com \
--to=tjanouse@redhat.com \
--cc=johnstul@us.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=riel@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