From: David Ahern <dsahern@gmail.com>
To: Christian Borntraeger <borntraeger@de.ibm.com>,
Jiri Olsa <jolsa@kernel.org>,
Arnaldo Carvalho de Melo <acme@redhat.com>
Cc: linux-kernel@vger.kernel.org,
Alexander Yarygin <yarygin@linux.vnet.ibm.com>
Subject: Re: [PATCH] perf kvm stat live: mark events as (x86 only) in help output
Date: Wed, 10 Dec 2014 06:57:13 -0700 [thread overview]
Message-ID: <54885139.5090901@gmail.com> (raw)
In-Reply-To: <1418218090-20718-1-git-send-email-borntraeger@de.ibm.com>
On 12/10/14 6:28 AM, Christian Borntraeger wrote:
> From: Alexander Yarygin <yarygin@linux.vnet.ibm.com>
>
> The mmio and ioport events are useful only on x86.
>
> Signed-off-by: Alexander Yarygin <yarygin@linux.vnet.ibm.com>
> Signed-off-by: Christian Borntraeger <borntraeger@de.ibm.com>
> ---
> tools/perf/builtin-kvm.c | 3 ++-
> 1 file changed, 2 insertions(+), 1 deletion(-)
>
> diff --git a/tools/perf/builtin-kvm.c b/tools/perf/builtin-kvm.c
> index b65eb050..612e8f9 100644
> --- a/tools/perf/builtin-kvm.c
> +++ b/tools/perf/builtin-kvm.c
> @@ -1268,7 +1268,8 @@ static int kvm_events_live(struct perf_kvm_stat *kvm,
> OPT_UINTEGER('d', "display", &kvm->display_time,
> "time in seconds between display updates"),
> OPT_STRING(0, "event", &kvm->report_event, "report event",
> - "event for reporting: vmexit, mmio, ioport"),
> + "event for reporting: "
> + "vmexit, mmio (x86 only), ioport (x86 only)"),
> OPT_INTEGER(0, "vcpu", &kvm->trace_vcpu,
> "vcpu id to report"),
> OPT_STRING('k', "key", &kvm->sort_key, "sort-key",
>
Acked-by: David Ahern <dsahern@gmail.com>
next prev parent reply other threads:[~2014-12-10 13:57 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-10 13:28 [PATCH] perf kvm stat live: mark events as (x86 only) in help output Christian Borntraeger
2014-12-10 13:57 ` David Ahern [this message]
2014-12-10 15:10 ` Arnaldo Carvalho de Melo
2014-12-12 8:18 ` [tip:perf/urgent] perf kvm stat live: Mark " tip-bot for Alexander Yarygin
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=54885139.5090901@gmail.com \
--to=dsahern@gmail.com \
--cc=acme@redhat.com \
--cc=borntraeger@de.ibm.com \
--cc=jolsa@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--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.