mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Andi Kleen <ak@linux.intel.com>
To: Ingo Molnar <mingo@kernel.org>
Cc: Stephane Eranian <eranian@google.com>,
	linux-kernel@vger.kernel.org, acme@redhat.com,
	peterz@infradead.org, mingo@elte.hu, jolsa@redhat.com,
	namhyung@kernel.org, khandual@linux.vnet.ibm.com
Subject: Re: [PATCH 2/4] perf/x86: add support for PERF_SAMPLE_BRANCH_CALL
Date: Tue, 13 Oct 2015 08:40:26 -0700	[thread overview]
Message-ID: <20151013154026.GB7750@tassilo.jf.intel.com> (raw)
In-Reply-To: <20151013134004.GA8843@gmail.com>

> I'm wondering how frequent zero-length calls are. If they still occur in typical 
> user-space, would it make sense to also have a separate branch sampling type for 
> zero length calls?

Apparently not too old icc compiled 32bit PIC binaries still contain it.
For gcc it was fixed for much longer.

But I'm not sure it's that interesting to sample by itself.

> push the current IP on the stack:
> 
> 	call next_addr
> next_addr:
> 	pop %reg
> 
> which can take over 10 cycles on certain microarchitectures (and it unbalances 
> whatever call stack tracking/caching the CPU does as well).
> 
> So it might make sense to analyze them separately. I guess that's the reason why 
> Intel added a separate flag for them in the PMU.

X86_BR_ZERO_CALL is only a software filter. There's no direct support for it
in the Intel hardware. It was added to make the LBR call stack more reliable,
which otherwise gets messed up by the zero length calls.

-Andi

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

  reply	other threads:[~2015-10-13 15:40 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-13  7:09 [PATCH 0/4] perf: add ability to sample direct call branches Stephane Eranian
2015-10-13  7:09 ` [PATCH 1/4] perf: add PERF_SAMPLE_BRANCH_CALL Stephane Eranian
2015-10-20  9:35   ` [tip:perf/core] perf: Add PERF_SAMPLE_BRANCH_CALL tip-bot for Stephane Eranian
2015-10-13  7:09 ` [PATCH 2/4] perf/x86: add support for PERF_SAMPLE_BRANCH_CALL Stephane Eranian
2015-10-13 13:40   ` Ingo Molnar
2015-10-13 15:40     ` Andi Kleen [this message]
2015-10-14  0:39     ` Stephane Eranian
2015-10-20  9:36   ` [tip:perf/core] perf/x86: Add " tip-bot for Stephane Eranian
2015-10-13  7:09 ` [PATCH 3/4] perf/powerpc: add " Stephane Eranian
2015-10-20  9:36   ` [tip:perf/core] perf/powerpc: Add " tip-bot for Stephane Eranian
2015-10-13  7:09 ` [PATCH 4/4] perf record: add ability to sample call branches Stephane Eranian
2015-10-20  9:36   ` [tip:perf/core] perf record: Add " tip-bot for Stephane Eranian

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=20151013154026.GB7750@tassilo.jf.intel.com \
    --to=ak@linux.intel.com \
    --cc=acme@redhat.com \
    --cc=eranian@google.com \
    --cc=jolsa@redhat.com \
    --cc=khandual@linux.vnet.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=mingo@kernel.org \
    --cc=namhyung@kernel.org \
    --cc=peterz@infradead.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®