From: Ingo Molnar <mingo@kernel.org>
To: Peter Zijlstra <peterz@infradead.org>
Cc: Borislav Petkov <bp@amd64.org>,
Frederic Weisbecker <fweisbec@gmail.com>,
Ingo Molnar <mingo@elte.hu>, Steven Rostedt <rostedt@goodmis.org>,
LKML <linux-kernel@vger.kernel.org>,
Borislav Petkov <borislav.petkov@amd.com>
Subject: Re: [PATCH 1/2] perf: Add persistent event facilities
Date: Fri, 18 May 2012 13:59:57 +0200 [thread overview]
Message-ID: <20120518115957.GB19785@gmail.com> (raw)
In-Reply-To: <1337340263.573.31.camel@twins>
* Peter Zijlstra <peterz@infradead.org> wrote:
> On Fri, 2012-05-18 at 13:03 +0200, Borislav Petkov wrote:
> > > - you allow an arbitrary place in debugfs; this might make finding
> > > them 'interesting'. Should we put them all in the same place?
> >
> > My take on this is that we want to be able to make the same events we
> > have now, persistent. Basically not trace for the duration of a child
> > process but in a process-agnostic way, system-wide.
>
> This would argue against per-task persistent events..
Yeah, 'persistency' is something that's per CPU at minimum.
> Note the plural there, it might be very desirable to allow
> multiple events into a single persistent buffer.
very, very, very much so. One (per CPU) buffer, with many events
multiplexed into it.
Thanks,
Ingo
next prev parent reply other threads:[~2012-05-18 12:00 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-21 14:34 [RFC PATCH 0/2] perf: Add persistent event facilities Borislav Petkov
2012-03-21 14:34 ` [PATCH 1/2] " Borislav Petkov
2012-05-18 9:58 ` Peter Zijlstra
2012-05-18 10:01 ` Borislav Petkov
2012-05-18 10:00 ` Peter Zijlstra
2012-05-18 10:02 ` Peter Zijlstra
2012-05-18 10:09 ` Peter Zijlstra
2012-05-18 10:49 ` Borislav Petkov
2012-05-18 10:14 ` Peter Zijlstra
2012-05-18 11:03 ` Borislav Petkov
2012-05-18 11:24 ` Peter Zijlstra
2012-05-18 11:59 ` Ingo Molnar [this message]
2012-05-18 12:55 ` Borislav Petkov
2012-05-18 13:37 ` Peter Zijlstra
2012-05-18 14:09 ` Borislav Petkov
2012-05-18 14:14 ` Peter Zijlstra
2012-05-18 14:21 ` Borislav Petkov
2012-05-18 14:37 ` Peter Zijlstra
2012-05-18 15:24 ` Borislav Petkov
2012-05-31 17:33 ` Borislav Petkov
2012-03-21 14:34 ` [PATCH 2/2] x86, mce: Add persistent MCE event Borislav Petkov
2012-03-22 8:36 ` Srivatsa S. Bhat
2012-03-22 11:40 ` Borislav Petkov
2012-03-22 11:57 ` Srivatsa S. Bhat
2012-03-23 12:31 ` Ingo Molnar
2012-03-23 13:30 ` Borislav Petkov
2012-03-24 7:37 ` Ingo Molnar
2012-03-24 9:00 ` Borislav Petkov
2012-03-24 9:15 ` Ingo Molnar
2012-05-15 15:32 ` Borislav Petkov
2012-05-18 8:18 ` Ingo Molnar
2012-05-18 10:03 ` 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=20120518115957.GB19785@gmail.com \
--to=mingo@kernel.org \
--cc=borislav.petkov@amd.com \
--cc=bp@amd64.org \
--cc=fweisbec@gmail.com \
--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