Re: [Xen-devel] [RFC][PATCH] 2/3] [TOOLS][XENTRACE] Update tools

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!

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel

<Prev in Thread]

Current Thread

[Next in Thread>

Previous by Date:

[Xen-devel] libxen-python, ron minnich

Next by Date:

Re: [Xen-devel] [RFC][PATCH] 3/3] [TOOLS][XENTRACE] Various tidyups to xentrace tools., Tony Breeds

Previous by Thread:

Re: [Xen-devel] [RFC][PATCH] 2/3] [TOOLS][XENTRACE] Update tools to write data to disk in a known endian'ness., Mark Williamson

Next by Thread:

[Xen-devel] [RFC][PATCH] 1/3] [XEN] Use explicit bit sized fields for exported xentrace data., Tony Breeds

Indexes:

[Date] [Thread] [Top] [All Lists]

WARNING - OLD ARCHIVES

xen-devel

Re: [Xen-devel] [RFC][PATCH] 2/3] [TOOLS][XENTRACE] Update tools to writ