All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jiri Olsa <jolsa@redhat.com>
To: Srikar Dronamraju <srikar@linux.vnet.ibm.com>
Cc: Arnaldo Carvalho de Melo <acme@kernel.org>,
	Jiri Olsa <jolsa@kernel.org>, Namhyung Kim <namhyung@kernel.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Ravi Bangoria <ravi.bangoria@linux.ibm.com>,
	Naveen N Rao <naveen.n.rao@linux.vnet.ibm.com>
Subject: Re: [PATCH 0/2] Perf/stat: Solve problems with repeat and interval
Date: Wed, 4 Sep 2019 17:53:54 +0200	[thread overview]
Message-ID: <20190904155354.GC10468@krava> (raw)
In-Reply-To: <20190904094738.9558-1-srikar@linux.vnet.ibm.com>

On Wed, Sep 04, 2019 at 03:17:36PM +0530, Srikar Dronamraju wrote:
> There are some problems in perf stat when using a combination of repeat and
> interval options. This series tries to fix them.
> 
> Srikar Dronamraju (2):
>   perf/stat: Reset previous counts on repeat with interval
>   perf/stat: Fix a segmentation fault when using repeat forever
> 
>  tools/perf/builtin-stat.c |  5 ++++-
>  tools/perf/util/stat.c    | 17 +++++++++++++++++
>  tools/perf/util/stat.h    |  1 +
>  3 files changed, 22 insertions(+), 1 deletion(-)
> 
> -- 
> 2.18.1
> 

Acked-by: Jiri Olsa <jolsa@kernel.org>

thanks,
jirka

  parent reply	other threads:[~2019-09-04 15:53 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-09-04  9:47 [PATCH 0/2] Perf/stat: Solve problems with repeat and interval Srikar Dronamraju
2019-09-04  9:47 ` [PATCH 1/2] perf/stat: Reset previous counts on repeat with interval Srikar Dronamraju
2019-09-20 16:20   ` [tip: perf/urgent] perf stat: " tip-bot2 for Srikar Dronamraju
2019-09-04  9:47 ` [PATCH 2/2] perf/stat: Fix a segmentation fault when using repeat forever Srikar Dronamraju
2019-09-20 16:20   ` [tip: perf/urgent] perf stat: " tip-bot2 for Srikar Dronamraju
2019-09-04 15:53 ` Jiri Olsa [this message]
2019-09-11  4:14 ` [PATCH 0/2] Perf/stat: Solve problems with repeat and interval Ravi Bangoria
2019-09-18 23:05   ` 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=20190904155354.GC10468@krava \
    --to=jolsa@redhat.com \
    --cc=acme@kernel.org \
    --cc=jolsa@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=namhyung@kernel.org \
    --cc=naveen.n.rao@linux.vnet.ibm.com \
    --cc=ravi.bangoria@linux.ibm.com \
    --cc=srikar@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.