From: Steven Rostedt <rostedt@goodmis.org>
To: Ingo Molnar <mingo@elte.hu>
Cc: mingo@redhat.com, hpa@zytor.com, mathieu.desnoyers@polymtl.ca,
anton@samba.org, linux-kernel@vger.kernel.org,
peterz@infradead.org, zhaolei@cn.fujitsu.com,
xiaoguangrong@cn.fujitsu.com, fweisbec@gmail.com,
tglx@linutronix.de, kosaki.motohiro@jp.fujitsu.com,
linux-tip-commits@vger.kernel.org
Subject: Re: [tip:timers/tracing] hrtimer: Add tracepoint for hrtimers
Date: Tue, 13 Oct 2009 14:56:14 -0400 [thread overview]
Message-ID: <1255460174.7113.2115.camel@gandalf.stny.rr.com> (raw)
In-Reply-To: <20091013184150.GA17492@elte.hu>
On Tue, 2009-10-13 at 20:41 +0200, Ingo Molnar wrote:
> > But still, we need to build a way to convert big endian to little, as
> > well as perhaps converting 32bit to 64 bit longs. As well as vice
> > versa.
>
> Exporting the print line as C in a convenient way does not in any way
> make it more difficult to define endianness and bit size - we have to do
> that anyway. It's largely orthogonal.
The way I do it now, is basically making a C interpreter. This can
easily handle word size and endianess (I have those exported too, and
can handle differences between host and file).
But to export the "printf" as a C function, that C function will need to
know a way what size a long is, as well as how to convert endianess.
I'm not really sure how to go about doing something like this
automatically. Every event will need its own C function to convert.
Sounds more like what Mathieu was describing.
We still don't have a way to handle enums and structures (like ktime).
-- Steve
next prev parent reply other threads:[~2009-10-13 18:58 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-10 2:48 [PATCH v6 1/3] ftrace: add tracepoint for timer Xiao Guangrong
2009-08-10 2:51 ` [PATCH v6 2/3] ftrace: add tracepoint for hrtimer Xiao Guangrong
2009-09-02 12:18 ` [tip:timers/tracing] hrtimer: Add tracepoint for hrtimers tip-bot for Xiao Guangrong
2009-10-13 3:25 ` Steven Rostedt
2009-10-13 7:08 ` Ingo Molnar
2009-10-13 13:17 ` Steven Rostedt
2009-10-13 13:18 ` Steven Rostedt
2009-10-13 13:26 ` Ingo Molnar
2009-10-13 14:02 ` Steven Rostedt
2009-10-13 15:35 ` [RFC] Trace types registry Mathieu Desnoyers
2009-10-13 18:41 ` [tip:timers/tracing] hrtimer: Add tracepoint for hrtimers Ingo Molnar
2009-10-13 18:56 ` Steven Rostedt [this message]
2009-10-13 7:48 ` Peter Zijlstra
2009-08-10 2:52 ` [PATCH v6 3/3] ftrace: add tracepoint for itimer Xiao Guangrong
2009-09-02 12:18 ` [tip:timers/tracing] itimers: Add tracepoints " tip-bot for Xiao Guangrong
2009-09-02 12:18 ` [tip:timers/tracing] timers: Add tracepoints for timer_list timers tip-bot for Xiao Guangrong
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=1255460174.7113.2115.camel@gandalf.stny.rr.com \
--to=rostedt@goodmis.org \
--cc=anton@samba.org \
--cc=fweisbec@gmail.com \
--cc=hpa@zytor.com \
--cc=kosaki.motohiro@jp.fujitsu.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tip-commits@vger.kernel.org \
--cc=mathieu.desnoyers@polymtl.ca \
--cc=mingo@elte.hu \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=tglx@linutronix.de \
--cc=xiaoguangrong@cn.fujitsu.com \
--cc=zhaolei@cn.fujitsu.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®