WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

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

To: Tony Breeds <tony@xxxxxxxxxxxxxxxxxx>
Subject: Re: [Xen-devel] [RFC][PATCH] 2/3] [TOOLS][XENTRACE] Update tools to write data to disk in a known endian'ness.
From: Mark Williamson <mark.williamson@xxxxxxxxxxxx>
Date: Mon, 4 Dec 2006 18:22:48 +0000
Cc: keir.fraser@xxxxxxxxxxxx, xen-devel@xxxxxxxxxxxxxxxxxxx
Delivery-date: Mon, 04 Dec 2006 10:22:56 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <20061201052324.GG27551@xxxxxxxxxxxxxxxxxx>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References: <200611300601.kAU614gE025340@xxxxxxxxxxxxxxxxxxxxxxxxx> <200611301312.43868.mark.williamson@xxxxxxxxxxxx> <20061201052324.GG27551@xxxxxxxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: KMail/1.9.5
> >                                                             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

Since traces are typically not going to be longlived but used for 
problem-specific debugging work, I think we can probably just make a clean 
break and define a new format.

Is anybody is really relying on the trace format being stable?  Please speak 
up now :-)

Cheers,
Mark


> >                           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!

-- 
Dave: Just a question. What use is a unicyle with no seat?  And no pedals!
Mark: To answer a question with a question: What use is a skateboard?
Dave: Skateboards have wheels.
Mark: My wheel has a wheel!

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

<Prev in Thread] Current Thread [Next in Thread>
  • Re: [Xen-devel] [RFC][PATCH] 2/3] [TOOLS][XENTRACE] Update tools to write data to disk in a known endian'ness., Mark Williamson <=