linux-kernel - Re: [PATCH 1/6] [RFC] posix clocks: dynamic clock ids.

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: <20101018142748.GA5767@riccoc20.at.omicron.at>
Date:	Mon, 18 Oct 2010 16:27:48 +0200
From:	Richard Cochran <richardcochran@...il.com>
To:	John Stultz <john.stultz@...aro.org>
Cc:	LKML <linux-kernel@...r.kernel.org>,
	Richard Cochran <richard.cochran@...cron.at>,
	Alessandro Zummo <a.zummo@...ertech.it>,
	Thomas Gleixner <tglx@...utronix.de>
Subject: Re: [PATCH 1/6] [RFC] posix clocks: dynamic clock ids.

On Fri, Oct 15, 2010 at 05:38:50PM -0700, John Stultz wrote:
> From: Richard Cochran <richardcochran@...il.com>
> 
> This patch augments the POSIX clock code to offer a dynamic clock
> creation method. Instead of registering a hard coded clock ID, modules
> may call create_posix_clock(), which returns a new clock ID.
> 
> Signed-off-by: Richard Cochran <richard.cochran@...cron.at>
> 
> This patch still has un-addressed lifetime issues pointed out by
> Alan Cox. More work is needed here, but for now this provides the
> functionality needed for the following patches.

I am working on a fully dynamic clock implementation in the style
suggested by Alan. Using it would change some details in this RTC
patch series, but not the general idea.

Should I post the dynamic clock stuff all by itself for review?

(The entire patch series including the PTP hardware clocks will take
a bit longer.)

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