On Thu, 2017-02-09 at 20:51 -0500, mathieu.desnoyersa wrote:
> On 32-bit systems, the current algorithm assume to have one clock read
> per 32-bit LSB overflow period, which is not guaranteed. It also has an
> issue on the first clock reads after module load, because the initial
> value for the las
Patch to fix recv() syscall missing in ARM syscall list.
Patch from lttng mailing list that fixes kernel timestamps being off
by about ~2 seconds on 32-bit systems. Additional patch to fix
compilation bug on non-X86 introduced by previous patch.
Signed-off-by: Trent Piepho
---
...trumentation
On Mon, 2017-03-06 at 17:12 +, Mathieu Desnoyers wrote:
> - On Mar 3, 2017, at 6:43 PM, Trent Piepho tpie...@kymetacorp.com wrote:
>
> Hi Trent,
>
> What lttng-modules branch is this for ?
Sorry about this, I meant to send this patch to the *buildroot* list to
fix
I've got a device that has an additional hardware, beyond the main
Linux CPU, that generates traceable events, asynchronously with
anything happening in Linux. It would nice if these trace points
could show up in an lttng trace along with normal lttng-ust and kernel
tracepoints.
Getting the FPGA,
On Thu, 2019-07-25 at 11:40 -0400, Mathieu Desnoyers wrote:
> There are a few reasons for using per-uid buffers over per-pid:
>
> - Lower memory consumption for use-cases with many processes,
> - Faster process launch time: no need to allocate buffers for each process.
> Useful for use-cases with
On Wed, 2019-02-20 at 13:53 -0500, Jonathan Rajotte-Julien wrote:
> On Wed, Feb 20, 2019 at 01:43:00PM -0500, Mosleh Uddin wrote:
> > Hello,
> >
> > I see, I was loading the liblttng-ust-fd but not fork. Once loading
> > both of
> > these with LD_PRELOAD everything seems to be working great. Thank
