From: Arnaldo Carvalho de Melo <acme@kernel.org>
To: Ingo Molnar <mingo@kernel.org>
Cc: Alexei Starovoitov <alexei.starovoitov@gmail.com>,
Anton Blanchard <anton@ozlabs.org>,
David Miller <davem@davemloft.net>,
Peter Zijlstra <peterz@infradead.org>,
Hemant Kumar <hemant@linux.vnet.ibm.com>,
Masami Hiramatsu <mhiramat@kernel.org>,
Steven Rostedt <rostedt@goodmis.org>,
Srikar Dronamraju <srikar@linux.vnet.ibm.com>,
Wang Nan <wangnan0@huawei.com>,
Namhyung Kim <namhyung@kernel.org>,
David Ahern <dsahern@gmail.com>, Jiri Olsa <jolsa@kernel.org>,
alexander.shishkin@linux.intel.com, sparclinux@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: change uprobe_events default ? Was: [PATCH] perf: Rename CONFIG_[UK]PROBE_EVENT to CONFIG_[UK]PROBE_EVENTS
Date: Thu, 16 Mar 2017 09:31:54 -0300 [thread overview]
Message-ID: <20170316123154.GT12825@kernel.org> (raw)
In-Reply-To: <20170316064055.GA7130@gmail.com>
Em Thu, Mar 16, 2017 at 07:40:55AM +0100, Ingo Molnar escreveu:
>
> * Arnaldo Carvalho de Melo <acme@kernel.org> wrote:
>
> > Added more people to the CC list.
> >
> > Em Wed, Mar 15, 2017 at 05:58:19PM -0700, Alexei Starovoitov escreveu:
> > > On Thu, Feb 16, 2017 at 05:00:50PM +1100, Anton Blanchard wrote:
> > > > We have uses of CONFIG_UPROBE_EVENT and CONFIG_KPROBE_EVENT as
> > > > well as CONFIG_UPROBE_EVENTS and CONFIG_KPROBE_EVENTS. Consistently
> > > > use the plurals.
> >
> > > this rename made me notice that UPROBE_EVENTS still defaults to 'n'.
> > > this is key feature that all distros enable, so having default 'n'
> > > is kinda saying that it's not something that should be turned on
> > > or used widely. which is obviously not the case.
> > > imo it's time to change it to 'y'.
> > > Thoughts?
> >
> > Agreed, I also found it strange that it was disabled by default when I
> > recently did a 'make oldconfig' :-\
>
> Agreed, someone please send a patch (or feel free to include it in the perf
> tooling tree) to switch the default around.
Ok, will collect the agreements as Acked-by tags and put it in
perf/core.
- Arnaldo
next prev parent reply other threads:[~2017-03-16 12:32 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-16 6:00 [PATCH] perf: Rename CONFIG_[UK]PROBE_EVENT to CONFIG_[UK]PROBE_EVENTS Anton Blanchard
2017-03-01 9:48 ` [tip:perf/urgent] perf/core: " tip-bot for Anton Blanchard
2017-03-16 0:58 ` change uprobe_events default ? Was: [PATCH] perf: " Alexei Starovoitov
2017-03-16 1:06 ` Arnaldo Carvalho de Melo
2017-03-16 1:10 ` David Ahern
2017-03-16 2:17 ` Namhyung Kim
2017-03-16 5:34 ` Srikar Dronamraju
2017-03-16 5:46 ` Wangnan (F)
2017-03-16 6:40 ` Ingo Molnar
2017-03-16 12:31 ` Arnaldo Carvalho de Melo [this message]
2017-03-16 7:42 ` Masami Hiramatsu
2017-03-16 16:37 ` [tip:perf/core] uprobes: Default UPROBES_EVENTS to Y tip-bot for Arnaldo Carvalho de Melo
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=20170316123154.GT12825@kernel.org \
--to=acme@kernel.org \
--cc=alexander.shishkin@linux.intel.com \
--cc=alexei.starovoitov@gmail.com \
--cc=anton@ozlabs.org \
--cc=davem@davemloft.net \
--cc=dsahern@gmail.com \
--cc=hemant@linux.vnet.ibm.com \
--cc=jolsa@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mhiramat@kernel.org \
--cc=mingo@kernel.org \
--cc=namhyung@kernel.org \
--cc=peterz@infradead.org \
--cc=rostedt@goodmis.org \
--cc=sparclinux@vger.kernel.org \
--cc=srikar@linux.vnet.ibm.com \
--cc=wangnan0@huawei.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;
as well as URLs for NNTP newsgroup(s).