public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Frederic Weisbecker <fweisbec@gmail.com>
To: Borislav Petkov <bp@amd64.org>
Cc: Peter Zijlstra <peterz@infradead.org>,
	Arnaldo Carvalho de Melo <acme@infradead.org>,
	Steven Rostedt <rostedt@goodmis.org>, Ingo Molnar <mingo@elte.hu>,
	LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 03/21] perf_events: Add a helper to search for an event in a context
Date: Thu, 1 Jul 2010 18:27:47 +0200	[thread overview]
Message-ID: <20100701162742.GI10616@nowhere> (raw)
In-Reply-To: <20100701162424.GI17823@aftab>

On Thu, Jul 01, 2010 at 06:24:24PM +0200, Borislav Petkov wrote:
> From: Frederic Weisbecker <fweisbec@gmail.com>
> Date: Thu, Jul 01, 2010 at 12:14:50PM -0400
> 
> Hi Frederic,
> 
> > On Thu, Jul 01, 2010 at 06:12:45PM +0200, Peter Zijlstra wrote:
> > > On Thu, 2010-07-01 at 18:11 +0200, Frederic Weisbecker wrote:
> > > > I suspect we need another syscall that can list all the persistent events
> > > > with a unique id and the attrs that follow.
> > > > 
> > > > So you get a unique id for all of them and you can create an fd on top
> > > > of this id by using a PERF_FLAG_REQUEST_PERSISTENT and this id put in
> > > > attr.config. 
> > > 
> > > Isn't that what filesystems were invented for?
> > 
> > 
> > The problem is when you create a persistent event, you lose the fd.
> > So you need to retrieve it somehow.
> 
> actually the idea is to decouple those from the fd alltogether and
> provide specific file_operations in debugfs and such, as Peter
> suggested. Which sounds much more sane to me especially since, at least
> in the MCE case, all the entities that register into that event need to
> see the same samples (and read the same buffers etc).



Sure the idea of putting that in fs is better.

Note the idea of a new syscall was quite close: it would have listed
unique ids of the persistent events, but not fds, you'd have yet to create
those fds on top of the ids.



> 
> And let's try not to read too much into those persistent events - it may
> just as well be that we need them only for MCEs and nothing else :)


Not really. It would be useful for boot tracing, amongst various other things
like flight recorder tracing, etc...


  reply	other threads:[~2010-07-01 16:27 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1277992175-19821-1-git-send-email-bp@amd64.org>
     [not found] ` <1277992175-19821-6-git-send-email-bp@amd64.org>
     [not found]   ` <20100701154737.GE8902@ghostprotocols.net>
     [not found]     ` <20100701161054.GF8902@ghostprotocols.net>
2010-07-01 16:17       ` [PATCH 05/21] perf: rewire generic library stuff, p1 Borislav Petkov
2010-07-01 17:14         ` Arnaldo Carvalho de Melo
2010-07-01 20:14           ` Borislav Petkov
2010-07-01 21:13             ` Arnaldo Carvalho de Melo
2010-07-01 21:37               ` Borislav Petkov
     [not found] ` <1277992175-19821-4-git-send-email-bp@amd64.org>
     [not found]   ` <1277992805.1917.142.camel@laptop>
     [not found]     ` <20100701141352.GA17823@aftab>
     [not found]       ` <20100701161133.GE10616@nowhere>
     [not found]         ` <1278000765.1917.220.camel@laptop>
     [not found]           ` <20100701161448.GF10616@nowhere>
2010-07-01 16:24             ` [PATCH 03/21] perf_events: Add a helper to search for an event in a context Borislav Petkov
2010-07-01 16:27               ` Frederic Weisbecker [this message]
2010-07-01 15:55 [RFC PATCH 00/21] RAS daemon prototype, v1 Borislav Petkov
2010-07-01 15:55 ` [PATCH 03/21] perf_events: Add a helper to search for an event in a context 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=20100701162742.GI10616@nowhere \
    --to=fweisbec@gmail.com \
    --cc=acme@infradead.org \
    --cc=bp@amd64.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=peterz@infradead.org \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox