All of lore.kernel.org
 help / color / mirror / Atom feed
From: Arnaldo Carvalho de Melo <acme@kernel.org>
To: Stephane Eranian <eranian@google.com>
Cc: Jiri Olsa <jolsa@kernel.org>, lkml <linux-kernel@vger.kernel.org>,
	Ingo Molnar <mingo@kernel.org>,
	Namhyung Kim <namhyung@kernel.org>,
	David Ahern <dsahern@gmail.com>,
	Alexander Shishkin <alexander.shishkin@linux.intel.com>,
	Peter Zijlstra <a.p.zijlstra@chello.nl>
Subject: Re: [PATCH 1/2] perf record: Synthesize features before events in pipe mode
Date: Wed, 14 Mar 2018 15:57:15 -0300	[thread overview]
Message-ID: <20180314185715.GE27335@kernel.org> (raw)
In-Reply-To: <CABPqkBS5u6Qkbw3qoq4ocgsMZSoVF2m_5pBQ5YTRnx3=mZG6LQ@mail.gmail.com>

Em Wed, Mar 14, 2018 at 11:45:14AM -0700, Stephane Eranian escreveu:
> On Wed, Mar 14, 2018 at 2:22 AM, Jiri Olsa <jolsa@kernel.org> wrote:
> > We need to synthesize events first, because some
> > features works on top of them (on report side).
> >
> > Link: http://lkml.kernel.org/n/tip-vz436m6fobfz8ykmuxo8phyy@git.kernel.org
> > Signed-off-by: Jiri Olsa <jolsa@kernel.org>
> 
> Works for me.
> Tested-by: Stephane Eranian <eranian@google.com>

Thanks for testing, will apply.

- Arnaldo

  reply	other threads:[~2018-03-14 18:57 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-03-14  9:22 [PATCH 1/2] perf record: Synthesize features before events in pipe mode Jiri Olsa
2018-03-14  9:22 ` [PATCH 2/2] perf report: Support forced leader feature " Jiri Olsa
2018-03-14 18:46   ` Stephane Eranian
2018-03-20  6:32   ` [tip:perf/core] " tip-bot for Jiri Olsa
2018-03-14 18:45 ` [PATCH 1/2] perf record: Synthesize features before events " Stephane Eranian
2018-03-14 18:57   ` Arnaldo Carvalho de Melo [this message]
2018-03-20  6:32 ` [tip:perf/core] " tip-bot for 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=20180314185715.GE27335@kernel.org \
    --to=acme@kernel.org \
    --cc=a.p.zijlstra@chello.nl \
    --cc=alexander.shishkin@linux.intel.com \
    --cc=dsahern@gmail.com \
    --cc=eranian@google.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.