From: Juergen Gross <juergen.gross@ts.fujitsu.com>
To: xen-devel@lists.xensource.com
Subject: [PATCH] Enable cpuid performance counter leaf for HVM
Date: Thu, 08 Sep 2011 15:29:34 +0200 [thread overview]
Message-ID: <8244f714acf1cc2bc085.1315488574@nehalem1> (raw)
[-- Attachment #1: Type: text/plain, Size: 238 bytes --]
In HVM domains the usable performance counters can be checked automatically
only, if cpuid leaf 0x0000000a is accessible.
Signed-off-by: juergen.gross@ts.fujitsu.com
1 file changed, 1 insertion(+)
tools/libxc/xc_cpuid_x86.c | 1 +
[-- Attachment #2: xen-staging.hg.patch --]
[-- Type: text/x-patch, Size: 1018 bytes --]
# HG changeset patch
# User Juergen Gross <juergen.gross@ts.fujitsu.com>
# Date 1315488544 -7200
# Node ID 8244f714acf1cc2bc08517a34dc241380f9648e6
# Parent bdd19847ae63b5dfb036e228cb16ec3ae678e995
Enable cpuid performance counter leaf for HVM
In HVM domains the usable performance counters can be checked automatically
only, if cpuid leaf 0x0000000a is accessible.
Signed-off-by: juergen.gross@ts.fujitsu.com
diff -r bdd19847ae63 -r 8244f714acf1 tools/libxc/xc_cpuid_x86.c
--- a/tools/libxc/xc_cpuid_x86.c Wed Sep 07 10:37:48 2011 +0100
+++ b/tools/libxc/xc_cpuid_x86.c Thu Sep 08 15:29:04 2011 +0200
@@ -392,6 +392,7 @@ static void xc_cpuid_hvm_policy(
case 0x00000002: /* Intel cache info (dumped by AMD policy) */
case 0x00000004: /* Intel cache info (dumped by AMD policy) */
+ case 0x0000000a: /* Architectural Performance Monitor Features */
case 0x80000002: /* Processor name string */
case 0x80000003: /* ... continued */
case 0x80000004: /* ... continued */
[-- Attachment #3: Type: text/plain, Size: 138 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel
next reply other threads:[~2011-09-08 13:29 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-08 13:29 Juergen Gross [this message]
2011-09-15 14:26 ` [PATCH] Enable cpuid performance counter leaf for HVM Ian Jackson
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=8244f714acf1cc2bc085.1315488574@nehalem1 \
--to=juergen.gross@ts.fujitsu.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 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).