X-Git-Url: http://git.lttng.org/?a=blobdiff_plain;f=lttv%2Flttv%2Fsync%2FREADME;h=6e76ec17a24a62039d403ca7c295f7bd8ec9b546;hb=48b641c1f6320eca569b2894f253d9d815250d45;hp=ada0210b99f01ddc71a64450ea0b4fecbca17b00;hpb=bc7c054de1fd8331749c1a73bb1842caae909aa2;p=lttv.git

diff --git a/lttv/lttv/sync/README b/lttv/lttv/sync/README
index ada0210b..6e76ec17 100644
--- a/lttv/lttv/sync/README
+++ b/lttv/lttv/sync/README
@@ -192,9 +192,11 @@ This reads parameters, creates SyncState and calls the processing init
 function. The "sync chain" is the set of event-* modules. At the moment there
 is only one module at each stage. However, as more module are added, it will
 become relevant to have many modules at the same stage simultaneously. This
-will require some modifications. I've kept this possibility at the back of my
-mind while designing. It is already partly supported at the matching stage
-through encapsulation of other matching modules.
+will require some modifications. It is already partly supported at the
+matching stage through encapsulation of other matching modules.
+
+sync_chain_unitest:main() provides a fairly simple example of sync chain
+implementation.
 
 ++ Stage 1: Event processing
 Specific to the tracing data source.