From: Andrew Morton <akpm@linux-foundation.org>
To: Andi Kleen <ak@suse.de>
Cc: Christoph Lameter <clameter@sgi.com>,
linux-kernel@vger.kernel.org,
Chuck Ebbert <76306.1226@compuserve.com>
Subject: Re: Remove constructor from buffer_head
Date: Fri, 4 May 2007 16:45:29 -0700 [thread overview]
Message-ID: <20070504164529.f64a2985.akpm@linux-foundation.org> (raw)
In-Reply-To: <200705050122.05275.ak@suse.de>
On Sat, 5 May 2007 01:22:05 +0200
Andi Kleen <ak@suse.de> wrote:
> > 2.6.21:
> >
> > akpm2:/home/akpm# opreport -l /boot/vmlinux-$(uname -r) | head -50
> > opreport error: No sample file found: try running opcontrol --dump
> > or specify a session containing sample files
>
> For me it works on a slightly post 2.6.21 kernel with suse oprofile-0.9.2-21
>
> Did you try opcontrol --dump?
Yes, tried various things. There's just nothing turning up in /var/lib/oprofile.
Chuck appears to be claiming that 2.6.21 oprofile is known to be broken,
but I never heard anything about that.
next prev parent reply other threads:[~2007-05-04 23:46 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-04 3:08 Remove constructor from buffer_head Christoph Lameter
2007-05-04 3:21 ` Andrew Morton
2007-05-04 3:34 ` Christoph Lameter
2007-05-04 4:37 ` Andrew Morton
2007-05-04 4:34 ` Christoph Lameter
2007-05-04 6:35 ` William Lee Irwin III
2007-05-04 16:05 ` Christoph Lameter
2007-05-04 20:42 ` Andrew Morton
2007-05-04 21:33 ` Andrew Morton
2007-05-04 23:22 ` Andi Kleen
2007-05-04 23:45 ` Andrew Morton [this message]
2007-05-05 9:31 ` Andi Kleen
2007-05-13 20:38 ` oprofile broken in 2.6.21 SMP (was Re: Remove constructor from buffer_head) Benjamin LaHaise
2007-05-15 3:12 ` Andrew Morton
2007-05-04 21:42 ` Remove constructor from buffer_head Christoph Lameter
2007-05-04 21:47 ` Andrew Morton
2007-05-04 21:52 ` Chuck Ebbert
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=20070504164529.f64a2985.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=76306.1226@compuserve.com \
--cc=ak@suse.de \
--cc=clameter@sgi.com \
--cc=linux-kernel@vger.kernel.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 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.