This is the mail archive of the systemtap@sourceware.org mailing list for the systemtap project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

[Bug runtime/14179] New: Reorganize the runtime to accommodate different backends


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.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]