All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Michael Kerrisk (man-pages)" <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: [patch] perf_event_open.2 PERF_EVENT_IOC_PERIOD update
Date: Wed, 30 Oct 2013 14:46:01 +1300	[thread overview]
Message-ID: <527064D9.4000907@gmail.com> (raw)
In-Reply-To: <alpine.DEB.2.10.1310280927280.22634-6xBS8L8d439fDsnSvq7Uq4Se7xf15W0s1dQoKJhdanU@public.gmane.org>

On 29.10.2013 02:33, Vince Weaver wrote:
> 
> The PERF_EVENT_IOC_PERIOD ioctl was broken until 2.6.36, and it turns out 
> that the ARM architecture has some differing behavior too.

Applied.

Thanks,

Michael


> Reported-by: Andreas Sandberg <andreas.sandberg-1zs4UD6AkMk@public.gmane.org>
> 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 f4cb5bd..f337a27 100644
> --- a/man2/perf_event_open.2
> +++ b/man2/perf_event_open.2
> @@ -1976,11 +1976,17 @@ reset, even if the event specified is not the group leader
>  (but see BUGS).
>  .TP
>  .B PERF_EVENT_IOC_PERIOD
> -IOC_PERIOD is the command to update the period; it
> -does not update the current period but instead defers until next.
> +This updates the overflow period for the event.
> +On most architectures the new period does not take effect until 
> +after the next overflow happens;
> +on ARM since Linux 3.7 the period is updated immediately.
>  
>  The argument is a pointer to a 64-bit value containing the
>  desired new period.
> +
> +Prior to Linux 2.6.36 this ioctl always failed due to a bug
> +in the kernel.
> +
>  .TP
>  .B PERF_EVENT_IOC_SET_OUTPUT
>  This tells the kernel to report event notifications to the specified
> 


-- 
Michael Kerrisk
Linux man-pages maintainer; http://www.kernel.org/doc/man-pages/
My next Linux/UNIX system programming course:
--
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-10-30  1:46 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-10-28 13:33 [patch] perf_event_open.2 PERF_EVENT_IOC_PERIOD update Vince Weaver
     [not found] ` <alpine.DEB.2.10.1310280927280.22634-6xBS8L8d439fDsnSvq7Uq4Se7xf15W0s1dQoKJhdanU@public.gmane.org>
2013-10-30  1:46   ` 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=527064D9.4000907@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.