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:	Thu, 29 Oct 2015 13:17:32 +0100
From:	Ingo Molnar <mingo@...nel.org>
To:	Arnaldo Carvalho de Melo <acme@...nel.org>
Cc:	linux-kernel@...r.kernel.org,
	Alexei Starovoitov <ast@...mgrid.com>,
	Brendan Gregg <brendan.d.gregg@...il.com>,
	Daniel Borkmann <daniel@...earbox.net>,
	David Ahern <dsahern@...il.com>, He Kuang <hekuang@...wei.com>,
	Jiri Olsa <jolsa@...nel.org>, Kaixu Xia <xiakaixu@...wei.com>,
	Masami Hiramatsu <masami.hiramatsu.pt@...achi.com>,
	Namhyung Kim <namhyung@...nel.org>,
	Paul Mackerras <paulus@...ba.org>,
	Peter Zijlstra <a.p.zijlstra@...llo.nl>, pi3orama@....com,
	Wang Nan <wangnan0@...wei.com>, Zefan Li <lizefan@...wei.com>,
	Arnaldo Carvalho de Melo <acme@...hat.com>
Subject: Re: [GIT PULL 0/6] perf/ebpf basic integration


* Arnaldo Carvalho de Melo <acme@...nel.org> wrote:

> Hi Ingo,
> 
> 	Please take a look at the changeset comments, I made notes in most of
> them, this seems like a nice cutoff point to allow basic testing, by
> developers, for the very basic integration of perf and ebpf, i.e. we can,
> having a ready built object file, built with clang, be able to use it as a perf
> event, passing it via -e/--event, etc.
> 
> 	Wang has lots more in the queue and I intend to work on them till I get
> all reviewed/tested/merged, i.e. in the immediate future.
> 
> 	What do you think? Fair to get his smaller gulp now? Or do you want to
> get it all the way with the code to get a .c file, build it, etc, that is
> ready, but I haven't reviewed/tested yet?
> 
> 	Ah, this is on top of what I sent to you via perf/core yesterday.

I'm fine with this, as long as this bit:

> More work is about to be reviewed, tested and merged that will allow the whole
> process of going from a .c file to an .o file via clang, etc to be done
> automagically. (Wang Nan)

... is treated as the primary interface. Very few people will use object files, so 
we need to integrate the whole life-time workflow, from instrumentation source 
code to perf output.

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/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