From: "jistone at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: systemtap@sourceware.org
Subject: [Bug runtime/14179] New: Reorganize the runtime to accommodate different backends
Date: Wed, 30 May 2012 01:50:00 -0000 [thread overview]
Message-ID: <bug-14179-6586@http.sourceware.org/bugzilla/> (raw)
http://sourceware.org/bugzilla/show_bug.cgi?id=14179
Bug #: 14179
Summary: Reorganize the runtime to accommodate different
backends
Product: systemtap
Version: unspecified
Status: NEW
Severity: enhancement
Priority: P2
Component: runtime
AssignedTo: systemtap@sourceware.org
ReportedBy: jistone@redhat.com
Classification: Unclassified
In order to better support new backends, especially the dyninst backend of bug
#14178, I suggest reorganizing the layout of our runtime.
First, code that is not actually built into the script module should be
separated - namely the whole /runtime/staprun/ path. This can become its own
/staprun/ path, and the configury for this should probably be merged with the
core (since it's already interdependent code).
Then, code that is built in should be organized according to platform
dependency. So files in the base runtime/ path should be neutral code to be
included by the translator. Implementations that are specific to the Linux
kernel can go in runtime/linux/, and chosen by #ifdef __KERNEL__. Code for the
Dyninst backend can go in runtime/dyninst/.
--
Configure bugmail: http://sourceware.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
next reply other threads:[~2012-05-30 1:50 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-30 1:50 jistone at redhat dot com [this message]
2012-05-30 1:51 ` [Bug runtime/14179] " jistone 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=bug-14179-6586@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).