public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: Avi Kivity <avi@redhat.com>
To: linux-kernel@vger.kernel.org
Cc: kvm@vger.kernel.org, Ingo Molnar <mingo@elte.hu>,
	a.p.zijlstra@chello.nl, acme@ghostprotocols.net,
	Frederic Weisbecker <fweisbec@gmail.com>
Subject: [PATCH 0/3] Preparatory perf patches for KVM PMU support
Date: Wed, 29 Jun 2011 18:42:34 +0300	[thread overview]
Message-ID: <1309362157-6596-1-git-send-email-avi@redhat.com> (raw)

The following three patches pave the way for KVM in-guest performance
monitoring.  One is a perf API improvement, another fixes the constraints
for the version 1 architectural PMU (which we will emulate), and the third
adds an export that KVM will use.

Please consider for merging; this will make further work on the KVM PMU
easier.

Avi Kivity (3):
  perf: add context field to perf_event
  x86, perf: add constraints for architectural PMU v1
  perf: export perf_event_refresh() to modules

 arch/arm/kernel/ptrace.c                |    3 ++-
 arch/powerpc/kernel/ptrace.c            |    2 +-
 arch/sh/kernel/ptrace_32.c              |    3 ++-
 arch/x86/kernel/cpu/perf_event_intel.c  |   23 ++++++++++++++++++-----
 arch/x86/kernel/kgdb.c                  |    2 +-
 arch/x86/kernel/ptrace.c                |    3 ++-
 drivers/oprofile/oprofile_perf.c        |    2 +-
 include/linux/hw_breakpoint.h           |   10 ++++++++--
 include/linux/perf_event.h              |    9 ++++++++-
 kernel/events/core.c                    |   24 +++++++++++++++++-------
 kernel/events/hw_breakpoint.c           |   10 +++++++---
 kernel/watchdog.c                       |    2 +-
 samples/hw_breakpoint/data_breakpoint.c |    2 +-
 13 files changed, 69 insertions(+), 26 deletions(-)

-- 
1.7.5.3

             reply	other threads:[~2011-06-29 15:42 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-06-29 15:42 Avi Kivity [this message]
2011-06-29 15:42 ` [PATCH 1/3] perf: add context field to perf_event Avi Kivity
2011-06-29 16:08   ` Frederic Weisbecker
2011-06-29 16:25     ` Avi Kivity
2011-06-29 16:27     ` Will Deacon
2011-07-04 13:58       ` Frederic Weisbecker
2011-07-04 14:10         ` Avi Kivity
2011-07-04 14:36           ` Frederic Weisbecker
2011-07-11 21:07             ` Will Deacon
2011-07-12  7:20               ` Avi Kivity
2011-07-12  8:38                 ` Peter Zijlstra
2011-07-12  9:08                   ` Avi Kivity
2011-07-12  9:14                     ` Peter Zijlstra
2011-07-12  9:16                       ` Avi Kivity
2011-07-12  9:18                         ` Peter Zijlstra
2011-07-12  9:27                           ` Avi Kivity
2011-07-12  9:31                             ` Peter Zijlstra
2011-07-12  9:36                               ` Avi Kivity
2011-07-12  9:42                                 ` Will Deacon
2011-07-12  9:41                               ` Joerg Roedel
2011-07-12  9:44                                 ` Avi Kivity
2011-07-12  9:48                                   ` Joerg Roedel
2011-07-12  9:55                                     ` Avi Kivity
2011-07-12 10:03                                       ` Joerg Roedel
2011-07-12 10:07                                         ` Avi Kivity
2011-07-12 10:24                                           ` Joerg Roedel
2011-07-12 10:36                                             ` Avi Kivity
2011-07-21 15:32                               ` Will Deacon
2011-07-21 15:36                                 ` Avi Kivity
2011-07-21 15:46                                   ` Will Deacon
2011-07-21 15:59                                     ` Avi Kivity
2011-07-21 16:37                                       ` Will Deacon
2011-07-05 14:30         ` Will Deacon
2011-07-05 14:34           ` Frederic Weisbecker
2011-06-29 15:42 ` [PATCH 2/3] x86, perf: add constraints for architectural PMU v1 Avi Kivity
2011-06-29 15:42 ` [PATCH 3/3] perf: export perf_event_refresh() to modules Avi Kivity

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=1309362157-6596-1-git-send-email-avi@redhat.com \
    --to=avi@redhat.com \
    --cc=a.p.zijlstra@chello.nl \
    --cc=acme@ghostprotocols.net \
    --cc=fweisbec@gmail.com \
    --cc=kvm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    /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