From: Ingo Molnar <mingo@elte.hu>
To: Masami Hiramatsu <mhiramat@redhat.com>
Cc: lkml <linux-kernel@vger.kernel.org>,
systemtap <systemtap@sources.redhat.com>,
DLE <dle-develop@lists.sourceforge.net>,
Dieter Ries <mail@dieterries.net>,
Ananth N Mavinakayanahalli <ananth@in.ibm.com>
Subject: Re: [PATCH -tip 1/3] kprobes: Hide CONFIG_OPTPROBES and set if arch support optimized kprobes
Date: Sat, 13 Mar 2010 08:27:38 +0100 [thread overview]
Message-ID: <20100313072738.GB4892@elte.hu> (raw)
In-Reply-To: <20100312232208.2017.55337.stgit@localhost6.localdomain6>
* Masami Hiramatsu <mhiramat@redhat.com> wrote:
> config OPTPROBES
> - bool "Kprobes jump optimization support (EXPERIMENTAL)"
> - default y
> - depends on KPROBES
> + def_bool y
> + depends on KPROBES && HAVE_OPTPROBES
> depends on !PREEMPT
> - depends on HAVE_OPTPROBES
> select KALLSYMS_ALL
> help
> This option will allow kprobes to optimize breakpoint to
The help text can be removed too, now that it's not interactive. Also, i'd
suggest to add a comment that this just relays HAVE_OPTPROBES now, set by the
arch.
Ingo
next prev parent reply other threads:[~2010-03-13 7:28 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-12 23:22 Masami Hiramatsu
2010-03-12 23:22 ` [PATCH -tip 2/3] [BUGFIX] perf probe: Fix probe_point buffer overrun Masami Hiramatsu
2010-03-13 12:26 ` [tip:perf/urgent] " tip-bot for Masami Hiramatsu
2010-03-12 23:22 ` [PATCH -tip 3/3] [BUGFIX] perf probe: Set need_dwarf if lazy matching is used Masami Hiramatsu
2010-03-13 12:26 ` [tip:perf/urgent] perf probe: Fix need_dwarf flag " tip-bot for Masami Hiramatsu
2010-03-13 7:27 ` Ingo Molnar [this message]
2010-03-15 17:00 ` [PATCH -tip v3] kprobes: Hide CONFIG_OPTPROBES and set if arch support optimized kprobes Masami Hiramatsu
2010-03-16 14:47 ` [tip:perf/core] kprobes: Hide CONFIG_OPTPROBES and set if arch supports " tip-bot for Masami Hiramatsu
2010-03-14 0:15 ` [PATCH -tip 1/3] kprobes: Hide CONFIG_OPTPROBES and set if arch support " OGAWA Hirofumi
2010-03-14 2:05 ` Masami Hiramatsu
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=20100313072738.GB4892@elte.hu \
--to=mingo@elte.hu \
--cc=ananth@in.ibm.com \
--cc=dle-develop@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=mail@dieterries.net \
--cc=mhiramat@redhat.com \
--cc=systemtap@sources.redhat.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
all inboxes | Powered by JetHome®