All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andi Kleen <ak@linux.intel.com>
To: Adrian Hunter <adrian.hunter@intel.com>
Cc: Andi Kleen <andi@firstfloor.org>,
	Arnaldo Carvalho de Melo <acme@kernel.org>,
	jolsa@kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/3] perf pt: Mark PT return events as "return"
Date: Tue, 24 May 2016 12:28:43 -0700	[thread overview]
Message-ID: <20160524192843.GC22049@tassilo.jf.intel.com> (raw)
In-Reply-To: <5744AA15.8010306@intel.com>

> It looks like it synths 2 samples for each return (one "branches" and
> one "return"), which I would expect would mess up the thread_stack pairing
> calls and returns.  Did you intend to have 2 samples?

No it should be only one. I'll check.

-Andi

-- 
ak@linux.intel.com -- Speaking for myself only

      reply	other threads:[~2016-05-24 19:28 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-05-24  0:52 [PATCH 1/3] perf pt: Mark PT return events as "return" Andi Kleen
2016-05-24  0:52 ` [PATCH 2/3] perf util: Move get_main_thread to thread.c Andi Kleen
2016-05-24 14:56   ` Arnaldo Carvalho de Melo
2016-06-02  6:30   ` [tip:perf/core] perf thread: Adopt get_main_thread from db-export.c tip-bot for Andi Kleen
2016-05-24  0:52 ` [PATCH 3/3] perf script: Support callindent Andi Kleen
2016-05-24 14:57 ` [PATCH 1/3] perf pt: Mark PT return events as "return" Arnaldo Carvalho de Melo
2016-05-24 16:26   ` Adrian Hunter
2016-05-24 18:10     ` Arnaldo Carvalho de Melo
2016-05-24 19:05       ` Andi Kleen
2016-05-24 19:23         ` Adrian Hunter
2016-05-24 19:28           ` Andi Kleen [this message]

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=20160524192843.GC22049@tassilo.jf.intel.com \
    --to=ak@linux.intel.com \
    --cc=acme@kernel.org \
    --cc=adrian.hunter@intel.com \
    --cc=andi@firstfloor.org \
    --cc=jolsa@kernel.org \
    --cc=linux-kernel@vger.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.