From: Olaf Hering <olaf@aepfle.de>
To: xen-devel@lists.xensource.com
Cc: George Dunlap <George.Dunlap@eu.citrix.com>
Subject: wrong vmexit size in xenalyze
Date: Fri, 19 Nov 2010 10:23:17 +0100 [thread overview]
Message-ID: <20101119092317.GA1755@aepfle.de> (raw)
George,
what is the reason behind this changeset?
http://xenbits.xensource.com/ext/xenalyze.hg?rev/9fa7e4d2a3af
All my vmexit trace entries have size 4 for 64bit and 3 for 32bit.
Looking at the code in ./xen/arch/x86/hvm/vmx/vmx.c, HVMTRACE_ND() gets
size 3 for VMEXIT64. But HVMTRACE_ND does a 'sizeof(u32)*count+1' in
xen-4.0.
The xen-unstable macro looks different. It was changed in this revision:
# 8 weeks ago: x86/hvm: fix extra size passed to __trace_var()
# revision 10: 9cebb977e9d8 (diff) (annotate)
# author: Keir Fraser <keir.fraser@citrix.com>
# date: Mon Sep 20 18:53:18 2010 +0100
I think this means most of the extra_words checks are bogus now, unless
the same change also goes into the 4.0 branch.
What should we do about this difference in tracedata?
Olaf
--- a/xenalyze.c Wed Nov 10 14:56:56 2010 +0000
+++ b/xenalyze.c Wed Nov 10 14:58:31 2010 +0000
@@ -4828,8 +4828,8 @@ void hvm_vmexit_process(struct record_in
};
} *r;
- if(ri->extra_words != 4
- && ri->extra_words != 3
+ if(ri->extra_words != 3
+ && ri->extra_words != 2
)
{
fprintf(warn, "FATAL: vmexit has unexpected extra words %d!\n",
next reply other threads:[~2010-11-19 9:23 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-19 9:23 Olaf Hering [this message]
2010-11-19 9:34 ` wrong vmexit size in xenalyze Keir Fraser
2010-11-19 9:50 ` George Dunlap
2010-11-19 10:05 ` Keir Fraser
2010-11-19 10:07 ` Olaf Hering
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=20101119092317.GA1755@aepfle.de \
--to=olaf@aepfle.de \
--cc=George.Dunlap@eu.citrix.com \
--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.