From: "Michael Kerrisk (man-pages)" <mtk.manpages@gmail.com>
To: Vince Weaver <vincent.weaver@maine.edu>
Cc: mtk.manpages@gmail.com, linux-man@vger.kernel.org,
linux-kernel@vger.kernel.org,
Peter Zijlstra <a.p.zijlstra@chello.nl>,
Ingo Molnar <mingo@redhat.com>,
Arnaldo Carvalho de Melo <acme@kernel.org>,
Stephane Eranian <eranian@google.com>,
Jiri Olsa <jolsa@redhat.com>,
Andy Lutomirski <luto@amacapital.net>,
Kan Liang <kan.liang@intel.com>,
Linus Torvalds <torvalds@linux-foundation.org>
Subject: Re: [patch 01/11] perf_event_open.2: 4.1 PERF_SAMPLE_BRANCH_CALL_STACK
Date: Wed, 14 Oct 2015 08:26:08 +0200 [thread overview]
Message-ID: <561DF580.50509@gmail.com> (raw)
In-Reply-To: <alpine.DEB.2.20.1507231307280.3742@vincent-weaver-1.umelst.maine.edu>
On 07/23/2015 07:08 PM, Vince Weaver wrote:
>
> This manpage patch relates to the addition of the
> PERF_SAMPLE_BRANCH_CALL_STACK functionaliry added in the following
> commit:
>
> commit 2c44b1936bb3b135a3fac8b3493394d42e51cf70 Author: Peter
> Zijlstra <peterz@infradead.org>
>
> perf/x86/intel: Expose LBR callstack to user space tooling
>
> With LBR call stack feature enable, there are three callchain
> options. Enable the 3rd callchain option (LBR callstack) to user
> space tooling.
Thanks, Vince. Applied.
Cheers,
Michael
> Signed-off-by: Peter Zijlstra (Intel) <peterz@infradead.org> Cc: Jiri
> Olsa <jolsa@redhat.com> Cc: Arnaldo Carvalho de Melo
> <acme@kernel.org> Cc: Andy Lutomirski <luto@amacapital.net> Cc: Kan
> Liang <kan.liang@intel.com> Cc: Linus Torvalds
> <torvalds@linux-foundation.org> Cc: Paul Mackerras
> <paulus@samba.org> Cc: Vince Weaver <vincent.weaver@maine.edu> Cc:
> linux-api@vger.kernel.org Link:
> http://lkml.kernel.org/r/20141105093759.GQ10501@worktop.programming.kicks-ass.net
>
> Signed-off-by: Ingo Molnar <mingo@kernel.org>
> Signed-off-by: Vince Weaver <vincent.weaver@maine.edu>
>
> diff --git a/man2/perf_event_open.2 b/man2/perf_event_open.2 index
> 856ec64..71bfb17 100644 --- a/man2/perf_event_open.2 +++
> b/man2/perf_event_open.2 @@ -1240,6 +1240,11 @@ Branch in
> transactional memory transaction. .BR PERF_SAMPLE_BRANCH_NO_TX "
> (since Linux 3.11)" .\" commit
> 135c5612c460f89657c4698fe2ea753f6f667963 Branch not in transactional
> memory transaction. +.BR PERF_SAMPLE_BRANCH_CALL_STACK " (since Linux
> 4.1)" +.\" commit 2c44b1936bb3b135a3fac8b3493394d42e51cf70 +Branch is
> part of a hardware generated call stack. +This requires hardware
> support, currently only found +on Intel x86 Haswell or newer. .RE
>
> .TP -- To unsubscribe from this list: send the line "unsubscribe
> linux-man" in the body of a message to majordomo@vger.kernel.org More
> majordomo info at http://vger.kernel.org/majordomo-info.html
>
--
Michael Kerrisk
Linux man-pages maintainer; http://www.kernel.org/doc/man-pages/
Linux/UNIX System Programming Training: http://man7.org/training/
prev parent reply other threads:[~2015-10-14 6:26 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-23 17:08 [patch 01/11] perf_event_open.2: 4.1 PERF_SAMPLE_BRANCH_CALL_STACK Vince Weaver
2015-10-14 6:26 ` Michael Kerrisk (man-pages) [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=561DF580.50509@gmail.com \
--to=mtk.manpages@gmail.com \
--cc=a.p.zijlstra@chello.nl \
--cc=acme@kernel.org \
--cc=eranian@google.com \
--cc=jolsa@redhat.com \
--cc=kan.liang@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-man@vger.kernel.org \
--cc=luto@amacapital.net \
--cc=mingo@redhat.com \
--cc=torvalds@linux-foundation.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