All of lore.kernel.org
 help / color / mirror / Atom feed
From: David Ahern <dsahern@gmail.com>
To: Christian Borntraeger <borntraeger@de.ibm.com>,
	Alexander Yarygin <yarygin@linux.vnet.ibm.com>,
	Jiri Olsa <jolsa@redhat.com>
Cc: Peter Zijlstra <a.p.zijlstra@chello.nl>,
	Paul Mackerras <paulus@samba.org>, Ingo Molnar <mingo@kernel.org>,
	Arnaldo Carvalho de Melo <acme@kernel.com>,
	Cornelia Huck <cornelia.huck@de.ibm.com>,
	linux-kernel@vger.kernel.org, Paolo Bonzini <pbonzini@redhat.com>
Subject: Re: [PATCH 1/4] perf kvm: Use defines of kvm events
Date: Mon, 07 Jul 2014 09:42:22 -0600	[thread overview]
Message-ID: <53BABFDE.1000703@gmail.com> (raw)
In-Reply-To: <53BAA963.2010800@de.ibm.com>

On 7/7/14, 8:06 AM, Christian Borntraeger wrote:
> On 03/07/14 16:29, Alexander Yarygin wrote:
>> Currently perf-kvm uses string literals for kvm event names,
>> but it works only for x86, because other architectures may have
>> other names for those events.
>>
>> To reduce dependence on architecture, we add <asm/kvm_perf.h> file with
>> defines for:
>> - kvm_entry and kvm_exit events,
>> - exit reason field name in kvm_exit event,
>> - length of exit reasons strings,
>> - vcpu_id field name in kvm trace events,
>>
>> and replace literals in perf-kvm.
>>
>> Signed-off-by: Alexander Yarygin <yarygin@linux.vnet.ibm.com>
>> Reviewed-by: Cornelia Huck <cornelia.huck@de.ibm.com>
>
> Acked-by: Christian Borntraeger <borntraeger@de.ibm.com>
> Would be good if Paolo and David could ack the KVM/perf parts. Then this should also go into next merge window.

I want to try out the patches on x86 and verify compiles on ppc; 
hopefully by end of day tomorrow.

David


  reply	other threads:[~2014-07-07 15:42 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-03 14:29 [PATCH/RFC 0/4] perf kvm: add stat support for s390 Alexander Yarygin
2014-07-03 14:29 ` [PATCH 1/4] perf kvm: Use defines of kvm events Alexander Yarygin
2014-07-07 14:06   ` Christian Borntraeger
2014-07-07 15:42     ` David Ahern [this message]
2014-07-09 13:45   ` David Ahern
2014-07-18  4:21   ` [tip:perf/core] " tip-bot for Alexander Yarygin
2014-07-03 14:29 ` [PATCH 2/4] perf kvm: Move arch specific code into arch/ Alexander Yarygin
2014-07-07 14:09   ` Christian Borntraeger
2014-07-09 13:45   ` David Ahern
2014-07-18  4:21   ` [tip:perf/core] " tip-bot for Alexander Yarygin
2014-07-03 14:29 ` [PATCH 3/4] perf kvm: Add skip_event() for --duration option Alexander Yarygin
2014-07-07 14:10   ` Christian Borntraeger
2014-07-09 13:45   ` David Ahern
2014-07-18  4:22   ` [tip:perf/core] " tip-bot for Alexander Yarygin
2014-07-03 14:29 ` [PATCH 4/4] perf kvm: Add stat support on s390 Alexander Yarygin
2014-07-07 14:11   ` Christian Borntraeger
2014-07-09 13:45   ` David Ahern
2014-07-10 10:50   ` Alexander Yarygin
2014-07-10 13:40     ` Arnaldo Carvalho de Melo
2014-07-18  4:22   ` [tip:perf/core] " tip-bot for Alexander Yarygin
2014-07-03 15:07 ` [PATCH/RFC 0/4] perf kvm: add stat support for s390 Christian Borntraeger
2014-07-09 16:47 ` David Ahern
2014-07-09 18:58   ` 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=53BABFDE.1000703@gmail.com \
    --to=dsahern@gmail.com \
    --cc=a.p.zijlstra@chello.nl \
    --cc=acme@kernel.com \
    --cc=borntraeger@de.ibm.com \
    --cc=cornelia.huck@de.ibm.com \
    --cc=jolsa@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@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.