linux-kernel - Re: [PATCHv2 00/36] perf tools: New build framework

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: <20150115163110.GE17228@krava.brq.redhat.com>
Date:	Thu, 15 Jan 2015 17:31:10 +0100
From:	Jiri Olsa <jolsa@...hat.com>
To:	David Ahern <dsahern@...il.com>
Cc:	Jiri Olsa <jolsa@...nel.org>, linux-kernel@...r.kernel.org,
	Adrian Hunter <adrian.hunter@...el.com>,
	Alexis Berlemont <alexis.berlemont@...il.com>,
	Andi Kleen <ak@...ux.intel.com>,
	Anton Blanchard <anton@...ba.org>,
	Arnaldo Carvalho de Melo <acme@...hat.com>,
	Borislav Petkov <bp@...en8.de>, Borislav Petkov <bp@...e.de>,
	Cody P Schafer <cody@...ux.vnet.ibm.com>,
	Corey Ashford <cjashfor@...ux.vnet.ibm.com>,
	Florian Fainelli <florian@...nwrt.org>,
	Frederic Weisbecker <fweisbec@...il.com>,
	Ingo Molnar <mingo@...nel.org>,
	Jean Pihet <jean.pihet@...aro.org>,
	Mark Salter <msalter@...hat.com>,
	Namhyung Kim <namhyung@...nel.org>,
	Paul Mackerras <paulus@...ba.org>,
	Peter Zijlstra <peterz@...radead.org>,
	"S. Lockwood-Childs" <sjl@...labs.com>,
	Sam Ravnborg <sam@...nborg.org>,
	Sasha Levin <sasha.levin@...cle.com>,
	Stephane Eranian <eranian@...gle.com>,
	Steven Rostedt <rostedt@...dmis.org>,
	Sukadev Bhattiprolu <sukadev@...ux.vnet.ibm.com>,
	Will Deacon <will.deacon@....com>
Subject: Re: [PATCHv2 00/36] perf tools: New build framework

On Thu, Jan 15, 2015 at 09:08:00AM -0700, David Ahern wrote:
> On 1/15/15 5:54 AM, Jiri Olsa wrote:
> >Since it's actually small portion of kbuild that perf needs,
> >I realized it's actually better to steal it than 'reconfigure'
> >kbuild to be usable for perf.
> >
> >Also this patchset is kind of incremental version of the latest:
> >   perf tools: Add kbuild support into Makefile.kbuild
> >so it should be easier to review.
> >
> >NOTE I couldn't find any copyright/credit messages in the kbuild
> >system, but would be happy to include it if someone suggests one.
> >
> >The stolen parts are in files:
> >   Makefile.kbuild
> >   Build.include
> >
> >The idea and more details are explained in the 'Documentation/Build'
> >file. The basic idea is the same as in kbuild system, with some minor
> >changes to allow for multiple binaries build definitions.
> >
> >User provides 'Build' files with objects definitions like:
> >   perf-y += perf.o
> >   perf-y += builtin-bench.o
> >   ...
> >
> >   libperf-y += util/
> >   ...
> >
> 
> It is not obvious to me how this works. Users provide a .config file for
> building perf? Or do users provide Build files like you state above? If it
> is a .config file then what if a .config file is not present is it auto
> generated using the current autoprobing?

so far users provide 'Build' files, which defines list of objects
to be built for specific outputs, like following Build file:

---
perf-y += perf.o
perf-y += builtin-bench.o

libperf-y += util/
---

means that build framework's output will be 2 files:

  - 'perf-in.o'    that contains (links) perf.o and builtin-bench.o objects
  - 'libperf-in.o' that contains (links) whatever is defined under 'util/'


also user can provide '.config-detected' file that will get included
into the Makefile.build to get the environment changed and refer to it
in the 'Build' files

I'll update docs with more details..

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