public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: john stultz <johnstul@us.ibm.com>
Cc: lkml <linux-kernel@vger.kernel.org>,
	albert@users.sourceforge.net, Paul Mackerras <paulus@samba.org>,
	schwidefsky@de.ibm.com, mahuja@us.ibm.com, donf@us.ibm.com,
	mpm@selenic.com
Subject: Re: [RFC][PATCH (1/4)] new timeofday core subsystem (v A4)
Date: Sat, 30 Apr 2005 09:50:05 +1000	[thread overview]
Message-ID: <1114818605.7182.299.camel@gaston> (raw)
In-Reply-To: <1114814747.28231.2.camel@cog.beaverton.ibm.com>

On Fri, 2005-04-29 at 15:45 -0700, john stultz wrote:
> All,
>         This patch implements the architecture independent portion of
> the time of day subsystem. For a brief description on the rework, see
> here: http://lwn.net/Articles/120850/ (Many thanks to the LWN team for
> that clear writeup!)
> 
> Mostly this version is just a cleanup of the last release. One neat
> feature is the new sysfs interface which allows you to manually override
> the selected timesource while the system is running. 
> 
> Included below is timeofday.c (which includes all the time of day
> management and accessor functions), ntp.c (which includes the ntp
> scaling calculation code, leapsecond processing, and ntp kernel state
> machine code), timesource.c (for timesource specific management
> functions), interface definition .h files, the example jiffies
> timesource (lowest common denominator time source, mainly for use as
> example code) and minimal hooks into arch independent code.
> 
> The patch does not function without minimal architecture specific hooks
> (i386, x86-64, ppc32, ppc64, ia64 and s390 examples to follow), and it
> should be able to be applied to a tree without affecting the code.

My concern at this point is how to deal with the userland gettimofday
implementation in the ppc64 vDSO ...

Ben.



  parent reply	other threads:[~2005-04-29 23:51 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-04-29 22:45 [RFC][PATCH (1/4)] new timeofday core subsystem (v A4) john stultz
2005-04-29 22:46 ` [RFC][PATCH (2/4)] new timeofday arch specific hooks " john stultz
2005-04-29 22:47   ` [RFC][PATCH (3/4)] new timeofday arch specific timesource drivers " john stultz
2005-04-29 22:48     ` [RFC][PATCH (4/4)] new timeofday vsyscall proof of concept " john stultz
2005-05-02 21:13   ` [RFC][PATCH (2/4)] new timeofday arch specific hooks " Pavel Machek
2005-05-02 21:28     ` john stultz
2005-04-29 23:35 ` [RFC][PATCH] new timeofday-based soft-timer subsystem Nishanth Aravamudan
2005-05-02 18:41   ` Darren Hart
2005-05-03 17:02   ` Nishanth Aravamudan
2005-05-03 17:22     ` Chris Friesen
2005-05-03 18:07       ` Nish Aravamudan
2005-05-03 21:47     ` Nishanth Aravamudan
2005-04-29 23:44 ` [RFC][PATCH (1/4)] new timeofday core subsystem (v A4) john stultz
2005-04-29 23:50 ` Benjamin Herrenschmidt [this message]
2005-04-30  0:33   ` 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=1114818605.7182.299.camel@gaston \
    --to=benh@kernel.crashing.org \
    --cc=albert@users.sourceforge.net \
    --cc=donf@us.ibm.com \
    --cc=johnstul@us.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mahuja@us.ibm.com \
    --cc=mpm@selenic.com \
    --cc=paulus@samba.org \
    --cc=schwidefsky@de.ibm.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