public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Borislav Petkov <bp@alien8.de>
To: Jiri Olsa <jolsa@redhat.com>
Cc: Arnaldo Carvalho de Melo <acme@infradead.org>,
	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: Thu, 26 Jun 2014 11:51:01 +0200	[thread overview]
Message-ID: <20140626095101.GA1284@pd.tnic> (raw)
In-Reply-To: <20140626073605.GB1177@krava.brq.redhat.com>

On Thu, Jun 26, 2014 at 09:36:05AM +0200, Jiri Olsa wrote:
> this functionality is inside evlist/evsel/target(...) objects

Yep, and that functionality depends on generic stuff which we're trying to
export first. :-)

> the ras daemon is not in tree yet is it? cant find it..

Here's an old version: http://thread.gmane.org/gmane.linux.kernel/1090275

> I think we should librarize only stuff we will share.

You sound just like acme! :-) But yeah, this is what he said at the time
and this is what we want to do - we don't want to do more work than
necessary after all :-)

> Whats the plan about the ras daemon (if I did not overlook it) to be
> put into tools?

I'd say no initially, after the kvmtool explosion last time. Which is
still ok I guess.

If it remains out of tree, we will probably have some issues if the
exported pieces change and we'll have to readjust the external code
which depends on it. We'll see.

-- 
Regards/Gruss,
    Boris.

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

  reply	other threads:[~2014-06-26  9:51 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
2014-06-26  7:36       ` Jiri Olsa
2014-06-26  9:51         ` Borislav Petkov [this message]
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=20140626095101.GA1284@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