From 3389a622d0e086fbda79db4f561af244a5f0ea16 Mon Sep 17 00:00:00 2001
From: ddomingo <ddomingo@redhat.com>
Date: Tue, 23 Sep 2008 13:05:18 +1000
Subject: committing

---
 .../en-US/Understanding_How_SystemTap_Works.xml                      | 5 ++++-
 1 file changed, 4 insertions(+), 1 deletion(-)

(limited to 'doc/SystemTap_Beginners_Guide/en-US')

diff --git a/doc/SystemTap_Beginners_Guide/en-US/Understanding_How_SystemTap_Works.xml b/doc/SystemTap_Beginners_Guide/en-US/Understanding_How_SystemTap_Works.xml
index c3fc0d9d..2794901c 100644
--- a/doc/SystemTap_Beginners_Guide/en-US/Understanding_How_SystemTap_Works.xml
+++ b/doc/SystemTap_Beginners_Guide/en-US/Understanding_How_SystemTap_Works.xml
@@ -32,7 +32,10 @@
 			
 <procedure id="systemtapsession">
 	<title>SystemTap Session</title>
-	<step><para>SystemTap first translates the script to C, running the system C compiler to create a kernel module from it.</para></step>
+	
+	<step><para>First, SystemTap checks the script against the existing tapset library (normally in <filename>/usr/share/systemtap/tapset/</filename> for any tapsets used.</para></step>
+	
+	<step><para>SystemTap then translates the script to C, running the system C compiler to create a kernel module from it.</para></step>
 	
 	<step><para>SystemTap loads the module, then enables all the probed events by "hooking" those events into the kernel.</para></step>
 		
-- 
cgit