qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Stefan Hajnoczi <stefanha@gmail.com>
To: Markus Armbruster <armbru@redhat.com>
Cc: Harsh Bora <harsh@linux.vnet.ibm.com>,
	qemu-devel@nongnu.org,
	"Aneesh Kumar K. V" <aneesh.kumar@linux.vnet.ibm.com>
Subject: Re: [Qemu-devel] RFC: Design Doc for a new trace format (to support variable number/size of args per event) simpletrace-v2
Date: Tue, 29 Nov 2011 12:56:03 +0000	[thread overview]
Message-ID: <CAJSP0QVvmusMJMAaptg22TfYvu+6YMSdrH+yi_L012oUieeZ4w@mail.gmail.com> (raw)
In-Reply-To: <m3pqgb5cnt.fsf@blackfin.pond.sub.org>

On Tue, Nov 29, 2011 at 12:35 PM, Markus Armbruster <armbru@redhat.com> wrote:
> Stefan Hajnoczi <stefanha@gmail.com> writes:
>
> [...]
>> So forget I said "self-describing" :).  I think the only changes from
>> the v1 format we need are:
>>
>> 1. New magic number to mark v2 format.
>>
>> 2. Trace records are no longer fixed-length, they include a size field:
>>
>> typedef struct {
>>     uint32_t length; /* in bytes */
>>     uint32_t reserved; /* unused */
>>     uint64_t event;
>>     uint64_t timestamp_ns;
>>     uint8_t arguments[];
>> } TraceRecord;
>>
>> 3. Strings are serialized like this:
>>
>> uint16_t length;
>> char chars[length];
>
> 16 bit length?  Sure you want that?

You're right, it's more future-proof to use a larger type.  Since I
said uint32_t length in TraceRecord, uint32_t here would work well.

Stefan

  reply	other threads:[~2011-11-29 12:56 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-11-29  8:29 [Qemu-devel] RFC: Design Doc for a new trace format (to support variable number/size of args per event) simpletrace-v2 Harsh Bora
2011-11-29 11:34 ` Stefan Hajnoczi
2011-11-29 11:47   ` Stefan Hajnoczi
2011-11-29 12:35     ` Markus Armbruster
2011-11-29 12:56       ` Stefan Hajnoczi [this message]
2011-11-30  6:07         ` Harsh Bora

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=CAJSP0QVvmusMJMAaptg22TfYvu+6YMSdrH+yi_L012oUieeZ4w@mail.gmail.com \
    --to=stefanha@gmail.com \
    --cc=aneesh.kumar@linux.vnet.ibm.com \
    --cc=armbru@redhat.com \
    --cc=harsh@linux.vnet.ibm.com \
    --cc=qemu-devel@nongnu.org \
    /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;
as well as URLs for NNTP newsgroup(s).