From: fche@redhat.com (Frank Ch. Eigler)
To: Mathieu Desnoyers <mathieu.desnoyers@efficios.com>
Cc: linux-kernel@vger.kernel.org, systemtap@sources.redhat.com,
ltt-dev@lists.casi.polymtl.ca,
Steven Rostedt <rostedt@goodmis.org>,
mingo@elte.hu, Peter Zijlstra <peterz@infradead.org>,
Frederic Weisbecker <fweisbec@gmail.com>,
Elena Zannoni <elena.zannoni@oracle.com>,
Arnaldo Carvalho de Melo <acme@infradead.org>,
Thomas Gleixner <tglx@linutronix.de>,
Aaron Spear <aaron_spear@mentor.com>,
Tasneem Brutch - SISA <t.brutch@sisa.samsung.com>,
Tim Bird <tim.bird@am.sony.com>,
dominique.toupin@ericsson.com, Andi Kleen <andi@firstfloor.org>,
"Paul E. McKenney" <paulmck@linux.vnet.ibm.com>,
Philippe Maisonneuve <Philippe.Maisonneuve@windriver.com>,
Felix Burton <Felix.Burton@windriver.com>,
Andrew McDermott <Andrew.McDermott@windriver.com>,
Stefan Hajnoczi <stefanha@gmail.com>
Subject: Re: [RFC] Common Trace Format Proposal for Linux (v1)
Date: Wed, 13 Oct 2010 11:48:09 -0400 [thread overview]
Message-ID: <y0miq166qme.fsf@fche.csb> (raw)
In-Reply-To: <20101005193712.GB25605@Krystal> (Mathieu Desnoyers's message of "Tue, 5 Oct 2010 15:37:12 -0400")
Hi -
mathieu wrote:
> [...]
> Metadata attribute representation:
> align = value; /* value in bits */
> [...]
> byte_order = native OR network OR be OR le; /* network and be are aliases */
> [...]
Is there some reason to invent a new textual syntax for describing
how to pack structs? There is DWARF, ASN.1, C, ....
- FChE
next prev parent reply other threads:[~2010-10-13 15:49 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-05 19:37 [RFC] Common Trace Format Proposal for Linux (v1) Mathieu Desnoyers
2010-10-13 15:48 ` Frank Ch. Eigler [this message]
2010-10-20 18:50 ` 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=y0miq166qme.fsf@fche.csb \
--to=fche@redhat.com \
--cc=Andrew.McDermott@windriver.com \
--cc=Felix.Burton@windriver.com \
--cc=Philippe.Maisonneuve@windriver.com \
--cc=aaron_spear@mentor.com \
--cc=acme@infradead.org \
--cc=andi@firstfloor.org \
--cc=dominique.toupin@ericsson.com \
--cc=elena.zannoni@oracle.com \
--cc=fweisbec@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=ltt-dev@lists.casi.polymtl.ca \
--cc=mathieu.desnoyers@efficios.com \
--cc=mingo@elte.hu \
--cc=paulmck@linux.vnet.ibm.com \
--cc=peterz@infradead.org \
--cc=rostedt@goodmis.org \
--cc=stefanha@gmail.com \
--cc=systemtap@sources.redhat.com \
--cc=t.brutch@sisa.samsung.com \
--cc=tglx@linutronix.de \
--cc=tim.bird@am.sony.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.