[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20080403141106.51528643.akpm@linux-foundation.org>
Date: Thu, 3 Apr 2008 14:11:06 -0700
From: Andrew Morton <akpm@...ux-foundation.org>
To: Roman Zippel <zippel@...ux-m68k.org>
Cc: johnstul@...ibm.com, linux-kernel@...r.kernel.org
Subject: Re: [PATCH 2/2] Introduce CLOCK_MONOTONIC_RAW
On Wed, 2 Apr 2008 13:50:36 +0200 (CEST)
Roman Zippel <zippel@...ux-m68k.org> wrote:
> On Tue, 18 Mar 2008, john stultz wrote:
>
> > My solution is to introduce CLOCK_MONOTONIC_RAW. This exposes a
> > nanosecond based time value, that increments starting at bootup and has
> > no frequency adjustments made to it what so ever.
> >
> > The time is accessed from userspace via the posix_clock_gettime()
> > syscall, passing CLOCK_MONOTONIC_RAW as the clock_id.
>
> This is a reworked version of this patch based on the previous
> clocksource_forward_now patch, since clocksource_forward_now() takes
> care of the time offset now, it's not needed to do this at various places.
> I also got rid of the monotonic_raw splitting, so the work done during
> update_wall_time() is quite a bit simpler.
All right, I give up. I dropped
clocksource-keep-track-of-original-clocksource-frequency.patch
clocksource-keep-track-of-original-clocksource-frequency-fix.patch
clocksource-introduce-clock_monotonic_raw.patch
clocksource-introduce-clock_monotonic_raw-fix.patch
clocksource-introduce-clock_monotonic_raw-fix-checkpatch-fixes.patch
clocksource-introduce-clocksource_forward_now.patch
Please someone resend everything from scratch when it's all sorted out.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists