From: "mjw at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: systemtap@sourceware.org
Subject: [Bug translator/13037] blacklist false positives
Date: Thu, 28 Jul 2011 08:01:00 -0000 [thread overview]
Message-ID: <bug-13037-6586-OlEYHj5EUp@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-13037-6586@http.sourceware.org/bugzilla/>
http://sourceware.org/bugzilla/show_bug.cgi?id=13037
Mark Wielaard <mjw at redhat dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |mjw at redhat dot com
--- Comment #1 from Mark Wielaard <mjw at redhat dot com> 2011-07-28 08:00:31 UTC ---
First try:
diff --git a/dwflpp.cxx b/dwflpp.cxx
index fda6afd..256b403 100644
--- a/dwflpp.cxx
+++ b/dwflpp.cxx
@@ -2986,7 +2986,9 @@ dwflpp::build_blacklist()
// Lots of locks
blfn += "|.*raw_.*lock.*";
- blfn += "|.*read_.*lock.*";
+ blfn += "|.*read_lock.*";
+ blfn += "|.*read_unlock.*";
+ blfn += "|.*read_trylock.*";
blfn += "|.*write_.*lock.*";
blfn += "|.*spin_.*lock.*";
blfn += "|.*rwlock_.*lock.*";
Which frees up the following (block and clock) functions for probing:
-ata_tf_read_block
-cdrom_read_block
-ext4_read_block_bitmap
-ext4_should_dioread_nolock
-pvclock_read_wallclock
-read_block_bitmap
-read_boot_clock
-read_persistent_clock
-read_tag_block
-sd_read_block_characteristics
-sd_read_block_limits
-thread_cpu_clock_get
-thread_cpu_clock_getres
-will_read_block
Still investigating the other [cb]lock related regexs.
--
Configure bugmail: http://sourceware.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
next prev parent reply other threads:[~2011-07-28 8:01 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-28 1:51 [Bug translator/13037] New: " fche at redhat dot com
2011-07-28 8:01 ` mjw at redhat dot com [this message]
2011-07-28 12:09 ` [Bug translator/13037] " mjw at redhat dot com
2016-05-26 17:56 ` fche at redhat dot com
2021-03-21 15:43 ` tiberiuzbirnea at gmail dot com
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=bug-13037-6586-OlEYHj5EUp@http.sourceware.org/bugzilla/ \
--to=sourceware-bugzilla@sourceware.org \
--cc=systemtap@sourceware.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).