From: Stefano Stabellini <stefano.stabellini@eu.citrix.com>
To: Boris Ostrovsky <boris.ostrovsky@oracle.com>
Cc: <david.vrabel@citrix.com>, <konrad.wilk@oracle.com>,
<kevin.tian@intel.com>, <jbeulich@suse.com>,
<dietmar.hahn@ts.fujitsu.com>, <stefano.stabellini@eu.citrix.com>,
<julien.grall@citrix.com>, <xen-devel@lists.xen.org>,
<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v6 0/6] xen/PMU: PMU support for Xen PV(H) guests
Date: Mon, 10 Aug 2015 11:01:45 +0100 [thread overview]
Message-ID: <alpine.DEB.2.02.1508101101000.11337@kaball.uk.xensource.com> (raw)
In-Reply-To: <1439170307-28370-1-git-send-email-boris.ostrovsky@oracle.com>
On Sun, 9 Aug 2015, Boris Ostrovsky wrote:
> Changes in v6:
> * Fix ARM builds (as suggested by Julien):
> o Make XEN_SYMS depend on X86 (patch 1)
> o Add CONFIG_XEN_HAVE_PVMMU and use it in drivers/xen/sys-hypervisor.c
> (patch 2)
> * Adjust release dates in Documentation/ABI/testing/sysfs-hypervisor-pmu
> (patch 2)
I confirm that it compiles just fine on ARM now.
> 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/Kconfig | 1 +
> 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 | 11 +
> drivers/xen/sys-hypervisor.c | 136 +++++-
> 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 ++++
> 20 files changed, 1220 insertions(+), 11 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
>
prev parent reply other threads:[~2015-08-10 10:03 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-10 1:31 Boris Ostrovsky
2015-08-10 1:31 ` [PATCH v6 1/6] xen: xensyms support Boris Ostrovsky
2015-08-10 1:31 ` [PATCH v6 2/6] xen/PMU: Sysfs interface for setting Xen PMU mode Boris Ostrovsky
2015-08-10 14:10 ` Konrad Rzeszutek Wilk
2015-08-10 1:31 ` [PATCH v6 3/6] xen/PMU: Initialization code for Xen PMU Boris Ostrovsky
2015-08-10 1:31 ` [PATCH v6 4/6] xen/PMU: Describe vendor-specific PMU registers Boris Ostrovsky
2015-08-10 1:31 ` [PATCH v6 5/6] xen/PMU: Intercept PMU-related MSR and APIC accesses Boris Ostrovsky
2015-08-10 1:31 ` [PATCH v6 6/6] xen/PMU: PMU emulation code Boris Ostrovsky
2015-08-10 10:01 ` Stefano Stabellini [this message]
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=alpine.DEB.2.02.1508101101000.11337@kaball.uk.xensource.com \
--to=stefano.stabellini@eu.citrix.com \
--cc=boris.ostrovsky@oracle.com \
--cc=david.vrabel@citrix.com \
--cc=dietmar.hahn@ts.fujitsu.com \
--cc=jbeulich@suse.com \
--cc=julien.grall@citrix.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®