From: "fche at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: systemtap@sources.redhat.com
Subject: [Bug translator/3498] improve offline processing speed by predicate fn
Date: Tue, 20 May 2008 22:36:00 -0000 [thread overview]
Message-ID: <20080520203233.20285.qmail@sourceware.org> (raw)
In-Reply-To: <20061109181920.3498.fche@redhat.com>
------- Additional Comments From fche at redhat dot com 2008-05-20 20:32 -------
One possible approach is to break the derivation process between the
probe-point matcher tree and the actual derived_foo_builder::build
calls, by storing in the session a vector of deferred-build calls.
Perhaps it should be rolled into the derived_probe_group class
structure. (This may also be a better place/time to handle listings.)
Once all the probes have been resolved to builders, they'd actually
start getting build calls. The dwarf builder can search the
deferred-builder queue for all the other occurrences of kernel.* and
module("*").*, and thus customize a good filter predicate for
dwfl_linux_kernel_report_offline().
--
What |Removed |Added
----------------------------------------------------------------------------
AssignedTo|fche at redhat dot com |systemtap at sources dot
| |redhat dot com
Status|NEW |ASSIGNED
http://sourceware.org/bugzilla/show_bug.cgi?id=3498
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
next parent reply other threads:[~2008-05-20 20:33 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20061109181920.3498.fche@redhat.com>
2008-05-20 22:36 ` fche at redhat dot com [this message]
2008-07-08 19:26 ` [Bug translator/3498] split pass-2 into wildcard/alias-expanded derived_probe_group pending work fche at redhat dot com
2008-07-08 19:31 ` fche at redhat dot com
2009-04-17 16:03 ` [Bug translator/3498] speed up pass-2: split at wildcard-expansion ||| match_node::build; compute tight elfutils report_..._offline predicate fche at redhat dot com
2009-07-07 18:34 ` fche at redhat 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=20080520203233.20285.qmail@sourceware.org \
--to=sourceware-bugzilla@sourceware.org \
--cc=systemtap@sources.redhat.com \
/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).