From: Arnaldo Carvalho de Melo <acme@kernel.org>
To: Jiri Olsa <jolsa@redhat.com>
Cc: Ravi Bangoria <ravi.bangoria@linux.ibm.com>,
alexander.shishkin@linux.intel.com, namhyung@kernel.org,
yao.jin@linux.intel.com, linux-kernel@vger.kernel.org,
yuzhoujian@didichuxing.com, tmricht@linux.vnet.ibm.com,
anton@samba.org
Subject: Re: [PATCH 1/2] perf stat: Use perf_evsel__is_clocki() for clock events
Date: Thu, 15 Nov 2018 11:22:31 -0800 [thread overview]
Message-ID: <20181115192231.GA13587@kernel.org> (raw)
In-Reply-To: <20181115135505.GA598@krava>
Em Thu, Nov 15, 2018 at 02:55:05PM +0100, Jiri Olsa escreveu:
> On Thu, Nov 15, 2018 at 03:25:32PM +0530, Ravi Bangoria wrote:
> > We already have function to check if a given event is either
> > SW_CPU_CLOCK or SW_TASK_CLOCK. Utilize it.
> >
> > Signed-off-by: Ravi Bangoria <ravi.bangoria@linux.ibm.com>
>
> Acked-by: Jiri Olsa <jolsa@kernel.org>
Thanks, applied to perf/core.
next prev parent reply other threads:[~2018-11-15 19:22 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-15 9:55 [PATCH 1/2] perf stat: Use perf_evsel__is_clocki() for clock events Ravi Bangoria
2018-11-15 9:55 ` [RFC 2/2] perf stat: Fix shadow stats " Ravi Bangoria
2018-11-15 14:17 ` Jiri Olsa
2018-11-16 4:28 ` [PATCH] " Ravi Bangoria
2018-11-16 13:35 ` Jiri Olsa
2018-11-26 18:45 ` Arnaldo Carvalho de Melo
2018-11-27 8:20 ` Ravi Bangoria
2018-11-27 12:37 ` Arnaldo Carvalho de Melo
2018-12-14 20:19 ` [tip:perf/core] " tip-bot for Ravi Bangoria
2018-12-18 13:46 ` tip-bot for Ravi Bangoria
2018-11-15 13:55 ` [PATCH 1/2] perf stat: Use perf_evsel__is_clocki() " Jiri Olsa
2018-11-15 19:22 ` Arnaldo Carvalho de Melo [this message]
2018-11-22 7:13 ` [tip:perf/core] " tip-bot for Ravi Bangoria
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=20181115192231.GA13587@kernel.org \
--to=acme@kernel.org \
--cc=alexander.shishkin@linux.intel.com \
--cc=anton@samba.org \
--cc=jolsa@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=namhyung@kernel.org \
--cc=ravi.bangoria@linux.ibm.com \
--cc=tmricht@linux.vnet.ibm.com \
--cc=yao.jin@linux.intel.com \
--cc=yuzhoujian@didichuxing.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox