From: Boris Ostrovsky <boris.ostrovsky@oracle.com>
To: david.vrabel@citrix.com, konrad.wilk@oracle.com
Cc: dietmar.hahn@ts.fujitsu.com, jbeulich@suse.com,
kevin.tian@intel.com, xen-devel@lists.xen.org,
linux-kernel@vger.kernel.org, boris.ostrovsky@oracle.com
Subject: [PATCH v5 0/6] xen/PMU: PMU support for Xen PV(H) guests
Date: Thu, 2 Jul 2015 10:53:30 -0400 [thread overview]
Message-ID: <1435848816-3323-1-git-send-email-boris.ostrovsky@oracle.com> (raw)
I haven't posted Linux part of PV(H) VPMU support in a while but now
that (hopefully) the hypervisor part is getting close to be done I
think it's time to post it again.
There are very few differences compared to the last version, mostly due
to updates in shared structures layouts. Patches 1 and 4 have no changes
at all and patch 5 has minor changes due to rebasing so I kept David's
Reviewed-by tag.
Boris Ostrovsky (6):
xen: xensyms support
xen/PMU: Sysfs interface for setting Xen PMU mode
xen/PMU: Initialization code for Xen PMU
xen/PMU: Describe vendor-specific PMU registers
xen/PMU: Intercept PMU-related MSR and APIC accesses
xen/PMU: PMU emulation code
Documentation/ABI/testing/sysfs-hypervisor-pmu | 23 +
arch/x86/include/asm/xen/hypercall.h | 6 +
arch/x86/include/asm/xen/interface.h | 123 ++++++
arch/x86/xen/Makefile | 2 +-
arch/x86/xen/apic.c | 6 +
arch/x86/xen/enlighten.c | 13 +-
arch/x86/xen/pmu.c | 572 +++++++++++++++++++++++++
arch/x86/xen/pmu.h | 15 +
arch/x86/xen/smp.c | 29 +-
arch/x86/xen/suspend.c | 23 +-
drivers/xen/Kconfig | 8 +
drivers/xen/sys-hypervisor.c | 127 ++++++
drivers/xen/xenfs/Makefile | 1 +
drivers/xen/xenfs/super.c | 3 +
drivers/xen/xenfs/xenfs.h | 1 +
drivers/xen/xenfs/xensyms.c | 152 +++++++
include/xen/interface/platform.h | 18 +
include/xen/interface/xen.h | 2 +
include/xen/interface/xenpmu.h | 94 ++++
19 files changed, 1208 insertions(+), 10 deletions(-)
create mode 100644 Documentation/ABI/testing/sysfs-hypervisor-pmu
create mode 100644 arch/x86/xen/pmu.c
create mode 100644 arch/x86/xen/pmu.h
create mode 100644 drivers/xen/xenfs/xensyms.c
create mode 100644 include/xen/interface/xenpmu.h
--
1.8.1.4
next reply other threads:[~2015-07-02 14:54 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-02 14:53 Boris Ostrovsky [this message]
2015-07-02 14:53 ` [PATCH v5 1/6] xen: xensyms support Boris Ostrovsky
2015-07-02 14:53 ` [PATCH v5 2/6] xen/PMU: Sysfs interface for setting Xen PMU mode Boris Ostrovsky
2015-07-02 16:16 ` [Xen-devel] " David Vrabel
2015-07-02 14:53 ` [PATCH v5 3/6] xen/PMU: Initialization code for Xen PMU Boris Ostrovsky
2015-07-02 16:21 ` [Xen-devel] " David Vrabel
2015-07-02 17:14 ` Boris Ostrovsky
2015-07-02 14:53 ` [PATCH v5 4/6] xen/PMU: Describe vendor-specific PMU registers Boris Ostrovsky
2015-07-02 14:53 ` [PATCH v5 5/6] xen/PMU: Intercept PMU-related MSR and APIC accesses Boris Ostrovsky
2015-07-02 14:53 ` [PATCH v5 6/6] xen/PMU: PMU emulation code Boris Ostrovsky
2015-07-02 16:22 ` [Xen-devel] " David Vrabel
2015-07-02 16:25 ` [Xen-devel] [PATCH v5 0/6] xen/PMU: PMU support for Xen PV(H) guests David Vrabel
2015-07-02 17:18 ` Boris Ostrovsky
2015-08-07 15:35 ` David Vrabel
2015-08-07 15:50 ` Julien Grall
2015-08-07 16:06 ` Boris Ostrovsky
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=1435848816-3323-1-git-send-email-boris.ostrovsky@oracle.com \
--to=boris.ostrovsky@oracle.com \
--cc=david.vrabel@citrix.com \
--cc=dietmar.hahn@ts.fujitsu.com \
--cc=jbeulich@suse.com \
--cc=kevin.tian@intel.com \
--cc=konrad.wilk@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--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
all inboxes | Powered by JetHome®