public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Borislav Petkov <bp@alien8.de>
To: Arnaldo Carvalho de Melo <acme@infradead.org>
Cc: Jiri Olsa <jolsa@redhat.com>, LKML <linux-kernel@vger.kernel.org>,
	Ingo Molnar <mingo@kernel.org>,
	Peter Zijlstra <peterz@infradead.org>,
	Robert Richter <rric@kernel.org>, David Ahern <dsahern@gmail.com>,
	Namhyung Kim <namhyung@gmail.com>,
	Jean Pihet <jean.pihet@linaro.org>
Subject: Re: [PATCH] perf tool: Carve out ctype.h et al
Date: Wed, 25 Jun 2014 22:11:47 +0200	[thread overview]
Message-ID: <20140625201147.GB13845@pd.tnic> (raw)
In-Reply-To: <20140625194254.GC18773@kernel.org>

On Wed, Jun 25, 2014 at 04:42:54PM -0300, Arnaldo Carvalho de Melo wrote:
> Probably will come in a separate patchkit that is dependent on this,
> but not strictly related?

Yeah, so roughly speaking, we want to carve out the code which opens and
handles events in perf tool so that we can use it in other tools. In the
particular example with the ras daemon, we want to be able to open a
tracepoint in userspace and read from it.

We're doing this piecewise because perf tool changes too fast and I've
done a full conversion patchset a couple of times already only to
realize that it grows obsolete practically only days after sending it
out. (Btw, for that it is all your fault, of course :-P). Which makes
preparing a full patchset almost impossible.

Does this explanation make sense?

@jirka: I'll try to reproduce your build error.

Thanks.

-- 
Regards/Gruss,
    Boris.

Sent from a fat crate under my desk. Formatting is fine.
--

  reply	other threads:[~2014-06-25 20:11 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-25  9:23 [PATCH] perf tool: Carve out ctype.h et al Borislav Petkov
2014-06-25 19:25 ` Jiri Olsa
2014-06-25 19:42   ` Arnaldo Carvalho de Melo
2014-06-25 20:11     ` Borislav Petkov [this message]
2014-06-26  7:36       ` Jiri Olsa
2014-06-26  9:51         ` Borislav Petkov
2014-06-25 20:38   ` Borislav Petkov
2014-06-25 21:17     ` Arnaldo Carvalho de Melo
2014-06-25 21:21       ` Borislav Petkov
2014-06-26  7:38       ` Jiri Olsa
2014-06-26 10:32         ` Borislav Petkov
2014-06-26 12:14           ` Jiri Olsa
2014-06-27 23:28             ` Borislav Petkov
2014-07-07 20:47               ` Arnaldo Carvalho de Melo
2014-07-07 20:59                 ` Borislav Petkov
2014-07-07 21:07                 ` Jiri Olsa
2014-07-07 21:27                   ` 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=20140625201147.GB13845@pd.tnic \
    --to=bp@alien8.de \
    --cc=acme@infradead.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox