[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Xen-devel] [RFC][PATCH] 1/3] [XEN] Use explicit bit sizedfieldsfor exported xentrace data.

  • To: "Ian Pratt" <m+Ian.Pratt@xxxxxxxxxxxx>
  • From: "George Dunlap " <dunlapg@xxxxxxxxx>
  • Date: Fri, 8 Dec 2006 15:28:05 -0500
  • Cc: Mark Williamson <mark.williamson@xxxxxxxxxxxx>, xen-devel@xxxxxxxxxxxxxxxxxxx, Keir Fraser <keir@xxxxxxxxxxxxx>, Tony Breeds <tony@xxxxxxxxxxxxxxxxxx>
  • Delivery-date: Fri, 08 Dec 2006 12:28:54 -0800
  • Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:sender:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references:x-google-sender-auth; b=mKvhFIRGidh8w/OaddixjFa20osQ2wD+5Q67ZnHAYUEuDnO/k3XnVSVrSxfhlENH2b3F4kk6VUyH4Qc8pf5T0znTw8VKubNIB7vX6rHcVUdKTgC6+AYxe/C9mlhwQ1y1e+1mNuBQp3GHPqbo00ZKjXOX3XUSweberjhF1G4TYeM=
  • List-id: Xen developer discussion <xen-devel.lists.xensource.com>

On 12/8/06, Ian Pratt <m+Ian.Pratt@xxxxxxxxxxxx> wrote:
If we did this with macros we could use sizeof(_x) to determine how many
bytes to write to the trace buffer. Os is the intention to deliberately
truncate some 64b quantities to 32b save trace buffer space?

Yes.  What initiated this discussion was that changing the trace
buffers to u64 would double the size of traces.  My typical traces are
already 1GB+, with longer ones reaching 10G+.  Since at this point I'm
looking mainly at 32-bit VMX code, it would be nice if I could avoid

However, as long as the /number/ of 64b quantities was variable, I
could make do with either size.


Xen-devel mailing list



Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.