From: Olaf Hering <olaf@aepfle.de>
To: George Dunlap <George.Dunlap@eu.citrix.com>
Cc: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>,
Keir Fraser <keir@xen.org>
Subject: Re: wrong vmexit size in xenalyze
Date: Fri, 19 Nov 2010 11:07:12 +0100 [thread overview]
Message-ID: <20101119100712.GA5089@aepfle.de> (raw)
In-Reply-To: <4CE6484B.9000707@eu.citrix.com>
On Fri, Nov 19, George Dunlap wrote:
> If you have a better idea, I'm open to it. A bit more discipline --
> doing an audit of the tracing after the feature freeze before each
> release -- would be helpful; some automated testing would be even
> more helpful.
I think the extra u32 is just padding and can be ignored.
Whats the purpose of the ->extra_bytes checks? If its just a data
integrity check, it can be removed because reading past the end of the
record data should not harm. Maybe limit the loops which iterate
->extra_bytes to 7 because more doesnt fit in a trace record.
Olaf
next prev parent reply other threads:[~2010-11-19 10:07 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-19 9:23 wrong vmexit size in xenalyze Olaf Hering
2010-11-19 9:34 ` Keir Fraser
2010-11-19 9:50 ` George Dunlap
2010-11-19 10:05 ` Keir Fraser
2010-11-19 10:07 ` Olaf Hering [this message]
2010-11-19 17:48 ` George Dunlap
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=20101119100712.GA5089@aepfle.de \
--to=olaf@aepfle.de \
--cc=George.Dunlap@eu.citrix.com \
--cc=keir@xen.org \
--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.