mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Alessandro Zummo <alessandro.zummo@towertech.it>
To: Matt Mackall <mpm@selenic.com>
Cc: Benjamin Herrenschmidt <benh@kernel.crashing.org>,
	Andi Kleen <ak@muc.de>,
	akpm@osdl.org, torvalds@osdl.org, davem@davemloft.net,
	kkojima@rr.iij4u.or.jp, lethal@linux-sh.org, paulus@samba.org,
	ralf@linux-mips.org, rmk@arm.linux.org.uk,
	linux-kernel@vger.kernel.org
Subject: Re: 11 minute RTC update (was Re: Remove RTC UIP)
Date: Wed, 29 Mar 2006 03:11:02 +0200	[thread overview]
Message-ID: <20060329031102.0e056d85@inspiron> (raw)
In-Reply-To: <20060329000345.GZ3642@waste.org>

On Tue, 28 Mar 2006 18:03:45 -0600
Matt Mackall <mpm@selenic.com> wrote:

> > > >  While we are on the topic, I would like to ask everyone about
> > > >  the 11 min ntp/rtc update feature of the kernel.
> > > > 
> > > >  It is something that makes sense to move to
> > > >  userland?
> > > 
> > > YES !!! :)
> > 
> >  great! given that it is not implemented in the new RTC subsystem
> >  and nobody objected, I will not add it :)
> 
> I agree that this should be migrated to userspace, but I'm more
> worried about the functionality impact here than for the UIP case.
> 
> With existing NTP setups, and the kernel no longer writing to the RTC,
> you might have the RTC drift far enough that NTP failed to sync on the
> next boot. (Correct me if I'm wrong, of course.)

 That's probably true, I'm not expert on the matter. The new subsystem only
 covers platforms that were not covered before (i.e. without external patches),
 so that this should not impact users because the NTP update mode
 was not working on them.

 The problem might arise when other RTC drivers (i.e. x86) will be converted
 and deployed.

 We need a migration plan. Any suggestion? 

-- 

 Best regards,

 Alessandro Zummo,
  Tower Technologies - Turin, Italy

  http://www.towertech.it


  reply	other threads:[~2006-03-29  1:11 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <200603270920.k2R9KYYx007214@shell0.pdx.osdl.net>
     [not found] ` <20060327111836.GA79131@muc.de>
     [not found]   ` <20060327163218.GD3642@waste.org>
     [not found]     ` <20060327190037.GB27030@muc.de>
     [not found]       ` <20060327211143.55ef7c4e@inspiron>
     [not found]         ` <1143512075.2284.2.camel@localhost.localdomain>
     [not found]           ` <20060329000215.683eb2d5@inspiron>
2006-03-29  0:03             ` Matt Mackall
2006-03-29  1:11               ` Alessandro Zummo [this message]
2006-03-29  1:21                 ` Matt Mackall
2006-03-29  1:45                   ` Alessandro Zummo
2006-03-29 16:49                     ` Bryan Henderson
2006-03-29 18:07                       ` Alessandro Zummo
2006-03-30  3:51                         ` Bryan Henderson

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=20060329031102.0e056d85@inspiron \
    --to=alessandro.zummo@towertech.it \
    --cc=ak@muc.de \
    --cc=akpm@osdl.org \
    --cc=benh@kernel.crashing.org \
    --cc=davem@davemloft.net \
    --cc=kkojima@rr.iij4u.or.jp \
    --cc=lethal@linux-sh.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mpm@selenic.com \
    --cc=paulus@samba.org \
    --cc=ralf@linux-mips.org \
    --cc=rmk@arm.linux.org.uk \
    --cc=torvalds@osdl.org \
    /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

all inboxes | Powered by JetHome®