All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@kernel.org>
To: Arnaldo Carvalho de Melo <acme@kernel.org>
Cc: linux-kernel@vger.kernel.org,
	Adrian Hunter <adrian.hunter@intel.com>,
	David Ahern <dsahern@gmail.com>, Jiri Olsa <jolsa@redhat.com>,
	Matt Fleming <matt@codeblueprint.co.uk>,
	Namhyung Kim <namhyung@kernel.org>,
	Peter Zijlstra <a.p.zijlstra@chello.nl>,
	Raphael Beamonte <raphael.beamonte@gmail.com>,
	Steven Rostedt <rostedt@goodmis.org>,
	Arnaldo Carvalho de Melo <acme@redhat.com>
Subject: Re: [GIT PULL 0/2] perf/urgent fixes
Date: Fri, 4 Sep 2015 11:01:54 +0200	[thread overview]
Message-ID: <20150904090153.GB17456@gmail.com> (raw)
In-Reply-To: <1441296129-31530-1-git-send-email-acme@kernel.org>


* Arnaldo Carvalho de Melo <acme@kernel.org> wrote:

> Hi Ingo,
> 
> 	Please consider pulling,
> 
> - Arnaldo
> 
> The following changes since commit 5b923564ccf43f92969c9e0fd199c8c5db657039:
> 
>   Merge tag 'perf-urgent-for-mingo' of git://git.kernel.org/pub/scm/linux/kernel/git/acme/linux into perf/urgent (2015-09-02 09:22:53 +0200)
> 
> are available in the git repository at:
> 
>   git://git.kernel.org/pub/scm/linux/kernel/git/acme/linux.git tags/perf-urgent-for-mingo
> 
> for you to fetch changes up to 53ff6bc37be449f546158a39c528d7814dfb15a1:
> 
>   perf tools: Fix use of wrong event when processing exit events (2015-09-02 17:46:26 -0300)
> 
> ----------------------------------------------------------------
> perf/urgent fixes:
> 
> - In some cases where perf_event.fork.{pid,tid} should be used we were instead
>   using perf_event.comm.{pid,tid}, which is not a problem for for the 'pid'
>   case, that sits in the same place in these union_perf_event members, but
>   comm.tid sits where fork.ppid is, oops.
> 
>   These cases were considered as (potentially) problematic:
> 
>    - 'perf script' with !sample_id_all, i.e. only non old kernels without
>       perf_event_attr.sample_id_all.
> 
>    - intel_pt could be affected when decoding without timestamps, as the exit
>      event is only used to flush out data which anyway gets flushed at the
>      end of the session.
> 
>    - intel_bts also uses the exit event to flush data which would probably not
>      cause errors as it would get flushed at the end of the session instead.
> 
>   Fix it. (Adrian Hunter)
> 
> - Due to relaxing the compiler checks for bison generated files, we missed
>   updating one parse_events_add_pmu() caller when this function had its
>   prototype changed, fix it. (Jiri Olsa)
> 
> Signed-off-by: Arnaldo Carvalho de Melo <acme@redhat.com>
> 
> ----------------------------------------------------------------
> Adrian Hunter (1):
>       perf tools: Fix use of wrong event when processing exit events
> 
> Jiri Olsa (1):
>       perf tools: Fix parse_events_add_pmu caller
> 
>  tools/perf/builtin-script.c    | 4 ++--
>  tools/perf/util/intel-bts.c    | 2 +-
>  tools/perf/util/intel-pt.c     | 2 +-
>  tools/perf/util/parse-events.y | 2 +-
>  4 files changed, 5 insertions(+), 5 deletions(-)

Pulled, thanks a lot Arnaldo!

	Ingo

  parent reply	other threads:[~2015-09-04  9:02 UTC|newest]

