This is the mail archive of the systemtap@sources.redhat.com 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] |
In order to let us decide how many of these extensibility points we need to support, we need ... drumroll ... more detailed examples. My intuition says that the basic library and translator points I marked above with [***] are sufficient for the forseeable future. notion of priviledged script tapsets located in a library
-How many times did that section of code get executed -What is the context this code is being run in? -Which process is using this resource. -Where in the user code triggered use of this resource (e.g. the syscall) -How long did it take to complete an action?
I think the list of mine you refer to above is this one:
- hardware performance counters
- power management hardware
- virtualization technologies
- strange new hardware to support multicore architectures
Unfortunately, this is not the future; the first three are happening
now, and the fourth will be with us within a year or so. Dealing with
some of these can require special libraries, linking conventions or compilation options. It's easy to imagine the compiler support for such options might be somewhat tempermental and inflexible at first.
I don't think we will understand all the implications before we commit
to a plan for tapset authoring.
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |