From: Ingo Molnar <mingo@kernel.org>
To: Arnaldo Carvalho de Melo <acme@ghostprotocols.net>
Cc: Darren Hart <dvhart@linux.intel.com>,
Hitoshi Mitake <h.mitake@gmail.com>, Ingo Molnar <mingo@elte.hu>,
linux-kernel@vger.kernel.org,
Peter Zijlstra <a.p.zijlstra@chello.nl>,
Paul Mackerras <paulus@samba.org>,
Michel Lespinasse <walken@google.com>,
Rusty Russell <rusty@rustcorp.com.au>,
Eric Dumazet <eric.dumazet@gmail.com>
Subject: Re: [PATCH] perf bench: add new benchmark subsystem and suite "futex wait"
Date: Wed, 6 Jun 2012 17:37:15 +0200 [thread overview]
Message-ID: <20120606153715.GA7842@gmail.com> (raw)
In-Reply-To: <20120606123023.GB2423@infradead.org>
* Arnaldo Carvalho de Melo <acme@ghostprotocols.net> wrote:
> Em Wed, Jun 06, 2012 at 09:39:09AM +0200, Ingo Molnar escreveu:
> > I'd rather not split it from the main perf binary, if embedded
> > wants a small static binary (do they really?) we could add
> > support for minimal builds of perf, with just a few [even one]
> > subcommand activated or so.
>
> The plan is to be able to do a:
>
> make -C tools/perf menuconfig
>
> And all the other *config make targets as the kernel, using Kconfig
> files, etc.
>
> So that we can pick and choose which subset of tools and features one
> wants.
Sounds very nifty to me!
Thanks,
Ingo
next prev parent reply other threads:[~2012-06-06 15:37 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-17 15:21 [PATCH] perf bench: add new benchmark subsystem and suite "futex wait" Hitoshi Mitake
2012-05-17 16:24 ` Darren Hart
2012-05-20 8:32 ` Hitoshi Mitake
2012-05-20 9:37 ` Hitoshi Mitake
2012-06-05 18:17 ` Darren Hart
2012-06-06 7:39 ` Ingo Molnar
2012-06-06 12:30 ` Arnaldo Carvalho de Melo
2012-06-06 15:37 ` Ingo Molnar [this message]
2012-06-06 14:18 ` David Ahern
2012-06-06 16:02 ` Hitoshi Mitake
2012-06-07 15:11 ` Hitoshi Mitake
2012-06-13 16:51 ` Darren Hart
2012-06-24 16:08 ` Hitoshi Mitake
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=20120606153715.GA7842@gmail.com \
--to=mingo@kernel.org \
--cc=a.p.zijlstra@chello.nl \
--cc=acme@ghostprotocols.net \
--cc=dvhart@linux.intel.com \
--cc=eric.dumazet@gmail.com \
--cc=h.mitake@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=paulus@samba.org \
--cc=rusty@rustcorp.com.au \
--cc=walken@google.com \
/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