From: zhaolei@cn.fujitsu.com (Zhaolei)
Subject: [ltt-dev] Make menuconfig finery
Date: Tue, 02 Dec 2008 14:38:06 +0800 [thread overview]
Message-ID: <4934D7CE.6050502@cn.fujitsu.com> (raw)
It we don't select markers, and enter lttng's menuitem, we will
see this screen:
.config - Linux Kernel v2.6.27.7 Configuration
------------------------------------------------------------------------------
|-------------------------- Linux Trace Toolkit --------------------------|
| Arrow keys navigate the menu. <Enter> selects submenus --->. |
| Highlighted letters are hotkeys. Pressing <Y> includes, <N> excludes, |
| <M> modularizes features. Press <Esc><Esc> to exit, <?> for Help, </> |
| for Search. Legend: [*] built-in [ ] excluded <M> module < > |
| |---------------------------------------------------------------------| |
| | ^@ | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| |---------------------------------------------------------------------| |
|-------------------------------------------------------------------------|
| <Select> < Exit > < Help > |
|-------------------------------------------------------------------------|
It isn't beautiful.
We can avoid this blank screen by this patch.
Signed-off-by: Zhao Lei <zhaolei at cn.fujitsu.com>
---
ltt/Kconfig | 14 ++++----------
1 files changed, 4 insertions(+), 10 deletions(-)
diff --git a/ltt/Kconfig b/ltt/Kconfig
index 341f178..8629321 100644
--- a/ltt/Kconfig
+++ b/ltt/Kconfig
@@ -1,6 +1,4 @@
-menu "Linux Trace Toolkit"
-
-config LTT
+menuconfig LTT
bool "Linux Trace Toolkit Instrumentation Support"
depends on EXPERIMENTAL
depends on TRACEPOINTS
@@ -28,9 +26,10 @@ config LTT
please check the following address :
http://ltt.polymtl.ca
+if LTT
+
config LTT_TRACEPROBES
tristate "Compile lttng tracing probes"
- depends on LTT
default m
help
Compile lttng tracing probes, which connect to the tracepoints when
@@ -79,7 +78,6 @@ config LTT_RELAY_CHECK_RANDOM_ACCESS
config LTT_SERIALIZE
tristate "Linux Trace Toolkit Serializer"
default y
- depends on LTT
help
Library for serializing information from format string and argument
list to the trace buffers.
@@ -93,7 +91,6 @@ config LTT_MARKER_CONTROL
config LTT_TRACER
tristate "Linux Trace Toolkit Tracer"
- depends on LTT
depends on LTT_MARKER_CONTROL
default y
help
@@ -112,7 +109,6 @@ config LTT_TRACER
config LTT_ALIGNMENT
bool "Align Linux Trace Toolkit Traces"
- depends on LTT
default y if !HAVE_EFFICIENT_UNALIGNED_ACCESS
help
This option enables dynamic alignment of data in buffers. The
@@ -125,14 +121,12 @@ config LTT_ALIGNMENT
config LTT_DEBUG_EVENT_SIZE
bool "Add event size field to LTT events for tracer debugging"
- depends on LTT
default n
help
Tracer-internal option to help debugging event type encoding problems.
config LTT_VMCORE
bool "Support trace extraction from crash dump"
- depends on LTT
default y
help
If you enable this option, the Linux Trace Toolkit Tracer will
@@ -180,4 +174,4 @@ config LTT_FTRACE
function tracing while a trace is being taken. Typically used when the
surroundings of a problem has been identified in a prior trace.
-endmenu
+endif # LTT
--
1.5.5.3
next reply other threads:[~2008-12-02 6:38 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-02 6:38 Zhaolei [this message]
2008-12-02 16:31 ` Mathieu Desnoyers
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=4934D7CE.6050502@cn.fujitsu.com \
--to=zhaolei@cn.fujitsu.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