linux-kernel - Re: [PATCH 0/4] perf: add support for profiling jitted code

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]

Message-ID: <54DB8262.1090705@gmail.com>
Date:	Wed, 11 Feb 2015 09:25:06 -0700
From:	David Ahern <dsahern@...il.com>
To:	Peter Zijlstra <peterz@...radead.org>,
	Stephane Eranian <eranian@...gle.com>
CC:	LKML <linux-kernel@...r.kernel.org>,
	Arnaldo Carvalho de Melo <acme@...hat.com>,
	"mingo@...e.hu" <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>
Subject: Re: [PATCH 0/4] perf: add support for profiling jitted code

On 2/11/15 9:15 AM, Peter Zijlstra wrote:
> On Wed, Feb 11, 2015 at 08:18:37AM -0500, Stephane Eranian wrote:
>
>> But, we need a portable solution, there are jitted environment on other
>> architectures.
>
> Yeah, I'm aware of that. But the time people are not liking any of those
> patches.
>
> The thing that seems to have most traction is something like
>
>    lkml.kernel.org/r/20150211161256.GH2896@...ktop.programming.kicks-ass.net
>
> Which would basically make the trace clock be CLOCK_MONOTONIC.
>

Sure, but IF that solution is ever adopted it will apply to top of tree 
kernels. In the meantime users of long term kernels (enterprise, LTS, 
other) need to be able to use this feature.

I understand that Ingo (and probably you as well) have a disdain for the 
kernel module approach mentioned above and it is not the preferred 
approach. But given the resistance for over *4 years* to solutions to 
this problem the module does provide a solution for the existing user base.

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