+config LTT+ bool "Linux Trace Toolkit support"+ depends on RELAYFS_FS=y+ default n+ ---help---+ It is possible for the kernel to log important events to a trace+ facility. Doing so, enables the use of the generated traces in order+ to reconstruct the dynamic behavior of the kernel, and hence the+ whole system.++ The tracing process contains 4 parts :+ 1) The logging of events by key parts of the kernel.+ 2) The tracer that keeps the events in a data buffer (uses+ relayfs).+ 3) A trace daemon that interacts with the tracer and is+ notified every time there is a certain quantity of data to+ read from the tracer.+ 4) A trace event data decoder that reads the accumulated data+ and formats it in a human-readable format.++ If you say Y, the first two components will be built into the kernel.+ Critical parts of the kernel will call upon the kernel tracing+ function. The data is then recorded by the tracer if a trace daemon+ is running in user-space and has issued a "start" command.++ In order to enable LTT support you must first select relayfs as+ built-in.++ For more information on kernel tracing, the trace daemon or the event+ decoder, please check the following address :+ http://www.opersys.com/ltt+ config SHMEM default y bool "Use full shmem filesystem" if EMBEDDED && MMU--- linux-2.6.10-relayfs/kernel/Makefile 2004-12-24 16:34:26.000000000 -0500+++ linux-2.6.10-relayfs-ltt/kernel/Makefile 2005-01-13 22:21:56.000000000 -0500@@ -17,6 +17,7 @@ obj-$(CONFIG_MODULES) += module.o obj-$(CONFIG_KALLSYMS) += kallsyms.o obj-$(CONFIG_PM) += power/ obj-$(CONFIG_BSD_PROCESS_ACCT) += acct.o+obj-$(CONFIG_LTT) += ltt-core.o obj-$(CONFIG_COMPAT) += compat.o obj-$(CONFIG_IKCONFIG) += configs.o obj-$(CONFIG_IKCONFIG_PROC) += configs.o--- linux-2.6.10-relayfs/MAINTAINERS 2004-12-24 16:35:00.000000000 -0500+++ linux-2.6.10-relayfs-ltt/MAINTAINERS 2005-01-13 22:21:56.000000000 -0500@@ -1363,6 +1363,13 @@ L: linux-security-module@wirex.com W: http://lsm.immunix.org S: Supported