A configure option is needed, suggested is "--enable-lttng-support". This will
enable all tracepoints in both libraries and server parts and create a
build/runtime dependency to lttng. The default is OFF.
A requirement is to be able to specify the PROVIDER for library tracepoints.
The suggestion is to export environment variable "OSAF_LIB_TRACEPOINT_PROVIDER"
before running configure. The default could be "org_opensaf" if not set.
Tracepoints in libraries:
We need to trace the duration of a lib call thus some kind of enter/leave is
needed. In Anders patch he had for example "saAmfResponse" and
"saAmfResponse_result" which would satisfy that req.
Errors occuring is traced with "saAmfResponse_result" thus no distinction
between a normal return and an error return. I think we should use loglevels in
lttng and have something like "saAmfResponse_enter" and "saAmfResponse_leave"
at DEBUG and "saAmfResponse_error" at ERROR
To be continued...
---
** [tickets:#454] osaf: Integration with LTTng-UST**
**Status:** unassigned
**Created:** Wed Jun 12, 2013 11:28 AM UTC by Anders Widell
**Last Updated:** Sat Sep 07, 2013 03:28 PM UTC
**Owner:** nobody
Migrated from <http://devel.opensaf.org/ticket/2809>
References:
<http://lttng.org/files/doc/man-pages/man3/lttng-ust.3.html>
<http://lttng.org/ust>
Requirements (to be discussed):
- Add tracepoints for SAF AIS APIs in the following priority order: IMM, AMF,
CKPT, SMF, NTF, ..
- Tracepoints are added in the shared libraries
- Some tracepoints should be added in the server processes, some in this case
means error handling/validation of API parameters
(- opensaf internal implementation tracing is a next step)
- Default provider name should be "org_opensaf"
- Provider name should be changeable at compile time
- LTTng-UST support should be optional, either the added tracepoints becomes
nops or are converted to some other backend (e.g. file like in the current
trace system)
- Tracepoint name should be e.g. "ais_imm_om_ccbapply",
"ais_amf_componentregister"
- API parameters should be traced, especially unique things like DNs, CCBID etc
- A downcall (such as saAmfComponentRegister) should be traced with two trace
points, one for the request and one for the response, they need names with a
suffix something like a _req and _resp
- A callback with a void return value (such as SaAmfCSISetCallbackT) should be
traced with one tracepoint
- A callback with a non void return value (such as saImmOiObjectCallbackT)
should be traced with two tracepoints
- the server should use the same tracepoint name for parameter validation, with
such change the use of syslog for invalid parameters can be removed.
- ...
---
Sent from sourceforge.net because [email protected] is
subscribed to https://sourceforge.net/p/opensaf/tickets/
To unsubscribe from further messages, a project admin can change settings at
https://sourceforge.net/p/opensaf/admin/tickets/options. Or, if this is a
mailing list, you can unsubscribe from the mailing list.
------------------------------------------------------------------------------
October Webinars: Code for Performance
Free Intel webinars can help you accelerate application performance.
Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most from
the latest Intel processors and coprocessors. See abstracts and register >
http://pubads.g.doubleclick.net/gampad/clk?id=60134791&iu=/4140/ostg.clktrk
_______________________________________________
Opensaf-tickets mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/opensaf-tickets
