From: Dietmar Hahn <dietmar.hahn@ts.fujitsu.com>
To: xen-devel <xen-devel@lists.xen.org>
Subject: [PATCH] docs: add vpmu description to xen-command-line.markdown
Date: Fri, 27 Apr 2012 11:20:37 +0200 [thread overview]
Message-ID: <95424045.BJ4a0xs4Vr@amur> (raw)
# HG changeset patch
# User Dietmar Hahn <dietmar.hahn@ts.fujitsu.com>
# Date 1335517766 -7200
# Node ID 9ba4e4a5f3b1b7dad77e2801afc0253d6d30d565
# Parent 107285938c50f82667bd4d014820b439a077c22c
Add a short description to the vpmu boot option in the
xen-command-line.markdown
Signed-off-by: Dietmar Hahn <dietmar.hahn@ts.fujitsu.com>
diff -r 107285938c50 docs/misc/xen-command-line.markdown
--- a/docs/misc/xen-command-line.markdown Thu Apr 26 10:03:08 2012 +0100
+++ b/docs/misc/xen-command-line.markdown Fri Apr 27 11:09:26 2012 +0200
@@ -543,7 +543,28 @@ console even after dom0 has been started
relinquish control to dom0.
### vpid
+
### vpmu
+> `= ( bts )`
+
+> Default: `off`
+
+Switch on the virtualized performance monitoring unit for HVM guests.
+
+If the current cpu isn't supported a message like
+'VPMU: Initialization failed. ...'
+is printed on the hypervisor serial log.
+
+For some Intel Nehalem processors a quirk handling exist for an unknown
+wrong behaviour (see handle_pmc_quirk()).
+
+If 'vpmu=bts' is specified the virtualisation of the Branch Trace Store (BTS)
+feature is switched on on Intel processors supporting this feature.
+
+*Warning:*
+As the BTS virtualisation is not 100% safe and because of the nehalem quirk
+don't use the vpmu flag on production systems with Intel cpus!
+
### vti\_vhpt\_size
### vti\_vtlb\_size
### watchdog
--
Company details: http://ts.fujitsu.com/imprint.html
next reply other threads:[~2012-04-27 9:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-27 9:20 Dietmar Hahn [this message]
2012-04-27 9:29 ` [PATCH] docs: add vpmu description to xen-command-line.markdown Ian Campbell
2012-04-27 10:00 ` Dietmar Hahn
2012-05-10 17:03 ` 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=95424045.BJ4a0xs4Vr@amur \
--to=dietmar.hahn@ts.fujitsu.com \
--cc=xen-devel@lists.xen.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 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.