From: Arnaldo Carvalho de Melo <acme@kernel.org>
To: Adrian Hunter <adrian.hunter@intel.com>
Cc: Jiri Olsa <jolsa@kernel.org>, lkml <linux-kernel@vger.kernel.org>,
David Ahern <dsahern@gmail.com>, Ingo Molnar <mingo@kernel.org>,
Namhyung Kim <namhyung@kernel.org>,
Peter Zijlstra <a.p.zijlstra@chello.nl>
Subject: Re: [PATCH 0/7] perf stat: Change event enable code
Date: Mon, 7 Dec 2015 18:09:08 -0300 [thread overview]
Message-ID: <20151207210908.GC11564@kernel.org> (raw)
In-Reply-To: <1449133606-14429-1-git-send-email-jolsa@kernel.org>
Em Thu, Dec 03, 2015 at 10:06:39AM +0100, Jiri Olsa escreveu:
> hi,
> while testing ftrace:function event I noticed we create
> stat counters as enabled (except for enable_on_exec couters).
>
> This way we count also filter setup and other config code
> which might be crucial for some events.
>
> Posponing the events enable once everything is ready.
>
> The last patch is RFC as I wasn't sure there's some hidden
> catch about perf_evlist__(enable|disable)_event functions
> I missed.. Adrian?
They look the same, Adrian?
Applied the first 6, will give some more time to Adrian to chime in.
- Arnaldo
next prev parent reply other threads:[~2015-12-07 21:09 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-03 9:06 [PATCH 0/7] perf stat: Change event enable code Jiri Olsa
2015-12-03 9:06 ` [PATCH 1/7] perf tools: Use event maps directly in perf_evsel__enable Jiri Olsa
2015-12-08 4:33 ` [tip:perf/core] perf evsel: " tip-bot for Jiri Olsa
2015-12-03 9:06 ` [PATCH 2/7] perf tools: Introduce perf_evsel__disable function Jiri Olsa
2015-12-08 4:33 ` [tip:perf/core] perf evsel: Introduce disable() method tip-bot for Jiri Olsa
2015-12-03 9:06 ` [PATCH 3/7] perf tools: Factor perf_evlist__(enable|disable) functions Jiri Olsa
2015-12-08 4:33 ` [tip:perf/core] perf evlist: " tip-bot for Jiri Olsa
2015-12-03 9:06 ` [PATCH 4/7] perf stat: Use perf_evlist__enable in handle_initial_delay Jiri Olsa
2015-12-08 4:34 ` [tip:perf/core] " tip-bot for Jiri Olsa
2015-12-03 9:06 ` [PATCH 5/7] perf stat: Create events as disabled Jiri Olsa
2015-12-08 4:34 ` [tip:perf/core] " tip-bot for Jiri Olsa
2015-12-03 9:06 ` [PATCH 6/7] perf stat: Move enable_on_exec setup under earlier code Jiri Olsa
2015-12-08 4:34 ` [tip:perf/core] " tip-bot for Jiri Olsa
2015-12-03 9:06 ` [RFC 7/7] perf tools: Remove perf_evlist__(enable|disable)_event functions Jiri Olsa
2015-12-03 9:09 ` [PATCH 0/7] perf stat: Change event enable code Jiri Olsa
2015-12-07 21:09 ` Arnaldo Carvalho de Melo [this message]
2015-12-08 7:29 ` Adrian Hunter
2015-12-08 13:53 ` Arnaldo Carvalho de Melo
2015-12-09 13:44 ` Adrian Hunter
2015-12-11 12:42 ` Adrian Hunter
2015-12-16 15:55 ` Jiri Olsa
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=20151207210908.GC11564@kernel.org \
--to=acme@kernel.org \
--cc=a.p.zijlstra@chello.nl \
--cc=adrian.hunter@intel.com \
--cc=dsahern@gmail.com \
--cc=jolsa@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=namhyung@kernel.org \
/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.