All of lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Zijlstra <peterz@infradead.org>
To: eranian@google.com
Cc: linux-kernel@vger.kernel.org, mingo@elte.hu, paulus@samba.org,
	davem@davemloft.net, fweisbec@gmail.com, robert.richter@amd.com,
	perfmon2-devel@lists.sf.net, eranian@gmail.com
Subject: Re: [PATCH] perf_events: add PERF_SAMPLE_BRANCH_STACK
Date: Wed, 07 Apr 2010 15:15:27 +0200	[thread overview]
Message-ID: <1270646127.20295.976.camel@laptop> (raw)
In-Reply-To: <4bbc7fcf.100db80a.6b9f.fffffb14@mx.google.com>

On Wed, 2010-04-07 at 14:45 +0200, Stephane Eranian wrote:
>         LBR is configured by default to record ALL taken branches.  On some
>         processors, it is possible to filter the type of branches. This will
>         be supported in a subsequent patch.
> 
>         On other processors, the sample type is allowed but will generate a
>         sample where nr=0 as is the case with other sampling types.

Right, so I already posted a patch like that:
  http://lkml.org/lkml/2010/3/4/160

and the reason its not merged is because there is no perf use-case for
it. Ingo wants to avoid merging ABI bits for which there is no userspace
around. We already have a few such things and we find that its too easy
to regress on those part.

So if you want this, please also implement a useful use-case in perf.


  reply	other threads:[~2010-04-07 13:15 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-04-07 12:45 [PATCH] perf_events: add PERF_SAMPLE_BRANCH_STACK Stephane Eranian
2010-04-07 13:15 ` Peter Zijlstra [this message]
2010-04-07 16:48   ` Stephane Eranian
2010-04-07 16:54     ` Peter Zijlstra

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=1270646127.20295.976.camel@laptop \
    --to=peterz@infradead.org \
    --cc=davem@davemloft.net \
    --cc=eranian@gmail.com \
    --cc=eranian@google.com \
    --cc=fweisbec@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=paulus@samba.org \
    --cc=perfmon2-devel@lists.sf.net \
    --cc=robert.richter@amd.com \
    /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.