From: Borislav Petkov <bp@alien8.de>
To: Robert Richter <rric@kernel.org>, Jean Pihet <jean.pihet@linaro.org>
Cc: Jiri Olsa <jolsa@redhat.com>,
Arnaldo Carvalho de Melo <acme@kernel.org>,
LKML <linux-kernel@vger.kernel.org>,
Ingo Molnar <mingo@kernel.org>,
Peter Zijlstra <peterz@infradead.org>,
David Ahern <dsahern@gmail.com>,
Namhyung Kim <namhyung@gmail.com>
Subject: crazy idea (was: Re: [PATCH] perf tool: Carve out ctype.h et al)
Date: Mon, 30 Jun 2014 09:07:55 +0200 [thread overview]
Message-ID: <20140630070755.GA4766@pd.tnic> (raw)
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?
--
Regards/Gruss,
Boris.
Sent from a fat crate under my desk. Formatting is fine.
--
next reply other threads:[~2014-06-30 7:08 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-30 7:07 Borislav Petkov [this message]
2014-06-30 9:39 ` crazy idea (was: Re: [PATCH] perf tool: Carve out ctype.h et al) Jean Pihet
2014-06-30 10:01 ` Borislav Petkov
2014-06-30 14:50 ` Robert Richter
2014-06-30 14:58 ` Arnaldo Carvalho de Melo
2014-06-30 15:18 ` Borislav Petkov
2014-06-30 19:28 ` Arnaldo Carvalho de Melo
2014-06-30 19:39 ` Borislav Petkov
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20140630070755.GA4766@pd.tnic \
--to=bp@alien8.de \
--cc=acme@kernel.org \
--cc=dsahern@gmail.com \
--cc=jean.pihet@linaro.org \
--cc=jolsa@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=namhyung@gmail.com \
--cc=peterz@infradead.org \
--cc=rric@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.