From: Christoph Hellwig <hch@infradead.org>
To: Andi Kleen <andi@firstfloor.org>
Cc: Stephane Eranian <eranian@hpl.hp.com>, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 13/22] 2.6.22-rc3 perfmon2 : common core functions
Date: Thu, 31 May 2007 19:29:45 +0100 [thread overview]
Message-ID: <20070531182945.GA9747@infradead.org> (raw)
In-Reply-To: <20070531172828.GC2538@one.firstfloor.org>
On Thu, May 31, 2007 at 07:28:28PM +0200, Andi Kleen wrote:
> I would prefer if oprofile would still work. It doesn't need to work
> in parallel but it should be possible to use it when perfmon
> is not active, but compiled in. That shouldn't be that difficult,
> should it?
I think the perform backend for oprofile is the right way to go.
I'd even go further and say we should merge the perfom backend with
oprofile as the only user first, because a) the current perfom user
interface is a complete mess and can't be merged as-is and b) that
ensures the oprofile backend works perfectly and we can kill some
existing code in exchange.
next prev parent reply other threads:[~2007-05-31 18:29 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-29 13:48 [PATCH 13/22] 2.6.22-rc3 perfmon2 : common core functions Stephane Eranian
2007-05-31 15:01 ` Andi Kleen
2007-05-31 17:16 ` Stephane Eranian
2007-05-31 17:28 ` Andi Kleen
2007-05-31 18:29 ` Christoph Hellwig [this message]
2007-05-31 18:43 ` Andi Kleen
2007-05-31 18:53 ` Christoph Hellwig
2007-05-31 19:02 ` Andi Kleen
2007-05-31 20:44 ` Stephane Eranian
2007-06-04 11:56 ` Stephane Eranian
[not found] ` <20070601101648.GD24898@frankl.hpl.hp.com>
[not found] ` <20070601105753.GE7217@one.firstfloor.org>
2007-06-12 12:32 ` problem with NMI MSR reserve routines Stephane Eranian
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=20070531182945.GA9747@infradead.org \
--to=hch@infradead.org \
--cc=andi@firstfloor.org \
--cc=eranian@hpl.hp.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox