mirror of https://lore.kernel.org/lkml/
 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, Kan Liang <kan.liang@intel.com>,
	Arnaldo Carvalho de Melo <acme@redhat.com>,
	Peter Zijlstra <peterz@infradead.org>,
	Ingo Molnar <mingo@redhat.com>
Subject: Re: [patch] perf_event_open.2: PERF_RECORD_MISC_PROC_MAP_PARSE_TIMEOUT
Date: Tue, 18 Oct 2016 08:14:56 +0200	[thread overview]
Message-ID: <0e5174be-17cd-83a5-3e1d-29d5ae720224@gmail.com> (raw)
In-Reply-To: <alpine.DEB.2.20.1610171048150.7683@macbook-air>

Hi Vince,

On 10/17/2016 04:50 PM, Vince Weaver wrote:
> 
> Linux 4.2 reserved a new bit from the misc field in the perf_event_open
> mmap sample buffer:
> PERF_RECORD_MISC_PROC_MAP_PARSE_TIMEOUT
> 
> Despite being reserved in the public include/uapi/linux/perf_event.h
> header file, this bit is never set by the kernel, rather it is used
> internally by the userspace "perf" utility to indicate that when
> attempting to parse all of the /proc/xxx/maps files for the sample
> it ended up taking too long so the scan was aborted.
> 
> Signed-off-by: Vince Weaver <vincent.weaver@maine.edu>

Thanks. Applied!

Cheers,

Michael


> diff --git a/man2/perf_event_open.2 b/man2/perf_event_open.2
> index fa8b1bd..59ad289 100644
> --- a/man2/perf_event_open.2
> +++ b/man2/perf_event_open.2
> @@ -1822,6 +1822,14 @@ See also
>  .BR PERF_RECORD_MISC_EXT_RESERVED " (since Linux 2.6.35)"
>  .\" commit 1676b8a077c352085d52578fb4f29350b58b6e74
>  This indicates there is extended data available (currently not used).
> +.TP
> +.B PERF_RECORD_MISC_PROC_MAP_PARSE_TIMEOUT
> +.\" commit 930e6fcd2bcce9bcd9d4aa7e755678d33f3fe6f4
> +This bit is not set by the kernel.
> +It is reserved for the userspace perf utility to indicate that
> +.I /proc/xxx/maps
> +parsing was taking too long and stopped and thus the mmap
> +records may be truncated.
>  .RE
>  .TP
>  .I type
> 


-- 
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:[~2016-10-18  6:15 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-10-17 14:50 Vince Weaver
2016-10-18  6:14 ` 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=0e5174be-17cd-83a5-3e1d-29d5ae720224@gmail.com \
    --to=mtk.manpages@gmail.com \
    --cc=acme@redhat.com \
    --cc=kan.liang@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-man@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=peterz@infradead.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

all inboxes | Powered by JetHome®