Mirror of the lttng-dev mailing list
 help / color / mirror / Atom feed
From: jonathan.rajotte-julien@efficios.com (Jonathan Rajotte)
Subject: [lttng-dev] [PATCH v2 lttng-ust 2/2] Doc: add LTTNG_UST_CLOCK_PLUGIN to man page
Date: Thu, 23 Jul 2015 16:02:51 -0400	[thread overview]
Message-ID: <1437681771-7495-2-git-send-email-jonathan.rajotte-julien@efficios.com> (raw)
In-Reply-To: <1437681771-7495-1-git-send-email-jonathan.rajotte-julien@efficios.com>

Also add indications on how to use the plugin with lttng-tools.

Signed-off-by: Jonathan Rajotte <jonathan.rajotte-julien at efficios.com>
---
 doc/examples/clock-override/README | 4 ++++
 doc/man/lttng-ust.3                | 5 +++++
 2 files changed, 9 insertions(+)

diff --git a/doc/examples/clock-override/README b/doc/examples/clock-override/README
index e3ddf22..aabbee2 100644
--- a/doc/examples/clock-override/README
+++ b/doc/examples/clock-override/README
@@ -2,3 +2,7 @@ This clock override example shows how to implement and load a clock
 override plugin for LTTng-UST. This can be useful in cases where direct
 hardware access is available for architecture-specific clocks, and where
 it should be used rather than the Linux kernel Monotonic clock.
+
+When using LTTng-tools keep in mind that lttng-sessiond uses lttng-ust's clock
+definition and functions. Thus LTTNG_UST_CLOCK_PLUGIN needs to be defined when
+launching lttng-sessiond.
diff --git a/doc/man/lttng-ust.3 b/doc/man/lttng-ust.3
index e66ab88..8b399aa 100644
--- a/doc/man/lttng-ust.3
+++ b/doc/man/lttng-ust.3
@@ -502,6 +502,11 @@ Used by the getcpu override plugin system. The environment variable
 provides the path to the shared object which will act as the getcpu override
 plugin. An example can be found under doc/examples/getcpu-override .
 .PP
+.IP "LTTNG_UST_CLOCK_PLUGIN"
+Used by the clock override plugin system. The environment variable
+provides the path to the shared object wich will act as the clock override
+plugin. An example can be found under doc/examples/clock-override .
+.PP
 
 .SH "SEE ALSO"
 
-- 
2.1.4




  reply	other threads:[~2015-07-23 20:02 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-23 17:59 [lttng-dev] [PATCH lttng-ust 1/2] Doc: add LTTNG_UST_GETCPU_PLUGIN " Jonathan Rajotte
2015-07-23 17:59 ` [lttng-dev] [PATCH lttng-ust 2/2] Doc: add LTTNG_UST_CLOCK_PLUGIN " Jonathan Rajotte
2015-07-23 19:37   ` Antoine Busque
2015-07-23 19:32 ` [lttng-dev] [PATCH lttng-ust 1/2] Doc: add LTTNG_UST_GETCPU_PLUGIN " Antoine Busque
2015-07-23 20:02 ` [lttng-dev] [PATCH v2 " Jonathan Rajotte
2015-07-23 20:02   ` Jonathan Rajotte [this message]
2015-07-24  2:22     ` [lttng-dev] [PATCH v2 lttng-ust 2/2] Doc: add LTTNG_UST_CLOCK_PLUGIN " Mathieu Desnoyers

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=1437681771-7495-2-git-send-email-jonathan.rajotte-julien@efficios.com \
    --to=jonathan.rajotte-julien@efficios.com \
    /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