Re: minor perf_event_open() clarification

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



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@xxxxxxxxx>
> 
> 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@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html




[Index of Archives]     [Kernel Documentation]     [Netdev]     [Linux Ethernet Bridging]     [Linux Wireless]     [Kernel Newbies]     [Security]     [Linux for Hams]     [Netfilter]     [Bugtraq]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux RAID]     [Linux Admin]     [Samba]

  Powered by Linux