Thread overview: 68+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-03 16:02 [GIT PULL 0/2] perf/urgent fixes Arnaldo Carvalho de Melo
2015-09-03 16:02 ` [PATCH 1/2] perf tools: Fix parse_events_add_pmu caller Arnaldo Carvalho de Melo
2015-09-03 16:02 ` [PATCH 2/2] perf tools: Fix use of wrong event when processing exit events Arnaldo Carvalho de Melo
2015-09-04  9:01 ` Ingo Molnar [this message]
  -- strict thread matches above, loose matches on Subject: below --
2018-09-18 15:37 [GIT PULL 0/2] perf/urgent fixes Arnaldo Carvalho de Melo
2018-09-18 15:37 ` Arnaldo Carvalho de Melo
2018-09-19 11:34 ` Ingo Molnar
2017-10-27 19:50 Arnaldo Carvalho de Melo
2017-07-04 19:29 Arnaldo Carvalho de Melo
2017-07-05  7:12 ` Ingo Molnar
2016-03-30 22:13 Arnaldo Carvalho de Melo
2016-03-31  6:28 ` Ingo Molnar
2016-03-24 15:52 Arnaldo Carvalho de Melo
2016-03-25  8:43 ` Ingo Molnar
2016-02-01 17:13 Arnaldo Carvalho de Melo
2015-09-22 15:22 Arnaldo Carvalho de Melo
2015-09-23  7:42 ` Ingo Molnar
2015-07-28 16:09 Arnaldo Carvalho de Melo
2015-07-31  7:59 ` Ingo Molnar
2015-07-15 15:20 Arnaldo Carvalho de Melo
2015-07-17 12:17 ` Ingo Molnar
2015-07-13 19:19 Arnaldo Carvalho de Melo
2015-07-15 11:34 ` Ingo Molnar
2015-05-12 21:18 Arnaldo Carvalho de Melo
2015-05-13  6:22 ` Ingo Molnar
2015-05-05 22:16 Arnaldo Carvalho de Melo
2015-05-06  2:55 ` Ingo Molnar
2014-06-23  7:54 Jiri Olsa
2014-06-25  5:41 ` Ingo Molnar
2014-06-04 13:26 Jiri Olsa
2014-06-05  7:53 ` Ingo Molnar
2014-04-15 13:07 Jiri Olsa
2014-04-15 17:26 ` Ingo Molnar
2014-02-28 21:25 Arnaldo Carvalho de Melo
2014-03-01  9:14 ` Ingo Molnar
2014-02-24 19:10 Arnaldo Carvalho de Melo
2014-02-27 11:49 ` Ingo Molnar
2014-01-23 19:38 Arnaldo Carvalho de Melo
2014-01-25  7:23 ` Ingo Molnar
2013-10-28 14:45 Arnaldo Carvalho de Melo
2013-10-28 14:59 ` Ingo Molnar
2013-01-22 22:07 Arnaldo Carvalho de Melo
2013-01-10 20:44 Arnaldo Carvalho de Melo
2012-10-30 13:02 Arnaldo Carvalho de Melo
2012-11-13 17:55 ` Ingo Molnar
2012-05-02 16:27 Arnaldo Carvalho de Melo
2012-05-02 17:34 ` Ingo Molnar
2012-04-16 20:29 Arnaldo Carvalho de Melo
2011-12-07 15:47 Arnaldo Carvalho de Melo
2011-12-07 22:24 ` Ingo Molnar
2011-11-16 14:51 Arnaldo Carvalho de Melo
2011-12-05  9:33 ` Ingo Molnar
2011-05-26 18:05 Arnaldo Carvalho de Melo
2011-05-26 19:17 ` Ingo Molnar
2011-05-15 16:38 Arnaldo Carvalho de Melo
2011-05-15 17:54 ` Ingo Molnar
2011-04-18 15:23 Arnaldo Carvalho de Melo
2011-04-18 15:36 ` Ingo Molnar
2011-03-30  2:29 Arnaldo Carvalho de Melo
2011-03-30  7:06 ` Ingo Molnar
2011-01-22  1:16 Arnaldo Carvalho de Melo
2011-01-18  1:10 Arnaldo Carvalho de Melo
2011-01-18  8:01 ` Ingo Molnar
2010-12-12 15:16 Arnaldo Carvalho de Melo
2010-07-22 20:36 Arnaldo Carvalho de Melo
2010-07-23  7:07 ` Ingo Molnar
2010-06-01 12:17 Arnaldo Carvalho de Melo
2010-06-02  7:13 ` Ingo Molnar

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=20150904090153.GB17456@gmail.com \
    --to=mingo@kernel.org \
    --cc=a.p.zijlstra@chello.nl \
    --cc=acme@kernel.org \
    --cc=acme@redhat.com \
    --cc=adrian.hunter@intel.com \
    --cc=dsahern@gmail.com \
    --cc=jolsa@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=matt@codeblueprint.co.uk \
    --cc=namhyung@kernel.org \
    --cc=raphael.beamonte@gmail.com \
    --cc=rostedt@goodmis.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.