mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Peter Zijlstra <peterz@infradead.org>
To: eranian@gmail.com
Cc: Vince Weaver <vincent.weaver@maine.edu>,
	LKML <linux-kernel@vger.kernel.org>,
	Ingo Molnar <mingo@redhat.com>, Paul Mackerras <paulus@samba.org>,
	Arnaldo Carvalho de Melo <acme@ghostprotocols.net>
Subject: Re: [patch, resend] perf: export struct perf_branch_entry to userspace
Date: Mon, 26 Aug 2013 14:12:02 +0200	[thread overview]
Message-ID: <20130826121202.GM31370@twins.programming.kicks-ass.net> (raw)
In-Reply-To: <CAMsRxf+FU4UhVvgVCww5CuNwfqOk915_-TKK4fC7daFoweMnQQ@mail.gmail.com>

On Mon, Aug 26, 2013 at 11:31:11AM +0200, Stephane Eranian wrote:
> On Fri, Aug 23, 2013 at 9:51 PM, Vince Weaver <vincent.weaver@maine.edu> wrote:
> >
> > On Mon, 8 Jul 2013, Vince Weaver wrote:
> >
> > If PERF_SAMPLE_BRANCH_STACK is enabled then samples are returned
> > with the format { u64 from, to, flags } but the flags layout
> > is not specified.
> >
> > This field has the type struct perf_branch_entry; move this
> > definition into include/uapi/linux/perf_event.h so users can
> > access these fields.
> >
> > This is similar to the existing inclusion of perf_mem_data_src in
> > the include/uapi/linux/perf_event.h file.
> >
> > Signed-off-by: Vince Weaver <vincent.weaver@maine.edu>
> >
> This makes sense.
> Acked-by: Stephane Eranian <eranian@google.com>

Thanks!

  reply	other threads:[~2013-08-26 12:12 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-08 19:25 Vince Weaver
2013-08-23 19:51 ` [patch, resend] " Vince Weaver
2013-08-26  9:31   ` Stephane Eranian
2013-08-26 12:12     ` Peter Zijlstra [this message]
2013-09-02  7:42   ` [tip:perf/core] perf: Export " tip-bot for Vince Weaver

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=20130826121202.GM31370@twins.programming.kicks-ass.net \
    --to=peterz@infradead.org \
    --cc=acme@ghostprotocols.net \
    --cc=eranian@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=paulus@samba.org \
    --cc=vincent.weaver@maine.edu \
    /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
Powered by JetHome