From: john stultz <johnstul@us.ibm.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: lkml <linux-kernel@vger.kernel.org>,
"Petr Titěra" <P.Titera@century.cz>,
"Thomas Gleixner" <tglx@linutronix.de>
Subject: Re: [PATCH] time: remove xtime_cache (take 2)
Date: Mon, 12 Apr 2010 21:06:40 -0700 [thread overview]
Message-ID: <1271131600.3469.20.camel@localhost.localdomain> (raw)
In-Reply-To: <20100412210044.2ebbc058.akpm@linux-foundation.org>
On Mon, 2010-04-12 at 21:00 -0400, Andrew Morton wrote:
> On Tue, 6 Apr 2010 14:30:51 -0700 John Stultz <johnstul@us.ibm.com> wrote:
>
> > Thomas: Mind queueing this up for 2.6.35?
> >
> > With the earlier logarithmic time accumulation patch, xtime will now
> > always be within one "tick" of the current time, instead of possibly
> > half a second off.
> >
> > This removes the need for the xtime_cache value, which always stored the
> > time at the last interrupt, so this patch cleans that up removing the
> > xtime_cache related code.
> >
> > This patch also addresses an issue with an earlier version of this change,
> > where xtime_cache was normalizing xtime, which could in some cases be
> > not valid (ie: tv_nsec == NSEC_PER_SEC). This is fixed by handling
> > the edge case in update_wall_time().
> >
> > ...
> >
> > --- a/kernel/time.c
> > +++ b/kernel/time.c
> > @@ -135,7 +135,6 @@ static inline void warp_clock(void)
> > write_seqlock_irq(&xtime_lock);
> > wall_to_monotonic.tv_sec -= sys_tz.tz_minuteswest * 60;
> > xtime.tv_sec += sys_tz.tz_minuteswest * 60;
> > - update_xtime_cache(0);
> > write_sequnlock_irq(&xtime_lock);
> > clock_was_set();
> > }
>
> This conflicts with your time-clean-up-warp_clock.patch, below.
>
> Shrug, I simply ignored the rejected hunk.
Yep. That should be fine. We're just dropping the update_xtime_cache
call, so if it doesn't exist, its not a problem.
thanks
-john
next prev parent reply other threads:[~2010-04-13 4:06 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-06 21:30 [PATCH] time: remove xtime_cache (take 2) John Stultz
2010-04-13 1:00 ` Andrew Morton
2010-04-13 4:06 ` john stultz [this message]
-- strict thread matches above, loose matches on Subject: below --
2010-03-03 0:19 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=1271131600.3469.20.camel@localhost.localdomain \
--to=johnstul@us.ibm.com \
--cc=P.Titera@century.cz \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tglx@linutronix.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