From: Lee Revell <rlrevell@joe-job.com>
To: linux-kernel <linux-kernel@vger.kernel.org>
Cc: Ingo Molnar <mingo@elte.hu>
Subject: Re: 2.6.14-rt1: oprofile doesn't work anymore
Date: Sun, 06 Nov 2005 13:45:59 -0500 [thread overview]
Message-ID: <1131302759.13599.10.camel@mindpipe> (raw)
In-Reply-To: <1131060132.4770.2.camel@mindpipe>
On Thu, 2005-11-03 at 18:22 -0500, Lee Revell wrote:
> I just tested this with oprofile both built into the kernel and as a
> module, and with oprofile userspace tools 0.9.1 and from CVS. No
> change. I have verified that /dev/oprofile is mounted. It looks like
> the profiler never sees any samples.
>
> rlrevell@mindpipe:~$ cat /dev/oprofile/stats/cpu0/sample_received
> 0
>
> Could one of the ktimers changes have broken the timer interrupt based
> profiling?
I have verified that oprofile does work with 2.6.14. So the breakage is
unique to the -rt kernel.
Lee
next prev parent reply other threads:[~2005-11-06 21:40 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-03 21:39 2.6.14-rt1: oprofile doesn't work anymore Lee Revell
2005-11-03 23:22 ` Lee Revell
2005-11-06 18:45 ` Lee Revell [this message]
2006-05-31 3:27 ` Lee Revell
-- strict thread matches above, loose matches on Subject: below --
2006-07-18 13:49 Jonathan Walsh
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=1131302759.13599.10.camel@mindpipe \
--to=rlrevell@joe-job.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
/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