From: Boris Ostrovsky <boris.ostrovsky@oracle.com>
To: xen-devel@lists.xen.org
Cc: Boris Ostrovsky <boris.ostrovsky@oracle.com>,
andrew.cooper3@citrix.com, kevin.tian@intel.com,
jun.nakajima@intel.com, jbeulich@suse.com
Subject: [PATCH v4 0/2] VPMU management update
Date: Wed, 1 Mar 2017 10:06:43 -0500 [thread overview]
Message-ID: <1488380805-5421-1-git-send-email-boris.ostrovsky@oracle.com> (raw)
Changes to how the hypervisor allocates and keeps track of active
VPMUs. The main purpose is to fix vpmu_enabled() reporting but this
also makes VPMU ref counting more consistent.
Changes in v4:
* Rebased to latest staging (xen/arch/x86/cpuid.c changes in patch1)
* Fixed whitespace in patch 2.
Boris Ostrovsky (2):
x86/vpmu: Add get/put_vpmu() and VPMU_AVAILABLE
x86/vpmu: Disable VPMU if guest's CPUID indicates no PMU support
xen/arch/x86/cpu/vpmu.c | 111 ++++++++++++++++++++++++++++--------------
xen/arch/x86/cpu/vpmu_intel.c | 4 ++
xen/arch/x86/cpuid.c | 6 +--
xen/arch/x86/domain.c | 5 ++
xen/arch/x86/domctl.c | 14 ++++++
xen/arch/x86/hvm/svm/svm.c | 5 --
xen/arch/x86/hvm/vmx/vmx.c | 5 --
xen/include/asm-x86/cpuid.h | 12 +++++
xen/include/asm-x86/vpmu.h | 6 ++-
9 files changed, 117 insertions(+), 51 deletions(-)
--
1.8.3.1
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel
next reply other threads:[~2017-03-01 15:06 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-01 15:06 Boris Ostrovsky [this message]
2017-03-01 15:06 ` [PATCH v4 1/2] x86/vpmu: Add get/put_vpmu() and VPMU_AVAILABLE Boris Ostrovsky
2017-03-01 15:06 ` [PATCH v4 2/2] x86/vpmu: Disable VPMU if guest's CPUID indicates no PMU support Boris Ostrovsky
2017-03-02 6:23 ` Tian, Kevin
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=1488380805-5421-1-git-send-email-boris.ostrovsky@oracle.com \
--to=boris.ostrovsky@oracle.com \
--cc=andrew.cooper3@citrix.com \
--cc=jbeulich@suse.com \
--cc=jun.nakajima@intel.com \
--cc=kevin.tian@intel.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 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).