[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <1305038132-5080-1-git-send-email-joerg.roedel@amd.com>
Date: Tue, 10 May 2011 16:35:29 +0200
From: Joerg Roedel <joerg.roedel@....com>
To: Peter Zijlstra <a.p.zijlstra@...llo.nl>,
Paul Mackerras <paulus@...ba.org>, Ingo Molnar <mingo@...e.hu>,
Arnaldo Carvalho de Melo <acme@...stprotocols.net>
CC: <linux-kernel@...r.kernel.org>, <kvm@...r.kernel.org>
Subject: [RFC][PATCH 0/3] perf support for amd guest/host-only bits
Hi,
this small set of patches implement support for the amd guest/host-only
bits into perf. The counting for either host or guest-mode can be
enabled using two additional attribute-bits.
The patches are RFC for now for several reasons. First of all, these are
my first patches for perf, so I likely don't implemented everything the
perf-way. Another reason is, that when one of these two bits is set, the
counters will only count when SVM is enabled (with KVM this is only the
case when a guest runs). So even when host-only is configured (which
needs to be done explicitly, so no regression, default is still to set
none of these two bits) the counter will not count at all as long as no
kvm guest is running. The question is whether this is ok or whether this
situation needs to be handled (say, count when host-only is specified by
userspace and svm is disabled). Or we just don't care because specifing
guest/host-only counting only makes sense with guests anyway. I am open
for both.
So any feedback is greatly appreciated :-)
Regards,
Joerg
Diffstat:
arch/x86/include/asm/perf_event.h | 3 +++
arch/x86/kernel/cpu/perf_event_amd.c | 6 ++++++
include/linux/perf_event.h | 5 ++++-
kernel/perf_event.c | 4 ++++
tools/perf/util/parse-events.c | 10 +++++++++-
5 files changed, 26 insertions(+), 2 deletions(-)
Shortlog:
Joerg Roedel (3):
perf, core: Introduce attrs to count in either host or guest mode
perf, x86: Use GO/HO bits in perf-ctr
perf, tools: Add support for guest/host-only profiling
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists