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

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

Message-ID: <20150218182242.GC32251@gmail.com>
Date:	Wed, 18 Feb 2015 19:22:42 +0100
From:	Ingo Molnar <mingo@...nel.org>
To:	John Stultz <john.stultz@...aro.org>
Cc:	David Ahern <dsahern@...il.com>,
	Stephane Eranian <eranian@...gle.com>,
	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>,
	Adrian Hunter <adrian.hunter@...el.com>,
	Paweł Moll <mail@...elmoll.com>
Subject: Re: [PATCH v2 4/4] clock: add perf_clock posix clock


* John Stultz <john.stultz@...aro.org> wrote:

> > AFAIK Stephane is not proposing this patch for 
> > inclusion but rather it is an unfortunate necessary 
> > evil. The module exposes perf_clock (ie., local_clock) 
> > to userspace and allows in this case the generation of 
> > samples with a perf timestamp which is required for 
> > proper sorting.
> >
> > I understand this solution is not liked, but it works, 
> > requires no kernel modifications to achieve the end 
> > goal and can be used for kernels going back to at least 
> > 2.6.38 (perhaps earlier, have not checked).
> 
> Yep. And I'm sympathetic to the fact that an alternative 
> solution hasn't made it upstream yet. I'm hopeful Pawel's 
> recent approach will make it in (it seems like it hasn't 
> raised any flags w/ scheduler folks - but I've not always 
> been able to follow the discussion closely).

So if it's part of this series and reviews fine then I'll 
be happy to apply it! Nothing better than having a kernel 
patch and an actual usecase go hand in hand.

Thanks,

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