From: Tony Breeds <tony@bakeyournoodle.com>
To: Mark Williamson <mark.williamson@cl.cam.ac.uk>
Cc: keir.fraser@cl.cam.ac.uk, xen-devel@lists.xensource.com
Subject: Re: [RFC][PATCH] 2/3] [TOOLS][XENTRACE] Update tools to write data to disk in a known endian'ness.
Date: Fri, 1 Dec 2006 16:23:24 +1100 [thread overview]
Message-ID: <20061201052324.GG27551@bakeyournoodle.com> (raw)
In-Reply-To: <200611301312.43868.mark.williamson@cl.cam.ac.uk>
On Thu, Nov 30, 2006 at 01:12:43PM +0000, Mark Williamson wrote:
> No objections to this here, seems like a nice improvement.
That's what we like to hear ;P
> I did wonder if
> perhaps some sort of trace file header would be useful, giving metadata. For
> instance, a record of what dom0 / Xen builds were being used, and type of
> machine might be useful.
I did think about doing something similar. I though I could steal the
high 16bits of the first CPU number in the file as a xentrace format
version number. Sure this would limit us to 64k CPUs but we can deal
with that limit later ;P
> A future extensible format would be a plus too, I
> guess. None of this is strictly necessary, it just might help with
> organising trace files.
You spoke in more detail about that in another email so I'll keep the
discussion there.
Yours Tony
linux.conf.au http://linux.conf.au/ || http://lca2007.linux.org.au/
Jan 15-20 2007 The Australian Linux Technical Conference!
next prev parent reply other threads:[~2006-12-01 5:23 UTC|newest]
Thread overview: 47+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-30 5:59 [RFC][PATCH] 0/3] [V2] Update xentrace to be compatable with PPC Tony Breeds
2006-11-30 5:59 ` [RFC][PATCH] 3/3] [TOOLS][XENTRACE] Various tidyups to xentrace tools Tony Breeds
2006-11-30 12:57 ` Mark Williamson
2006-12-01 5:39 ` Tony Breeds
2006-11-30 5:59 ` [RFC][PATCH] 2/3] [TOOLS][XENTRACE] Update tools to write data to disk in a known endian'ness Tony Breeds
2006-11-30 13:12 ` Mark Williamson
2006-12-01 5:23 ` Tony Breeds [this message]
2006-12-04 18:22 ` Mark Williamson
2006-11-30 16:27 ` George Dunlap
2006-12-01 5:43 ` Tony Breeds
2006-11-30 5:59 ` [RFC][PATCH] 1/3] [XEN] Use explicit bit sized fields for exported xentrace data Tony Breeds
2006-11-30 13:02 ` Mark Williamson
2006-11-30 16:58 ` George Dunlap
2006-11-30 17:03 ` Keir Fraser
2006-12-01 2:29 ` Mark Williamson
2006-12-01 11:32 ` Jimi Xenidis
2006-12-01 17:54 ` George Dunlap
2006-12-01 18:37 ` Keir Fraser
2006-12-05 16:54 ` Mark Williamson
2006-12-05 20:05 ` George Dunlap
2006-12-06 16:10 ` [RFC][PATCH] 1/3] [XEN] Use explicit bit sized fieldsfor " Ian Pratt
2006-12-07 2:43 ` Mark Williamson
2006-12-07 5:29 ` Tony Breeds
2006-12-07 10:32 ` Keir Fraser
2006-12-07 14:21 ` Ian Pratt
2006-12-07 18:25 ` George Dunlap
2006-12-08 10:52 ` [RFC][PATCH] 1/3] [XEN] Use explicit bit sizedfieldsfor " Ian Pratt
2006-12-08 20:28 ` George Dunlap
2006-12-04 18:20 ` [RFC][PATCH] 1/3] [XEN] Use explicit bit sized fields for " Mark Williamson
2006-12-12 17:29 ` LTTng Xen port Mathieu Desnoyers
2006-12-12 21:20 ` Ian Pratt
2006-12-12 22:14 ` Mathieu Desnoyers
2006-12-13 2:25 ` Tony Breeds
2006-12-15 5:02 ` Mark Williamson
2006-12-28 3:08 ` M.A. Williamson
2007-03-09 1:20 ` LTTng Xen port : finally in a repository near you Mathieu Desnoyers
2007-06-25 8:43 ` INAKOSHI Hiroya
2007-06-27 0:37 ` Mark Williamson
2007-06-27 16:22 ` Mathieu Desnoyers
2007-06-27 16:25 ` Keir Fraser
2007-06-27 16:14 ` Mathieu Desnoyers
2007-06-28 5:07 ` INAKOSHI Hiroya
2007-06-28 6:58 ` Mathieu Desnoyers
2007-06-28 12:32 ` INAKOSHI Hiroya
2007-06-28 15:08 ` Mathieu Desnoyers
2007-06-29 0:19 ` INAKOSHI Hiroya
-- strict thread matches above, loose matches on Subject: below --
2006-12-04 3:47 [RFC][PATCH] 0/3] [V3] Update xentrace to be compatable with PPC Tony Breeds
2006-12-04 3:47 ` [RFC][PATCH] 2/3] [TOOLS][XENTRACE] Update tools to write data to disk in a known endian'ness Tony Breeds
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=20061201052324.GG27551@bakeyournoodle.com \
--to=tony@bakeyournoodle.com \
--cc=keir.fraser@cl.cam.ac.uk \
--cc=mark.williamson@cl.cam.ac.uk \
--cc=xen-devel@lists.xensource.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.