linux-kernel - Re: [PATCH 2/7] timekeeping: Provide new API to get the current time resolution

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:	Wed, 20 May 2015 20:55:45 +0200
From:	Harald Geyer <harald@...ib.org>
To:	John Stultz <john.stultz@...aro.org>
cc:	LKML <linux-kernel@...r.kernel.org>,
	Thomas Gleixner <tglx@...utronix.de>,
	Ingo Molnar <mingo@...nel.org>
Subject: Re: [PATCH 2/7] timekeeping: Provide new API to get the current time resolution

John Stultz writes:
> > I was thinking that the variable hrtimer_resolution, that Thomas
> > introduced in
> > https://git.kernel.org/cgit/linux/kernel/git/tip/tip.git/commit/include/linux/hrtimer.h?h=timers/wip&id=03eeacdb07e2fdfc4ef311c2593286c92eba609c
> > is meant to provide the same information. I haven't looked into this
> > in detail yet, so I might be wrong, but it is on my todo list for
> > after it appears in the trees I work with...
> 
> Well, I don't think the above covers the same usage, since one is the
> hrtimer resolution (which we expose to userspace via the posix timers
> interface) vs the timekeeping/clocksource resolution (which we don't
> intend to expose to userspace).

Ok, hrtimer resolution is not updated when we change clocksource.
Seems like I misinterpreted something when I read the series.

> That said, if you're not sure if this patch is still necessary, I'm
> happy to drop it, since your iio code was the only potential user so
> far.  :)

Looks like my patch is still needed... :(

Thanks,
Harald
--
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/