From: Ben Thomas <bthomas@virtualiron.com>
To: xen-devel@lists.xensource.com
Subject: [PATCH] perfc_defn.h - increase VMX reason size array
Date: Wed, 08 Mar 2006 21:14:01 -0500 [thread overview]
Message-ID: <440F8F69.7060507@virtualiron.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 655 bytes --]
If I'm reading the spec correctly, the April 2005 Intel Virtualization
Technology Specification (Appendix A1) indicates that there are 44
potential exit reason codes. Based upon this, increase the size of
the PERFCOUNTER_ARRAY for vmexits.
Signed-off-by: Ben Thomas (bthomas@virtualiron.com)
--
------------------------------------------------------------------------
Ben Thomas Virtual Iron Software
bthomas@virtualiron.com Tower 1, Floor 2
978-849-1214 900 Chelmsford Street
Lowell, MA 01851
[-- Attachment #2: perfc_defn.patch --]
[-- Type: text/x-patch, Size: 641 bytes --]
diff -r 96678f701d42 xen/include/xen/perfc_defn.h
--- a/xen/include/xen/perfc_defn.h Mon Mar 6 11:12:48 2006 -0500
+++ b/xen/include/xen/perfc_defn.h Wed Mar 8 21:01:52 2006 -0500
@@ -26,7 +26,7 @@ PERFCOUNTER_ARRAY(hypercalls,
PERFCOUNTER_ARRAY(hypercalls, "hypercalls", NR_hypercalls)
PERFCOUNTER_ARRAY(exceptions, "exceptions", 32)
-#define VMX_PERF_EXIT_REASON_SIZE 37
+#define VMX_PERF_EXIT_REASON_SIZE 44
#define VMX_PERF_VECTOR_SIZE 0x20
PERFCOUNTER_ARRAY(vmexits, "vmexits", VMX_PERF_EXIT_REASON_SIZE)
PERFCOUNTER_ARRAY(cause_vector, "cause vector", VMX_PERF_VECTOR_SIZE)
[-- Attachment #3: Type: text/plain, Size: 138 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel
reply other threads:[~2006-03-09 2:14 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=440F8F69.7060507@virtualiron.com \
--to=bthomas@virtualiron.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.