linux-man.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Michael Kerrisk <mtk.manpages-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: Vince Weaver <vincent.weaver-e7X0jjDqjFGHXe+LvDLADg@public.gmane.org>
Cc: linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: minor perf_event_open() clarification
Date: Sat, 01 Jun 2013 22:53:47 +0200	[thread overview]
Message-ID: <51AA5F5B.8080407@gmail.com> (raw)
In-Reply-To: <alpine.DEB.2.10.1305301720060.13646-6xBS8L8d439fDsnSvq7Uq4Se7xf15W0s1dQoKJhdanU@public.gmane.org>

On 05/30/13 23:22, Vince Weaver wrote:
> 
> Clarify the perf_event_open() wakeup_events/wakeup_watermark fields a bit,
> based on info from kernel commit cfeb1d90a1b1.

Thanks Vince. Applied.

Cheers,

Michael


> Signed-off-by: Vince Weaver <vincent.weaver-e7X0jjDqjFGHXe+LvDLADg@public.gmane.org>
> 
> diff --git a/man2/perf_event_open.2 b/man2/perf_event_open.2
> index f3850f0..14b89ae 100644
> --- a/man2/perf_event_open.2
> +++ b/man2/perf_event_open.2
> @@ -870,6 +870,16 @@ happen before an overflow signal happens.
>  Which one is used is selected by the
>  .I watermark
>  bitflag.
> +
> +.I wakeup_events
> +only counts
> +.B PERF_RECORD_SAMPLE
> +record types.  
> +To  receive a signal for every incoming
> +.B PERF_RECORD
> +type set
> +.I wakeup_watermark
> +to 1.
>  .TP
>  .IR "bp_type" " (Since Linux 2.6.33)"
>  This chooses the breakpoint type.
> 

--
To unsubscribe from this list: send the line "unsubscribe linux-man" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

      parent reply	other threads:[~2013-06-01 20:53 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-30 21:22 minor perf_event_open() clarification Vince Weaver
     [not found] ` <alpine.DEB.2.10.1305301720060.13646-6xBS8L8d439fDsnSvq7Uq4Se7xf15W0s1dQoKJhdanU@public.gmane.org>
2013-06-01 20:53   ` Michael Kerrisk [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=51AA5F5B.8080407@gmail.com \
    --to=mtk.manpages-re5jqeeqqe8avxtiumwx3w@public.gmane.org \
    --cc=linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=vincent.weaver-e7X0jjDqjFGHXe+LvDLADg@public.gmane.org \
    /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;
as well as URLs for NNTP newsgroup(s).