From: Alexei Starovoitov <alexei.starovoitov@gmail.com>
To: Anton Blanchard <anton@ozlabs.org>
Cc: davem@davemloft.net, peterz@infradead.org, mingo@redhat.com,
acme@kernel.org, alexander.shishkin@linux.intel.com,
sparclinux@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: change uprobe_events default ? Was: [PATCH] perf: Rename CONFIG_[UK]PROBE_EVENT to CONFIG_[UK]PROBE_EVENTS
Date: Wed, 15 Mar 2017 17:58:19 -0700 [thread overview]
Message-ID: <20170316005817.GA6805@ast-mbp.thefacebook.com> (raw)
In-Reply-To: <20170216060050.20866-1-anton@ozlabs.org>
On Thu, Feb 16, 2017 at 05:00:50PM +1100, Anton Blanchard wrote:
> From: Anton Blanchard <anton@samba.org>
>
> 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.
>
> Signed-off-by: Anton Blanchard <anton@samba.org>
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?
next prev parent reply other threads:[~2017-03-16 0:58 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 ` Alexei Starovoitov [this message]
2017-03-16 1:06 ` change uprobe_events default ? Was: [PATCH] perf: " 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
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=20170316005817.GA6805@ast-mbp.thefacebook.com \
--to=alexei.starovoitov@gmail.com \
--cc=acme@kernel.org \
--cc=alexander.shishkin@linux.intel.com \
--cc=anton@ozlabs.org \
--cc=davem@davemloft.net \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=sparclinux@vger.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;
as well as URLs for NNTP newsgroup(s).