linux-kernel - Re: [PATCH v2] timekeeping: Added a function to return tv_sec portion of ktime_get_real

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]

Date:	Tue, 28 Oct 2014 21:31:32 +0100 (CET)
From:	Thomas Gleixner <tglx@...utronix.de>
To:	Arnd Bergmann <arnd@...db.de>
cc:	Heena Sirwani <heenasirwani@...il.com>,
	linux-kernel@...r.kernel.org, john.stultz@...aro.org
Subject: Re: [PATCH v2] timekeeping: Added a function to return tv_sec portion
 of ktime_get_real_ts64()

On Tue, 28 Oct 2014, Arnd Bergmann wrote:
> On Tuesday 28 October 2014 18:13:09 Thomas Gleixner wrote:
> I'd like to apply this patch to my y2038 branch and apply the
> other patches that need it on top, unless you want to still submit
> it for 3.18.

I think I should take these patches for 3.18. We do not create users
yet, but it makes it easier for submaintaners to apply stuff which you
convert. And it lets me have the whole core lot together with other
changes in that area. I create a seperate branch which you can pull
from.

> Regarding the names, should we then have
> 
> time64_t ktime_get_real_seconds(void);
> time64_t ktime_get_seconds(void);

I like that one. Moving all the time interfaces to a ktime_ prefix and
let the default implementation as CLOCK_MONOTONIC and the others with
the added '_real', '_boot' ... describe their CLOCK_WHATEVER property
makes it pretty clear.

Thanks,

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