Title: lttng-dev, Ravi left a message for you
See this email in English, Deutsch, Français, Italiano, Español, Português or 36 other languages.
Sorry had a sending problem.
Here is the rest.
On Wed, Aug 24, 2016 at 12:35 PM, Jonathan Rajotte <
jonathan.r.jul...@gmail.com> wrote:
> Hi,
>
> On Aug 24, 2016 12:18 PM, "Francis Deslauriers" <
> francis.deslauri...@mail.utoronto.ca> wrote:
> >
> > Hi David,
> > If you specifically want to
Hi,
On Aug 24, 2016 12:18 PM, "Francis Deslauriers" wrote:
>
> Hi David,
> If you specifically want to trace the scheduling of the threads of your
app, you don't need custom tracepoints.
> Enabling the sched_switch kernel event will give you both of cpu id
Hi David,
If you specifically want to trace the scheduling of the threads of your
app, you don't need custom tracepoints.
Enabling the sched_switch kernel event will give you both of cpu id and
thread id. Look at the cpu_id and next_tid fields.
You can enable the sched_switch event using : lttng
Merged, thanks !
Julien
On 23-Aug-2016 11:44:45 PM, Mathieu Desnoyers wrote:
> Signed-off-by: Mathieu Desnoyers
> ---
> tracker_private.h | 3 ++-
> wrapper/freelist-ll.h | 21 +++--
> 2 files changed, 17 insertions(+), 7 deletions(-)
>
>
Merged, big thanks !
Julien
On 23-Aug-2016 07:37:01 PM, Mathieu Desnoyers wrote:
> - 3 sizeof() issues (using pointer size rather than object size),
> - state tracking merge issue on switch in: the get following the
> insertion may not get the same node when there are duplicates,
> - also
Stefan Hajnoczi writes:
> On Sun, Aug 21, 2016 at 02:32:34PM +0200, Lluís Vilanova wrote:
>> Unfortuntely, I've been unable to to make dtrace recognise QEMU's events (I'm
>> only able to see the host kernel events). If someone with more experience on
>> it
>> can help me use dtrace with QEMU's
Hi
I am new to tracing in Linux and to lttng. I have a multi-threaded user
application and I want to see:
1) When the threads are scheduled to run
2) Which cores the threads are running on.
I have installed lttng on Ubuntu 14.04 LTS. I am expecting to visualise the
trace using