From: Christian Borntraeger <borntraeger@de.ibm.com>
To: Alexander Yarygin <yarygin@linux.vnet.ibm.com>,
Jiri Olsa <jolsa@redhat.com>
Cc: David Ahern <dsahern@gmail.com>,
Peter Zijlstra <a.p.zijlstra@chello.nl>,
Paul Mackerras <paulus@samba.org>,
Arnaldo Carvalho de Melo <acme@redhat.com>,
Cornelia Huck <cornelia.huck@de.ibm.com>,
linux-kernel@vger.kernel.org, Paolo Bonzini <pbonzini@redhat.com>
Subject: Re: [PATCH 0/4] perf kvm: Refactoring and small improvements
Date: Thu, 03 Jul 2014 16:47:04 +0200 [thread overview]
Message-ID: <53B56CE8.1040306@de.ibm.com> (raw)
In-Reply-To: <1404395992-17095-1-git-send-email-yarygin@linux.vnet.ibm.com>
On 03/07/14 15:59, Alexander Yarygin wrote:
> Hello,
>
> We divided patch series "perf/s390/kvm: trace events, perf kvm stat"
> into 2 parts.
>
> This patch set is a preparation for the next one, which adds support for
> perf kvm stat support on s390.
>
> Patch 1 removes direct dependence of perf kvm stat from x86.
> Patches 2-3 are refactoring.
> Patch 4 adds arch/s390/header.c to be used by perf kvm stat on s390.
>
> Compared to the previous version, patches contain some minor style/typo fixes.
>
> Link to the previous thread: https://lkml.org/lkml/2014/4/25/331
> (mirror: http://marc.info/?l=linux-kernel&m=139841718926897)
>
> Please consider to merge.
>
> Thanks.
>
> Alexander Yarygin (4):
> perf kvm: Introduce HAVE_KVM_STAT_SUPPORT flag
> perf kvm: Simplify of exit reasons tables definitions
> perf kvm: Refactoring of cpu_isa_config()
> perf: Allow to use cpuinfo on s390
>
> tools/perf/arch/s390/Makefile | 1 +
> tools/perf/arch/s390/util/header.c | 28 ++++++++++++++
> tools/perf/arch/x86/Makefile | 1 +
> tools/perf/builtin-kvm.c | 72 +++++++++++++++++++-----------------
> tools/perf/config/Makefile | 4 ++
> tools/perf/perf-sys.h | 1 +
> 6 files changed, 73 insertions(+), 34 deletions(-)
> create mode 100644 tools/perf/arch/s390/util/header.c
>
> --
> 1.7.9.5
>
CCing Paolo to allow him to comment.
FWIW, all patches
Acked-by: Christian Borntraeger <borntraeger@de.ibm.com>
Should be good for next merge window.
next prev parent reply other threads:[~2014-07-03 14:47 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-03 13:59 [PATCH 0/4] perf kvm: Refactoring and small improvements Alexander Yarygin
2014-07-03 13:59 ` [PATCH 1/4] perf kvm: Introduce HAVE_KVM_STAT_SUPPORT flag Alexander Yarygin
2014-07-16 19:15 ` [tip:perf/core] " tip-bot for Alexander Yarygin
2014-07-03 13:59 ` [PATCH 2/4] perf kvm: Simplify of exit reasons tables definitions Alexander Yarygin
2014-07-16 19:16 ` [tip:perf/core] perf kvm: Simplify " tip-bot for Alexander Yarygin
2014-07-03 13:59 ` [PATCH 3/4] perf kvm: Refactoring of cpu_isa_config() Alexander Yarygin
2014-07-16 19:16 ` [tip:perf/core] " tip-bot for Alexander Yarygin
2014-07-03 14:08 ` [PATCH 4/4] perf: Allow to use cpuinfo on s390 Alexander Yarygin
2014-07-16 19:16 ` [tip:perf/core] perf tools: " tip-bot for Alexander Yarygin
2014-07-03 14:47 ` Christian Borntraeger [this message]
2014-07-03 15:22 ` [PATCH 0/4] perf kvm: Refactoring and small improvements Arnaldo Carvalho de Melo
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=53B56CE8.1040306@de.ibm.com \
--to=borntraeger@de.ibm.com \
--cc=a.p.zijlstra@chello.nl \
--cc=acme@redhat.com \
--cc=cornelia.huck@de.ibm.com \
--cc=dsahern@gmail.com \
--cc=jolsa@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=paulus@samba.org \
--cc=pbonzini@redhat.com \
--cc=yarygin@linux.vnet.ibm.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.