From: Frederic Weisbecker <fweisbec@gmail.com>
To: Peter Zijlstra <peterz@infradead.org>
Cc: Kirill Smelkov <kirr@mns.spb.ru>,
linux-kernel@vger.kernel.org,
Arnaldo Carvalho de Melo <acme@redhat.com>,
Ingo Molnar <mingo@elte.hu>, Mike Galbraith <efault@gmx.de>,
Paul Mackerras <paulus@samba.org>,
Stephane Eranian <eranian@google.com>,
Tom Zanussi <tzanussi@gmail.com>
Subject: Re: Q: perf log mode?
Date: Wed, 12 Jan 2011 15:42:43 +0100 [thread overview]
Message-ID: <20110112144240.GA1755@nowhere> (raw)
In-Reply-To: <1294841288.19601.49.camel@laptop>
On Wed, Jan 12, 2011 at 03:08:08PM +0100, Peter Zijlstra wrote:
> On Wed, 2011-01-12 at 17:06 +0300, Kirill Smelkov wrote:
> > I'm trying to use perf together with e.g. kprobes as a tool to show what
> > is happening with my system in "live-log" mode. The problem is, for
> > seldom events, actual info output is largely delayed because perf reads
> > sample data in whole pages. Could something be done with it or am I'm
> > missing something? Here is detailed description:
>
> perf_event_attr = {
> .watermark = 0,
> .wakeup_events = 1,
> };
Which is perhaps something we want as a default when perf record -c 1
and the output is the pipe mode.
next prev parent reply other threads:[~2011-01-12 14:42 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-12 14:06 Q: perf log mode? Kirill Smelkov
2011-01-12 14:08 ` Peter Zijlstra
2011-01-12 14:42 ` Frederic Weisbecker [this message]
2011-01-12 14:53 ` Peter Zijlstra
2011-01-12 15:10 ` Frederic Weisbecker
2011-01-12 14:59 ` Kirill Smelkov
2011-01-12 15:02 ` Peter Zijlstra
2011-01-12 16:30 ` Arnaldo Carvalho de Melo
2011-01-13 8:26 ` Kirill Smelkov
2011-01-12 15:21 ` Arnaldo Carvalho de Melo
2011-01-12 16:31 ` Kirill Smelkov
2011-01-12 17:07 ` Arnaldo Carvalho de Melo
2011-01-14 7:25 ` [tip:perf/urgent] perf record: Add "nodelay" mode, disabled by default tip-bot for Kirill Smelkov
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=20110112144240.GA1755@nowhere \
--to=fweisbec@gmail.com \
--cc=acme@redhat.com \
--cc=efault@gmx.de \
--cc=eranian@google.com \
--cc=kirr@mns.spb.ru \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=paulus@samba.org \
--cc=peterz@infradead.org \
--cc=tzanussi@gmail.com \
/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.