Disable kprobe blacklist in guru mode.

diff --git a/NEWS b/NEWS
index 74fd1df5977be9de82c2e1c15f4d8d23e569d9cc..fff8afc910c38f5db50f971397d2a75143a5d1a6 100644 (file)
--- a/NEWS
+++ b/NEWS
@@ -1,5 +1,10 @@
 * What's new
 
+- In guru mode (-g), the kernel probing blacklist is disabled, leaving 
+  only a subset - the kernel's own internal kprobe blacklist - to attempt
+  to filter out areas unsafe to probe.  The differences may be enough to
+  probe more interrupt handlers.
+
 - Variables unavailable in current context may be skipped by setting a 
   session level flag with command line option --skip-badvars now available. 
   This will simply substitute the otherwise error causing variable with a 

diff --git a/tapsets.cxx b/tapsets.cxx
index 894a744760a67ad4becddcceb9a35fc6870f97cb..6de6271b81a3b0e458812c83f52accef7a12d596 100644 (file)
--- a/tapsets.cxx
+++ b/tapsets.cxx
@@ -3521,9 +3521,17 @@ dwarf_query::blacklisted_p(const string& funcname,
 
   if (! (goodfn && goodfile))
     {
-      if (sess.verbose>1)
-       clog << " skipping - blacklisted";
-      return true;
+      if (sess.guru_mode)
+        {
+         if (sess.verbose>1)
+           clog << " guru mode enabled - ignoring blacklist";
+        }
+      else
+        {
+         if (sess.verbose>1)
+           clog << " skipping - blacklisted";
+         return true;
+        }
     }
 
   // This probe point is not blacklisted.