Poky Project Discussions
 help / color / mirror / Atom feed
From: Darren Hart <dvhart@linux.intel.com>
To: "poky@yoctoproject.org" <poky@yoctoproject.org>
Subject: [PATCH] linux-yocto-2.6.37: Add debugfs and ftrace features to standard ktype meta-data
Date: Mon, 03 Jan 2011 15:24:33 -0800	[thread overview]
Message-ID: <4D225AB1.7010404@linux.intel.com> (raw)

ftrace provides low impact tracing facilities and should be made
available on the main kernel - as opposed to a debug or tracing
kernel which often add enough overhead to mask subtle bugs.

These features are available on the 2.6.34 yocto kernel.

Boot and trace-cmd tested on qemux86-64.

Signed-off-by: Darren Hart <darren@dvhart.com>
CC: Bruce Ashfield <bruce.ashfield@windriver.com>
CC: Tom Zanussi <tom.zanussi@intel.com>
---
 meta/cfg/kernel-cache/features/debugfs/debugfs.cfg |    1 +
 meta/cfg/kernel-cache/features/debugfs/debugfs.scc |    1 +
 meta/cfg/kernel-cache/features/ftrace/ftrace.cfg   |    2 ++
 meta/cfg/kernel-cache/features/ftrace/ftrace.scc   |    1 +
 meta/cfg/kernel-cache/ktypes/standard/standard.scc |    4 ++++
 5 files changed, 9 insertions(+), 0 deletions(-)
 create mode 100644 meta/cfg/kernel-cache/features/debugfs/debugfs.cfg
 create mode 100644 meta/cfg/kernel-cache/features/debugfs/debugfs.scc
 create mode 100644 meta/cfg/kernel-cache/features/ftrace/ftrace.cfg
 create mode 100644 meta/cfg/kernel-cache/features/ftrace/ftrace.scc

diff --git a/meta/cfg/kernel-cache/features/debugfs/debugfs.cfg b/meta/cfg/kernel-cache/features/debugfs/debugfs.cfg
new file mode 100644
index 0000000..39c2d26
--- /dev/null
+++ b/meta/cfg/kernel-cache/features/debugfs/debugfs.cfg
@@ -0,0 +1 @@
+CONFIG_DEBUG_FS=y
diff --git a/meta/cfg/kernel-cache/features/debugfs/debugfs.scc b/meta/cfg/kernel-cache/features/debugfs/debugfs.scc
new file mode 100644
index 0000000..8f84947
--- /dev/null
+++ b/meta/cfg/kernel-cache/features/debugfs/debugfs.scc
@@ -0,0 +1 @@
+kconf non-hardware debugfs.cfg
diff --git a/meta/cfg/kernel-cache/features/ftrace/ftrace.cfg b/meta/cfg/kernel-cache/features/ftrace/ftrace.cfg
new file mode 100644
index 0000000..bab800c
--- /dev/null
+++ b/meta/cfg/kernel-cache/features/ftrace/ftrace.cfg
@@ -0,0 +1,2 @@
+CONFIG_FUNCTION_TRACER=y
+CONFIG_FUNCTION_GRAPH_TRACER=y
diff --git a/meta/cfg/kernel-cache/features/ftrace/ftrace.scc b/meta/cfg/kernel-cache/features/ftrace/ftrace.scc
new file mode 100644
index 0000000..c92e30f
--- /dev/null
+++ b/meta/cfg/kernel-cache/features/ftrace/ftrace.scc
@@ -0,0 +1 @@
+kconf non-hardware ftrace.cfg
diff --git a/meta/cfg/kernel-cache/ktypes/standard/standard.scc b/meta/cfg/kernel-cache/ktypes/standard/standard.scc
index 9fa6c1e..8212465 100644
--- a/meta/cfg/kernel-cache/ktypes/standard/standard.scc
+++ b/meta/cfg/kernel-cache/ktypes/standard/standard.scc
@@ -33,6 +33,10 @@ tag powerpc
 
 include features/hrt/hrt.scc
 
+include features/debugfs/debugfs.scc
+
+include features/ftrace/ftrace.scc
+
 include patches/wrs_patches.scc
 
 # #include features/ieee_float/ieee_float.scc
-- 
1.7.1
-- 
Darren Hart
Yocto Linux Kernel


             reply	other threads:[~2011-01-03 23:24 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-01-03 23:24 Darren Hart [this message]
2011-01-04 20:51 ` [PATCH] linux-yocto-2.6.37: Add debugfs and ftrace features to standard ktype meta-data Bruce Ashfield

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=4D225AB1.7010404@linux.intel.com \
    --to=dvhart@linux.intel.com \
    --cc=poky@yoctoproject.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