linux-kernel - Re: re-adding clocksource_get

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 for Android: free password hash cracker in your pocket

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

Message-ID: <x2p1f1b08da1004091358z1d185aacya6c0fa2f55322fc7@mail.gmail.com>
Date:	Fri, 9 Apr 2010 13:58:54 -0700
From:	john stultz <johnstul@...ibm.com>
To:	Giuseppe CAVALLARO <peppe.cavallaro@...com>
Cc:	linux-kernel@...r.kernel.org
Subject: Re: re-adding clocksource_get_next ?

On Thu, Apr 8, 2010 at 11:53 PM, Giuseppe CAVALLARO
<peppe.cavallaro@...com> wrote:
> Hello!
> this function was removed in the past but I've not clear all the details.
> While testing LLTng, I wrote the patch, in attachment, that re-adds it
> again.
> The clocksource_get_next returns the first clock source available
> (without looking at the rating).
> In my environment, a clock source is a TMU channel (e.g. TMU1) and,
> indeed, clocksource_get_next works fine.

Could you provide some more details as to why you need raw access to
the clocksource, instead of using something like ktime_get(),
getrawmonotonic() or sched_clock()?

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