X-Git-Url: https://git.liburcu.org/?a=blobdiff_plain;f=2.9%2Flttng-docs-2.9.txt;h=7fe1dbe9c24520b9adb689dff39696b3df33bcf6;hb=35df69388ff1fdf8a57e81832f64fb1fc132054c;hp=36f4963bb0475f5e6e9ad37b52d945ca7d6eedaf;hpb=310431f4f33a67ffa4523cd928571b8225c40462;p=lttng-docs.git diff --git a/2.9/lttng-docs-2.9.txt b/2.9/lttng-docs-2.9.txt index 36f4963..7fe1dbe 100644 --- a/2.9/lttng-docs-2.9.txt +++ b/2.9/lttng-docs-2.9.txt @@ -1,7 +1,7 @@ The LTTng Documentation ======================= Philippe Proulx -v2.9, 25 July 2017 +v2.9, 22 January 2018 include::../common/copyright.txt[] @@ -340,12 +340,12 @@ but note that: applications. [role="growable"] -.Availability of LTTng{nbsp}{revision} for major Linux distributions as of 25 July 2017. +.Availability of LTTng{nbsp}{revision} for major Linux distributions as of 22 January 2018. |==== |Distribution |Available in releases |Alternatives |https://www.ubuntu.com/[Ubuntu] -|<>. +|<>. Ubuntu{nbsp}14.04 _Trusty Tahr_ and Ubuntu{nbsp}16.04 _Xenial Xerus_: <>. @@ -354,54 +354,57 @@ other Ubuntu releases. |https://getfedora.org/[Fedora] |<>. -|link:/docs/v2.8#doc-fedora[LTTng{nbsp}2.8 for Fedora 25]. +|link:/docs/v2.10#doc-fedora[LTTng{nbsp}2.10 for Fedora{nbsp}27]. <> for other Fedora releases. |https://www.debian.org/[Debian] -|xref:debian[Debian "stretch" (stable), Debian "buster" (testing), +|<>. +|link:/docs/v2.10#doc-debian[LTTng{nbsp}2.10 for Debian "buster" (testing) and Debian "sid" (unstable)]. -|<> for + + +<> for other Debian releases. |https://www.archlinux.org/[Arch Linux] -|<>. -| +|_Not available_ +|link:/docs/v2.10#doc-arch-linux[LTTng{nbsp}2.10 for the current Arch Linux build]. + +<>. |https://alpinelinux.org/[Alpine Linux] -|<>. -|<> for -other Alpine Linux releases. +|_Not available_ +|link:/docs/v2.10#doc-alpine-linux[LTTng{nbsp}2.10 for Alpine Linux{nbsp}3.7 +and Alpine Linux{nbsp}"edge"]. + +<>. |https://www.redhat.com/[RHEL] and https://www.suse.com/[SLES] |See http://packages.efficios.com/[EfficiOS Enterprise Packages]. | |https://buildroot.org/[Buildroot] -|<>. -|link:/docs/v2.8#doc-buildroot[LTTng{nbsp}2.8 for Buildroot{nbsp}2016.11]. - -<> for +|<<"buildroot", "Buildroot{nbsp}2017.02, Buildroot{nbsp}2017.05, Buildroot{nbsp}2017.08, and Buildroot{nbsp}2017.11">>. +|<> for other Buildroot releases. |http://www.openembedded.org/wiki/Main_Page[OpenEmbedded] and https://www.yoctoproject.org/[Yocto] -|<> (`openembedded-core` layer). -|link:/docs/v2.8#doc-oe-yocto[LTTng{nbsp}2.8 for Yocto Project{nbsp}2.2 _Morty_] +|<> (`openembedded-core` layer). - -<> for -other OpenEmbedded releases. +|<> for +other Yocto/OpenEmbedded releases. |==== [[ubuntu]] === [[ubuntu-official-repositories]]Ubuntu -LTTng{nbsp}{revision} is available on Ubuntu{nbsp}17.04 _Zesty Zapus_. -For previous releases of Ubuntu, <>. +LTTng{nbsp}{revision} is available on Ubuntu{nbsp}17.04 _Zesty Zapus_ +and Ubuntu{nbsp}17.10 _Artful Aardvark_. For previous releases of +Ubuntu, <>. To install LTTng{nbsp}{revision} on Ubuntu{nbsp}17.04 _Zesty Zapus_: @@ -547,8 +550,7 @@ LTTng-UST{nbsp}{revision} from source and pass the [[debian]] === Debian -To install LTTng{nbsp}{revision} on Debian "stretch" (stable), -Debian "buster" (testing), or Debian "sid" (unstable): +To install LTTng{nbsp}{revision} on Debian "stretch" (stable): . Install the main LTTng{nbsp}{revision} packages: + @@ -582,84 +584,6 @@ Debian "buster" (testing), or Debian "sid" (unstable): -- -[[arch-linux]] -=== Arch Linux - -To install LTTng{nbsp}{revision} on Arch Linux using -https://github.com/rmarquis/pacaur[pacaur]: - -. Install the main LTTng{nbsp}{revision} packages: -+ --- -[role="term"] ----- -$ pacaur -Sy lttng-tools -$ pacaur -Sy lttng-ust -$ pacaur -Sy lttng-modules ----- --- - -. **If you need to instrument and trace <>**, install the LTTng-UST Python agent: -+ --- -[role="term"] ----- -$ pacaur -Sy python-lttngust -$ pacaur -Sy python2-lttngust ----- --- - - -[[alpine-linux]] -=== Alpine Linux - -To install LTTng-tools{nbsp}{revision} and LTTng-UST{nbsp}{revision} on -Alpine Linux "edge": - -. Make sure your system is - https://wiki.alpinelinux.org/wiki/Edge[configured for "edge"]. -. Enable the _testing_ repository by uncommenting the corresponding - line in path:{/etc/apk/repositories}. -. Add the LTTng packages: -+ --- -[role="term"] ----- -# apk add lttng-tools -# apk add lttng-ust-dev ----- --- - -To install LTTng-modules{nbsp}{revision} (Linux kernel tracing support) -on Alpine Linux "edge": - -. Add the vanilla Linux kernel: -+ --- -[role="term"] ----- -# apk add linux-vanilla linux-vanilla-dev ----- --- - -. Reboot with the vanilla Linux kernel. -. Download, build, and install the latest LTTng-modules{nbsp}{revision}: -+ --- -[role="term"] ----- -$ cd $(mktemp -d) && -wget http://lttng.org/files/lttng-modules/lttng-modules-latest-2.9.tar.bz2 && -tar -xf lttng-modules-latest-2.9.tar.bz2 && -cd lttng-modules-2.9.* && -make && -sudo make modules_install && -sudo depmod -a ----- --- - - [[enterprise-distributions]] === RHEL, SUSE, and other enterprise distributions @@ -671,8 +595,9 @@ see http://packages.efficios.com/[EfficiOS Enterprise Packages]. [[buildroot]] === Buildroot -To install LTTng{nbsp}{revision} on Buildroot{nbsp}2017.02 or -Buildroot{nbsp}2017.05: +To install LTTng{nbsp}{revision} on Buildroot{nbsp}2017.02, +Buildroot{nbsp}2017.05, Buildroot{nbsp}2017.08, or +Buildroot{nbsp}2017.11: . Launch the Buildroot configuration tool: + @@ -696,7 +621,8 @@ $ make menuconfig LTTng{nbsp}{revision} recipes are available in the http://layers.openembedded.org/layerindex/branch/master/layer/openembedded-core/[`openembedded-core`] -layer for Yocto Project{nbsp}2.3 _Pyro_ under the following names: +layer for Yocto Project{nbsp}2.3 _Pyro_ and Yocto Project{nbsp}2.4 _Rocko_ +under the following names: * `lttng-tools` * `lttng-modules` @@ -1592,10 +1518,14 @@ as soon as a there's no space left for a new event record, whereas in discard mode, the tracer only discards the event record that doesn't fit. -In discard mode, LTTng increments a count of lost event records when -an event record is lost and saves this count to the trace. In -overwrite mode, LTTng keeps no information when it overwrites a -sub-buffer before consuming it. +In discard mode, LTTng increments a count of lost event records when an +event record is lost and saves this count to the trace. In overwrite +mode, since LTTng 2.8, LTTng increments a count of lost sub-buffers when +a sub-buffer is lost and saves this count to the trace. In this mode, +the exact number of lost event records in those lost sub-buffers is not +saved to the trace. Trace analyses can use the trace's saved discarded +event record and sub-buffer counts to decide whether or not to perform +the analyses even if trace data is known to be missing. There are a few ways to decrease your probability of losing event records.