public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Peter Zijlstra <peterz@infradead.org>
To: Ingo Molnar <mingo@elte.hu>
Cc: Paul Mundt <lethal@linux-sh.org>,
	Martin Schwidefsky <schwidefsky@de.ibm.com>,
	linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: register_timer_hook use in arch/sh/oprofile
Date: Fri, 26 Jun 2009 09:01:25 +0200	[thread overview]
Message-ID: <1245999685.31755.157.camel@twins> (raw)
In-Reply-To: <20090624132447.GD6224@elte.hu>

On Wed, 2009-06-24 at 15:24 +0200, Ingo Molnar wrote:
> 
> [ And long-term analysis ('perf stat' type of runs) dont need IRQs 
>   anyway - perfcounters reads outs the counts and summarizes them 
>   across the measured workload. ]

If the counter width is less than 64 bits we do need to have some
interrupt to read them from before they cycle so we can accumulate the
deltas into a proper u64.

But for proper 64 bit hardware counters there is indeed no need for
that.

  reply	other threads:[~2009-06-26  7:01 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-24 11:11 register_timer_hook use in arch/sh/oprofile Martin Schwidefsky
2009-06-24 11:29 ` Paul Mundt
2009-06-24 12:17   ` Ingo Molnar
2009-06-24 12:25     ` Paul Mundt
2009-06-24 12:37       ` Ingo Molnar
2009-06-24 12:40       ` Paul Mackerras
2009-06-24 12:47         ` Ingo Molnar
2009-06-24 12:28   ` Martin Schwidefsky
2009-06-24 12:34     ` Paul Mundt
2009-06-24 12:45       ` Ingo Molnar
2009-06-24 13:14         ` Paul Mundt
2009-06-24 13:24           ` Ingo Molnar
2009-06-26  7:01             ` Peter Zijlstra [this message]
2009-06-26  7:23               ` Ingo Molnar
2009-06-26  7:26                 ` Paul Mundt
2009-06-26  7:36                 ` Peter Zijlstra
2009-06-24 12:54       ` Martin Schwidefsky
2009-12-16  4:52         ` Paul Mundt
2009-12-16  7:21           ` Ingo Molnar

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=1245999685.31755.157.camel@twins \
    --to=peterz@infradead.org \
    --cc=lethal@linux-sh.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=schwidefsky@de.ibm.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox