public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
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>,
	Alexander Shishkin <alexander.shishkin@linux.intel.com>,
	Borislav Petkov <bp@alien8.de>,
	Frederic Weisbecker <fweisbec@gmail.com>,
	"H. Peter Anvin" <hpa@zytor.com>,
	Kaixu Xia <kaixu.xia@linaro.org>,
	Linus Torvalds <torvalds@linux-foundation.org>,
	Mike Galbraith <efault@gmx.de>, Robert Richter <rric@kernel.org>,
	Thomas Gleixner <tglx@linutronix.de>,
	adrian.hunter@intel.com, kan.liang@intel.com,
	markus.t.metzger@intel.com, mathieu.poirier@linaro.org
Subject: Re: [patch 07/11] perf_event_open.2: 4.1 add AUX_FLAG_OVERWRITE support
Date: Wed, 14 Oct 2015 08:33:42 +0200	[thread overview]
Message-ID: <561DF746.3090403@gmail.com> (raw)
In-Reply-To: <alpine.DEB.2.20.1507231313130.3742@vincent-weaver-1.umelst.maine.edu>

On 07/23/2015 07:13 PM, Vince Weaver wrote:
> 
> This manpage patch relates to the addition of the AUX sample flag
> AUX_FLAG_OVERWRITE as added in the following commit:

Thanks, Vince. Applied.

Cheers,

Michael



> 	commit 2023a0d2829e521fe6ad6b9907f3f90bfbf57142
> 	Author: Alexander Shishkin <alexander.shishkin@linux.intel.com>
> 
> 	perf: Support overwrite mode for the AUX area
> 
> 	Signed-off-by: Alexander Shishkin <alexander.shishkin@linux.intel.com>
> 	Signed-off-by: Peter Zijlstra (Intel) <peterz@infradead.org>
> 	Cc: Borislav Petkov <bp@alien8.de>
> 	Cc: Frederic Weisbecker <fweisbec@gmail.com>
> 	Cc: H. Peter Anvin <hpa@zytor.com>
> 	Cc: Kaixu Xia <kaixu.xia@linaro.org>
> 	Cc: Linus Torvalds <torvalds@linux-foundation.org>
> 	Cc: Mike Galbraith <efault@gmx.de>
> 	Cc: Paul Mackerras <paulus@samba.org>
> 	Cc: Robert Richter <rric@kernel.org>
> 	Cc: Stephane Eranian <eranian@google.com>
> 	Cc: Thomas Gleixner <tglx@linutronix.de>
> 	Cc: acme@infradead.org
> 	Cc: adrian.hunter@intel.com
> 	Cc: kan.liang@intel.com
> 	Cc: markus.t.metzger@intel.com
> 	Cc: mathieu.poirier@linaro.org
> 	Link: http://lkml.kernel.org/r/1421237903-181015-9-git-send-email-alexander.shishkin@linux.intel.com
> 	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 dfb0b64..238eb62 100644
> --- a/man2/perf_event_open.2
> +++ b/man2/perf_event_open.2
> @@ -1670,6 +1670,15 @@ rlimit as well as the
>  .I perf_event_mlock_kb
>  allowance.
>  
> +By default the AUX buffer will be truncated if it will not fit
> +in the available space in the ring buffer.
> +If the AUX buffer is mapped as a read only buffer, then it will
> +operate in ring buffer mode where old data will be overwritten
> +by new.
> +In overwrite mode it might not be possible to infer where the
> +new data began, and it is the consumer's job to disable
> +measurement while reading to avoid possible data races.
> +
>  The
>  .IR aux_head " and " aux_tail
>  ring buffer pointers have the same behavior and ordering
> @@ -2476,6 +2485,10 @@ describes the aux update.
>  .B PERF_AUX_FLAG_TRUNCATED
>  if set then the data returned was truncated to fit the available
>  buffer size.
> +.TP
> +.B PERF_AUX_FLAG_OVERWRITE
> +.\" commit 2023a0d2829e521fe6ad6b9907f3f90bfbf57142
> +if set then the data returned has overwritten previous data.
>  .RE
>  .RE
>  .RE
> 


-- 
Michael Kerrisk
Linux man-pages maintainer; http://www.kernel.org/doc/man-pages/
Linux/UNIX System Programming Training: http://man7.org/training/

      reply	other threads:[~2015-10-14  6:33 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-23 17:13 [patch 07/11] perf_event_open.2: 4.1 add AUX_FLAG_OVERWRITE support Vince Weaver
2015-10-14  6:33 ` 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=561DF746.3090403@gmail.com \
    --to=mtk.manpages@gmail.com \
    --cc=a.p.zijlstra@chello.nl \
    --cc=acme@kernel.org \
    --cc=adrian.hunter@intel.com \
    --cc=alexander.shishkin@linux.intel.com \
    --cc=bp@alien8.de \
    --cc=efault@gmx.de \
    --cc=eranian@google.com \
    --cc=fweisbec@gmail.com \
    --cc=hpa@zytor.com \
    --cc=kaixu.xia@linaro.org \
    --cc=kan.liang@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-man@vger.kernel.org \
    --cc=markus.t.metzger@intel.com \
    --cc=mathieu.poirier@linaro.org \
    --cc=mingo@redhat.com \
    --cc=rric@kernel.org \
    --cc=tglx@linutronix.de \
    --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