From: Andi Kleen <andi@firstfloor.org>
To: Christoph Hellwig <hch@infradead.org>,
Andi Kleen <andi@firstfloor.org>,
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 20:43:14 +0200 [thread overview]
Message-ID: <20070531184313.GA7217@one.firstfloor.org> (raw)
In-Reply-To: <20070531182945.GA9747@infradead.org>
> 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
Can you suggest concrete criticism/improvements/alternative proposals to
Stephane then?
> 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.
Hmm, but at least for oprofile like functionality oprofile code seems
much simpler. And it's not really bad code. I assume the user interface
would change too. I think it's better to let them coexist for some time.
-Andi
next prev parent reply other threads:[~2007-05-31 18:43 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
2007-05-31 18:43 ` Andi Kleen [this message]
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=20070531184313.GA7217@one.firstfloor.org \
--to=andi@firstfloor.org \
--cc=eranian@hpl.hp.com \
--cc=hch@infradead.org \
--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.