linux-kernel - Re: crazy idea (was: Re: [PATCH] perf tool: Carve out ctype.h et al)

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:	Mon, 30 Jun 2014 11:39:39 +0200
From:	Jean Pihet <jean.pihet@...aro.org>
To:	Borislav Petkov <bp@...en8.de>, Fu Wei <fu.wei@...aro.org>
Cc:	Robert Richter <rric@...nel.org>, Jiri Olsa <jolsa@...hat.com>,
	Arnaldo Carvalho de Melo <acme@...nel.org>,
	LKML <linux-kernel@...r.kernel.org>,
	Ingo Molnar <mingo@...nel.org>,
	Peter Zijlstra <peterz@...radead.org>,
	David Ahern <dsahern@...il.com>,
	Namhyung Kim <namhyung@...il.com>
Subject: Re: crazy idea (was: Re: [PATCH] perf tool: Carve out ctype.h et al)

Hi Boris,

-- added Fu Wei in the loop --

On 30 June 2014 09:07, Borislav Petkov <bp@...en8.de> wrote:
> On Sat, Jun 28, 2014 at 01:28:19AM +0200, Borislav Petkov wrote:
>> Ok, cool. So guys, can we apply this one so that I can continue with the
>> next round?
>
> Ok, I had this crazy idea recently:
>
> How about we copy the perf tool code we need for the RAS daemon and
> start hacking on it in a separate repo, somewhere else?
>
> This way we can start adding features and stuff and finally do some real
> work on it. The code which deals with opening a tracepoint and reading
> from it should be pretty stable by now so we won't have to sync back
> with perf too often. And if we do, we'll copy the changed bits.
>
> In the meantime, we can still work on the splitting of the kernel code
> if it is desired.
>
> In any case, I would definitely like to parallelize the work because
> if we wait for the split to happen, we won't have a RAS daemon with
> persistent events by Christmas 2050 and by then who knows whether we're
> even alive.</sarcastic joke>
>
> So what do you guys think, makes some sense at least?

That makes perfect sense since:
- we need the RAS daemon implementation soon (not just before the
final blackdown ;-),
- for other tools to exist (like RAS daemon) we need to split out the
perf code in small units. This will take a significant amount of work
and time to happen,
- the RAS daemon basically is a shrink-down perf with persistent events support.

How do we start the RAS daemon? As of today we have a prototype
implementation in C.

Fu Wei, can you confirm about the initial RAS daemon prototype?

Thx, regards,
Jean

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