linux-kernel - Re: [PATCH] tools:perf: move tools/perf/util to tools/lib/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:	Thu, 12 Jun 2014 16:01:20 +0200
From:	Borislav Petkov <bp@...en8.de>
To:	Jean Pihet <jean.pihet@...aro.org>
Cc:	Arnaldo Carvalho de Melo <acme@...nel.org>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	"linaro-kernel@...ts.linaro.org" <linaro-kernel@...ts.linaro.org>,
	Jiri Olsa <jolsa@...hat.com>, Ingo Molnar <mingo@...nel.org>,
	Robert Richter <rric@...nel.org>
Subject: Re: [PATCH] tools:perf: move tools/perf/util to tools/lib/perf_util

On Thu, Jun 12, 2014 at 03:19:50PM +0200, Jean Pihet wrote:
> The idea is to move the re-usable code in libraries, so that other
> tools than perf can use it as well.

Of course it is - didn't I say that too?

> > And I told Jean repeatedly that this needs to be splitted slowly, in
> > smaller libraries like we've been discussing it numerous times.
> Hrrr. I see it as a first move, later the rest of the code can be
> moved the same way.
> Now it seems that moving all from util/ at once is too much. How do
> you see it happening?
> 
> Note: moving some code in the perf source is hairy enough (cf. the
> simplicity of the Makefiles ;-) and so I do not want to re-do it all
> over again too many times.

You're encountering the *exact* *same* issues I was fighting with. And I
was trying to save you that work because I did that conversion a couple
of times already! And hell yeah it is a *lot* of work! And a lot of
*wasted* work at that. Except maybe the fact that it gives you a rough
idea of what needs to be done.

So, for example, looka here:

http://lkml.kernel.org/r/20140612112534.GA24194@gmail.com

Borislav Petkov (4):
      perf tools: Move u64_swap union
      tools: Unify export.h
      tools: Consolidate types.h
      perf/events/core: Drop unused variable after cleanup

4 patches dealing with more or less one thing. No more. Once they're
accepted, you do another so many. And rinse and repeat.

And I've forwarded you the mails of how we want to split them with
Ingo's and acme's thoughts.

In any case, this is the only way I know of currently, which seems to
work right now with the amount of patches going into perf tool and with
the bandwidth of reviewers.

Additionally, if you'd like, we could sync among each other on who does
what. Maybe Robert would like to help too.

HTH.

-- 
Regards/Gruss,
    Boris.

Sent from a fat crate under my desk. Formatting is fine.
--
--
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/