linux-kernel - RE: NTP time sync

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <009a01c7114a$b429f850$020120ac@Jocke>
Date:	Sun, 26 Nov 2006 12:04:54 +0100
From:	"Joakim Tjernlund" <joakim.tjernlund@...nsmode.se>
To:	"'David Brownell'" <david-b@...bell.net>,
	"'Benjamin Herrenschmidt'" <benh@...nel.crashing.org>
Cc:	<akpm@...l.org>,
	"'Alessandro Zummo'" <alessandro.zummo@...ertech.it>,
	<linuxppc-dev@...abs.org>, <lethal@...ux-sh.org>,
	"'Linux Kernel Mailing List'" <linux-kernel@...r.kernel.org>,
	<ralf@...ux-mips.org>, "'Andi Kleen'" <ak@....de>,
	<paulus@...ba.org>, <rmk@....linux.org.uk>, <davem@...emloft.net>,
	<kkojima@...iij4u.or.jp>
Subject: RE: NTP time sync

> -----Original Message-----
> From: 
> linuxppc-dev-bounces+joakim.tjernlund=transmode.se@...abs.org 
> [mailto:linuxppc-dev-bounces+joakim.tjernlund=transmode.se@ozl
> abs.org] On Behalf Of David Brownell
> Sent: den 26 november 2006 00:22
> To: Benjamin Herrenschmidt
> Cc: akpm@...l.org; Alessandro Zummo; linuxppc-dev@...abs.org; 
> lethal@...ux-sh.org; Linux Kernel Mailing List; 
> ralf@...ux-mips.org; Andi Kleen; paulus@...ba.org; 
> rmk@....linux.org.uk; davem@...emloft.net; kkojima@...iij4u.or.jp
> Subject: Re: NTP time sync
> 
> On Thursday 23 November 2006 3:00 am, Benjamin Herrenschmidt wrote:
> > 
> > Couldn't we have a transition period by making the kernel 
> not rely on
> > interrupts ? if the NTP irq code just triggers a work 
> queue, then all of
> > a sudden, all of the RTC drivers can be used and the 
> latency is small.
> > That might well be a good enough solution and is very simple.
> 
> Good point.  Of course, one issue is that the NTP sync code all
> seems to be platform-specific right now ... just like the code
> to set the system time from an RTC at boot (except for the new
> RTC framework stuff) and after resume.
> 
> - Dave

Looking at rtc-dev.c I don't see a MARJOR number assigned to /dev/rtcN. Seems like
it is dynamically allocated to whatever major number that is free.
Is that the way it is supposed to be? How do I create a static /dev/rtcN in my /dev
directory if the major number isn't fixed?
Maybe I am just missing something, feel free to correct me :)

 Jocke

-
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/