linux-kernel - Re: [PATCH] /dev/time for Linux, inspired by Plan 9

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] [day] [month] [year] [list]

Message-Id: <20090314232700.BNAW15318.fed1rmmtao105.cox.net@fed1rmimpo01.cox.net>
Date:	Sat, 14 Mar 2009 18:27:04 -0500
From:	Chris Brannon <cmbrannon@....net>
To:	linux-kernel@...r.kernel.org
Subject: Re: [PATCH] /dev/time for Linux, inspired by Plan 9

J.R. Mauro wrote:
> On Sat, Mar 07, 2009 at 10:23:05AM -0600, Chris Brannon wrote:
> > John Stultz wrote:
> > > Ehh. Why would we want to export raw kernel internal values like
> > > jiffies and HZ?
> > > 
> > > I think the CLOCK_MONOTONIC clockid would probably be a better value to
> > > export.
> > 
> > I'll look at CLOCK_MONOTONIC clockid.  I'm more than glad to export
> > something > more appropriate, including nothing at all (dummy values,
> > perhaps).
> 
> Chris, are the current values exactly what one would get if reading /dev/time
> onPlan 9?
> If possible, it would be nice to aim for 100% compatibility as there are
> folks trying to get complete Plan 9 binary compatibility working in Linux.

On Plan 9, the last two values are architecture-dependent.
I rewrote my patch to export nanoseconds since boot and nanoseconds per
second, but either choice should be ok from the standpoint of compatibility.

I am going to rework this patch to eliminate the inconsistencies
with the Plan 9 interface.

Thanks to Jochen Vos for pointing out the error in the documentation.
I forgot to change my example to reflect the change to the code.

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