All of lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Zijlstra <peterz@infradead.org>
To: Borislav Petkov <bp@alien8.de>
Cc: Ingo Molnar <mingo@elte.hu>,
	Frederic Weisbecker <fweisbec@gmail.com>,
	Steven Rostedt <rostedt@goodmis.org>,
	Arnaldo Carvalho de Melo <acme@redhat.com>,
	Lin Ming <ming.m.lin@intel.com>,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/2] perf: Add persistent events
Date: Sun, 23 May 2010 20:15:13 +0200	[thread overview]
Message-ID: <1274638513.1674.1727.camel@laptop> (raw)
In-Reply-To: <1274554806-28216-2-git-send-email-bp@alien8.de>

On Sat, 2010-05-22 at 21:00 +0200, Borislav Petkov wrote:
> Register and enable events marked as persistent right after perf events
> has initialized.
> 
> Not-yet-signed-off-by: Borislav Petkov <bp@alien8.de>

Nah, this is totally wrong.

A persistent event would simply be a regular event, but created by the
kernel and not tied to a file-desc's lifetime.




  parent reply	other threads:[~2010-05-23 18:15 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-05-22 19:00 [RFC PATCH 0/2] perf: persistent events prototype Borislav Petkov
2010-05-22 19:00 ` [PATCH 2/2] x86, mce: Make MCE tracepoint persistent event Borislav Petkov
     [not found] ` <1274554806-28216-2-git-send-email-bp@alien8.de>
2010-05-23 18:15   ` Peter Zijlstra [this message]
2010-05-23 18:33     ` [PATCH 1/2] perf: Add persistent events Borislav Petkov
2010-05-23 18:40       ` Peter Zijlstra
2010-05-23 18:54         ` Borislav Petkov
2010-05-23 19:23           ` Peter Zijlstra
2010-05-25  7:32             ` Borislav Petkov
2010-05-25 14:59               ` Peter Zijlstra
2010-05-28 14:33                 ` Ingo Molnar
2010-05-28 15:17                   ` Peter Zijlstra
2010-05-28 15:57                     ` Borislav Petkov
2010-05-28 18:07                       ` Peter Zijlstra
2010-06-03 13:43                         ` Borislav Petkov
2010-06-03 17:32                           ` Arnaldo Carvalho de Melo
2010-06-03 21:39                             ` Borislav Petkov
2010-06-14 19:25                             ` Borislav Petkov
2010-06-14 21:01                               ` Arnaldo Carvalho de Melo
2010-06-14 21:24                                 ` Borislav Petkov
2010-06-15  1:02                                   ` Arnaldo Carvalho de Melo
2010-06-15 10:22                                     ` Borislav Petkov
2010-06-15 13:22                                       ` Arnaldo Carvalho de Melo
2010-06-17 13:43                                     ` Borislav Petkov
2010-06-17 14:25                                       ` Arnaldo Carvalho de Melo
2010-06-17 15:27                                         ` Borislav Petkov
2010-06-17 16:19                                       ` Steven Rostedt
2010-06-17 17:31                                         ` Borislav Petkov
2010-05-23 20:36 ` [RFC PATCH 0/2] perf: persistent events prototype Steven Rostedt
  -- strict thread matches above, loose matches on Subject: below --
2010-05-22 19:04 Borislav Petkov
2010-05-22 19:04 ` [PATCH 1/2] perf: Add persistent events Borislav Petkov
2010-05-22 19:14   ` Borislav Petkov
2010-05-25  3:11   ` Steven Rostedt

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=1274638513.1674.1727.camel@laptop \
    --to=peterz@infradead.org \
    --cc=acme@redhat.com \
    --cc=bp@alien8.de \
    --cc=fweisbec@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=ming.m.lin@intel.com \
    --cc=mingo@elte.hu \
    --cc=rostedt@goodmis.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.