public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Robert Richter <rric@kernel.org>
To: Vince Weaver <vince@deater.net>
Cc: Peter Zijlstra <peterz@infradead.org>,
	Ingo Molnar <mingo@kernel.org>,
	Arnaldo Carvalho de Melo <acme@infradead.org>,
	Borislav Petkov <bp@alien8.de>, Jiri Olsa <jolsa@redhat.com>,
	linux-kernel@vger.kernel.org,
	Vince Weaver <vincent.weaver@maine.edu>
Subject: Re: [PATCH v3 12/12] [RFC] perf, persistent: ioctl functions to control persistency
Date: Tue, 27 Aug 2013 14:17:44 +0200	[thread overview]
Message-ID: <20130827121744.GE15884@rric.localhost> (raw)
In-Reply-To: <20130823100747.GC10223@rric.localhost>

> > On Thu, 22 Aug 2013, Robert Richter wrote:
> > > This is for Linux man-pages:

Updated description below.

-Robert



Author: Robert Richter <robert.richter@linaro.org>
Date:   Tue Aug 13 11:22:22 2013 +0200

    [RFC] perf, persistent: ioctl functions to control persistency
    
    Implementing ioctl functions to control persistent events. There are
    functions to detach or attach an event to or from a process. The
    PERF_EVENT_IOC_DETACH ioctl call makes an event persistent. After
    closing the event's fd it runs then in the background of the system
    without the need of a controlling process. The perf_event_open()
    syscall can be used to reopen the event by any process. The
    PERF_EVENT_IOC_ATTACH ioctl attaches the event again so that it is
    removed after closing the event's fd.
    
    This is for Linux man-pages:
    
        type ...
    
            PERF_TYPE_PERSISTENT (Since Linux 3.xx)
    
                Open a persistent event that is already running in the
                background of the system. There is a unique identifier for
                each persistent event that needs to be specified in the
                event's attribute config field.  Persistent events are
                listed under:
    
                  /sys/bus/event_source/devices/persistent/
    
                See PERF_EVENT_IOC_DETACH how to create a persistent
                event. The instance creating such an event should also be
                responsible for removing it.
    
        ...
        persistent : 41, /* always-on event */
        ...
    
        persistent: (Since Linux 3.xx)
    
            Put event into persistent state after opening. After closing
            the event's fd the event is persistent in the system and
            continues to run.
    
        perf_event ioctl calls
    
            PERF_EVENT_IOC_DETACH (Since Linux 3.xx)
    
                Any event that was opened with the perf_event_open()
                syscall may become a persistent event. This is done by
                detaching the event from the controlling process that
                holds the event's file descriptor. This ioctl can be used
                for doing this. After detaching it, the event is
                persistent in the system. An unique identifier for the
                persistent event is returned or an error otherwise. After
                closing the fd the event will continue to run. The
                following allows to connect to the event again:
    
                    pe.type = PERF_TYPE_PERSISTENT;
                    pe.config = <pevent_id>;
                    ...
                    fd = perf_event_open(...);
    
                The event must be reopened on the same cpu.
    
            PERF_EVENT_IOC_ATTACH (Since Linux 3.xx)
    
                Attach the event specified by the file descriptor to the
                current process. The event is no longer persistent in the
                system and will be removed after all users disconnected
                from the event. Thus, if there are no other users the
                event will be closed too after closing its file
                descriptor, the event then no longer exists.
    
    Cc: Vince Weaver <vincent.weaver@maine.edu>
    Signed-off-by: Robert Richter <robert.richter@linaro.org>
    Signed-off-by: Robert Richter <rric@kernel.org>

  reply	other threads:[~2013-08-27 12:17 UTC|newest]

Thread overview: 37+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-08-22 14:13 [PATCH v3 00/12] perf, persistent: Add persistent events Robert Richter
2013-08-22 14:13 ` [PATCH v3 01/12] perf, mmap: Factor out ring_buffer_detach_all() Robert Richter
2013-08-22 14:13 ` [PATCH v3 02/12] perf, mmap: Factor out try_get_event()/put_event() Robert Richter
2013-08-22 14:13 ` [PATCH v3 03/12] perf, mmap: Factor out perf_alloc/free_rb() Robert Richter
2013-08-22 14:13 ` [PATCH v3 04/12] perf, mmap: Factor out perf_get_fd() Robert Richter
2013-08-22 14:13 ` [PATCH v3 05/12] perf: Add persistent events Robert Richter
2013-08-22 14:13 ` [PATCH v3 06/12] mce, x86: Enable " Robert Richter
2013-08-22 14:13 ` [PATCH v3 07/12] perf, persistent: Implementing a persistent pmu Robert Richter
2013-08-22 14:13 ` [PATCH v3 08/12] perf, persistent: Exposing persistent events using sysfs Robert Richter
2013-08-22 18:00   ` Vince Weaver
2013-08-23  9:37     ` Robert Richter
2013-08-23 16:39       ` Vince Weaver
2013-08-27 11:16         ` Robert Richter
2013-08-22 14:13 ` [PATCH v3 09/12] perf, persistent: Use unique event ids Robert Richter
2013-08-22 14:13 ` [PATCH v3 10/12] perf, persistent: Implement reference counter for events Robert Richter
2013-08-22 14:13 ` [PATCH v3 11/12] perf, persistent: Dynamically resize list of sysfs entries Robert Richter
2013-08-22 14:13 ` [PATCH v3 12/12] [RFC] perf, persistent: ioctl functions to control persistency Robert Richter
2013-08-22 18:18   ` Vince Weaver
2013-08-23  9:11     ` Borislav Petkov
2013-08-23  9:45       ` Robert Richter
2013-08-23 10:44         ` Robert Richter
2013-08-23 11:34           ` Borislav Petkov
2013-08-23 17:07             ` Vince Weaver
2013-08-23 19:39               ` Borislav Petkov
2013-08-23 21:08                 ` Vince Weaver
2013-08-23 21:09                   ` Borislav Petkov
2013-08-27 11:54                   ` Robert Richter
2013-08-27 12:22                     ` Borislav Petkov
2013-08-27 12:41                       ` Robert Richter
2013-08-27 12:48                         ` Borislav Petkov
2013-08-23 10:07     ` Robert Richter
2013-08-27 12:17       ` Robert Richter [this message]
2013-08-24  9:38 ` [PATCH v3 00/12] perf, persistent: Add persistent events Borislav Petkov
2013-08-27 12:27   ` Robert Richter
2013-08-27 12:38     ` Borislav Petkov
2014-03-28 14:54       ` Jean Pihet
2014-03-29  9:42         ` Borislav Petkov

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=20130827121744.GE15884@rric.localhost \
    --to=rric@kernel.org \
    --cc=acme@infradead.org \
    --cc=bp@alien8.de \
    --cc=jolsa@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@kernel.org \
    --cc=peterz@infradead.org \
    --cc=vince@deater.net \
    --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