linux-kernel - Re: [PATCH v2 4/4] clock: add perf

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, 18 Feb 2015 10:15:26 -0800
From:	John Stultz <john.stultz@...aro.org>
To:	Stephane Eranian <eranian@...gle.com>
Cc:	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	Arnaldo Carvalho de Melo <acme@...hat.com>,
	Peter Zijlstra <peterz@...radead.org>,
	Ingo Molnar <mingo@...e.hu>,
	"ak@...ux.intel.com" <ak@...ux.intel.com>,
	Jiri Olsa <jolsa@...hat.com>,
	Namhyung Kim <namhyung@...nel.org>,
	Rose Belcher <cel@...ibm.com>,
	Sukadev Bhattiprolu <sukadev@...ux.vnet.ibm.com>,
	Sonny Rao <sonnyrao@...omium.org>,
	John Mccutchan <johnmccutchan@...gle.com>,
	David Ahern <dsahern@...il.com>,
	Adrian Hunter <adrian.hunter@...el.com>,
	Pawel Moll <pawell.moll@....com>
Subject: Re: [PATCH v2 4/4] clock: add perf_clock posix clock

On Wed, Feb 18, 2015 at 10:10 AM, Stephane Eranian <eranian@...gle.com> wrote:
> On Wed, Feb 18, 2015 at 1:00 PM, John Stultz <john.stultz@...aro.org> wrote:
>> On Wed, Feb 18, 2015 at 9:21 AM, Stephane Eranian <eranian@...gle.com> wrote:
>>> This patch is a re-packaging of David's Ahern
>>> posix perf clock available here:
>>>
>>>         https://github.com/dsahern/linux/blob/perf-full-monty/README.ahern
>>>
>>> The patch itself is based on Pawel Moll's original post:
>>>
>>>         https://lkml.org/lkml/2013/3/14/523
>>>
>>> The new clock is call PERF_CLOCK. To use it
>>>
>>>         #include <time.h>
>>>         #include <linux/time.h>
>>>
>>>         struct timespec ts;
>>>
>>>         clock_gettime(PERF_CLOCK, &ts);
>>
>> I'd still strongly recommend against exposing the perf clock to
>> userspace this way.  The time domain isn't clearly different from
>> something like CLOCK_MONOTONIC_RAW and doesn't really have well
>> defined behavior. We're just exporting "whatever the kernel does
>> internally" to userspace, and in the past similar internal use clocks
>> like the sched_clock have changed their behavior, so I'm not confident
>> the perf clock is really baked enough (including cross architectures)
>> to make it part of the ABI.
>>
>> Pawel and others have continued to work on other approaches that allow
>> for perf events to be interpolated to, or use CLOCK_MONOTONIC itself,
>> which I don't object to, so you might want to follow up on those?
>>
> Personally, I don't have a preference. I want something that is EASY to
> correlate to the perf_events timestamp and that is PORTABLE across
> architectures. Where is the patch that uses CLOCK_MONOTONIC?
> I assume it changes the clock used by perf_events and I further assume
> this clock can be read from NMI context (without requiring locking).

I believe it can be found here:
https://lkml.org/lkml/2015/1/21/711

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/