public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Tim Blechmann <tim@klingt.org>
To: Peter Zijlstra <peterz@infradead.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: perf: counter and event question
Date: Mon, 28 Dec 2009 14:09:49 +0100	[thread overview]
Message-ID: <4B38AE1D.8060703@klingt.org> (raw)
In-Reply-To: <1262005413.7135.98.camel@laptop>

[-- Attachment #1: Type: text/plain, Size: 977 bytes --]

>>>> like it is impossible to sample instructions with a period of 1? 
>>>
>>> Pretty much, imagine the cpu getting a trap every cycle.
>>
>> is this a hardware restriction? a slowdown is acceptable for me, as long
>> as i am able to collect a huge number of samples accurately ...
> 
> Large number of samples and sample interval are only related through the
> runtime of your application.
> 
> Use a sensible period (~10k ins) and run a 'little' longer.

well, for my application, i am not interested in statistical data, but
in the order of the events ...
(i am not doing profiling, but trying to gather a sequence of
machine-structured data for an artistic project)

tim

-- 
tim@klingt.org
http://tim.klingt.org

It is better to make a piece of music than to perform one, better to
perform one than to listen to one, better to listen to one than to
misuse it as a means of distraction, entertainment, or acquisition of
'culture'.
  John Cage


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 197 bytes --]

  reply	other threads:[~2009-12-28 13:10 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-12-28 11:16 perf: counter and event question Tim Blechmann
2009-12-28 11:26 ` Peter Zijlstra
2009-12-28 12:39   ` Tim Blechmann
2009-12-28 13:03     ` Peter Zijlstra
2009-12-28 13:09       ` Tim Blechmann [this message]
2009-12-28 14:02         ` Peter Zijlstra

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=4B38AE1D.8060703@klingt.org \
    --to=tim@klingt.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=peterz@infradead.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