public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Mathieu Desnoyers <compudj@krystal.dyndns.org>
To: ltt-dev@lists.casi.polymtl.ca
Cc: Michael Rubin <mrubin@google.com>,
	Peter Zijlstra <peterz@infradead.org>,
	linux-kernel@vger.kernel.org,
	Steven Rostedt <rostedt@goodmis.org>,
	Michael Davidson <md@google.com>,
	Martin Bligh <mbligh@google.com>, Ingo Molnar <mingo@elte.hu>,
	Jan Blunck <jblunck@suse.de>,
	Thomas Gleixner <tglx@linutronix.de>
Subject: Re: [ltt-dev] LTTng new trace format, cleanup, kernel 2.6.27 support
Date: Sat, 11 Oct 2008 13:25:02 -0400	[thread overview]
Message-ID: <20081011172502.GA12718@Krystal> (raw)
In-Reply-To: <20081010233428.GA7035@Krystal>

I just released LTTng 0.39 and lttv 0.11.1, trace format 2.1, which
fixes the subbuffer header 32-64 bits portability.

I do not use packed structures anymore since trace format 2.0 because
gcc generates inefficient code (at least on mips and powerpc). However,
I make sure the fields fall on their natural alignment within the
structure so the compiler does not have to add ABI-specific padding. I
also added a header_end[0] field at the end of the header to be able to
easily compute the header size without including any supplementary
padding the compiler would add at the end of the structure.

Mathieu

* Mathieu Desnoyers (compudj@krystal.dyndns.org) wrote:
> Hi everyone,
> 
> I just cleaned up the LTTng trace format heavily, got rid of the
> heartbeat timer (by checking for overflow at the tracing site), got rid
> of the "special" compact channel; it removed about 5 FIXMEs in LTTng
> (cpu hotplug and compact channel related). Everything is compact now :
> 
> Event header is :
> 
> (32-bits alignment)
> 27-bits TSC
> 5-bits event ID
>  ID #31 reserved to specify extended event ID
>  ID #30 reserved to specify both ext. event ID and event size
>  ID #29 reserved to specify ext. event ID, event size and ext. TSC
> <ext.>
> 16-bits event ID (opt)
> 16-bits event size (opt) size = 65535 to specify large event size
> 32-bits large event size (opt)
> 64-bits TSC (opt) (aligned on sizeof (void *))
> (event payload aligned on the maximum alignment required within the
>  payload)
> 
> This is much more compact than the previous format, and permits a
> "tracer debug mode" in menuconfig which enables the "event size" field,
> which helps cross-checking the size expected by the userspace tool and
> the size written by the kernel.
> 
> Note that this "event size" field can eventually be enabled on a
> per-event or per-channel basis. This will probably be useful to encode
> "binary blobs"...
> 
> I also cleanup up the subbuffer header to make is much smaller than the
> previous one by removing unneeded information.
> 
> I renamed the "facilities" channel to a better name : "metadata".  It
> contains marker descriptions.
> 
> The trace major number is bumped to "2" and is completely incompatible
> with old LTTV. New version are LTTng 0.38 (for Linux 2.6.27) and LTTV
> 0.11.0.
> 
> Testing especially taking traces and reading them across different
> architectures is welcome (e.g. trace taken on powerpc 32, lttv running
> on x86_64).
> 
> Mathieu
> 
> 
> -- 
> Mathieu Desnoyers
> OpenPGP key fingerprint: 8CD5 52C3 8E3C 4140 715F  BA06 3F25 A8FE 3BAE 9A68
> 
> _______________________________________________
> ltt-dev mailing list
> ltt-dev@lists.casi.polymtl.ca
> http://lists.casi.polymtl.ca/cgi-bin/mailman/listinfo/ltt-dev
> 

-- 
Mathieu Desnoyers
OpenPGP key fingerprint: 8CD5 52C3 8E3C 4140 715F  BA06 3F25 A8FE 3BAE 9A68

      reply	other threads:[~2008-10-11 17:30 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-10-10 23:34 LTTng new trace format, cleanup, kernel 2.6.27 support Mathieu Desnoyers
2008-10-11 17:25 ` Mathieu Desnoyers [this message]

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=20081011172502.GA12718@Krystal \
    --to=compudj@krystal.dyndns.org \
    --cc=jblunck@suse.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=ltt-dev@lists.casi.polymtl.ca \
    --cc=mbligh@google.com \
    --cc=md@google.com \
    --cc=mingo@elte.hu \
    --cc=mrubin@google.com \
    --cc=peterz@infradead.org \
    --cc=rostedt@goodmis.org \
    --cc=tglx@linutronix.de \
    /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