I think you could work on the PPC support based on the code in linux-next.
We could try to push it into 2.6.29. If that does not work out, it
won't be wasted
effort because we will push it for 2.6.30.
On Thu, Nov 6, 2008 at 7:51 PM, Corey J Ashford <cjashfor@...> wrote:
> This is excellent news and progress, Stephane!
> It wasn't clear to me from your more recent postings to LKML whether or
> not you were planning to do those architecture posts yourself, or to rely
> on the other contributors to do that.
> Obviously, we have the advantage of being able to test arch (Power in our
> case) patches first. Do you think I should create patches relative to
> linux-next to get Power arch support in before perfmon makes it upstream
> to 2.6.29?
> - Corey
> Corey Ashford
> Software Engineer
> IBM Linux Technology Center, Linux Toolchain
> Beaverton, OR
> "stephane eranian" <eranian@...> wrote on 11/06/2008 10:06:36
>> Hello everyone,
>> I wanted to update you on the status of the merge with upstream kernel.
>> As of yesterday, the perfmon3 minimal patchset as posted on LKML and
>> as available in the perfmon linux-next GIT has been included by Stephen
>> Rothwell into the official linux-next GIT tree.
>> What does that mean?
>> It means that, if all goes well, the first building block for perfmon3
> will be
>> merged upstream with 2.6.29, so about 3 months from now.
>> Just to remind people of what this patchset include:
>> - perfmon3 syscall API (5 syscalls)
>> - only support for counting
>> - only support for per-thread monitoring
>> - only support for AMD64 and Intel architectural PMUs (32 and
>> - no event set, no multiplexing
>> - no PMU description modules (all builtin)
>> Once this is in, it will be much easier to submit incremental changes.
>> I think we should add new architecture support first, then add
>> sampling, multiplexing.
>> As of now, if you are contributing code against this
> linux-next/perfmon3, then
>> it needs to be posted on LKML as well as the perfmon2 mailing list.
>> I will keep updating the perfmon2 tree. The perfmon3 branch will be used
>> all new developments from now on.
>> As for user level tools, pfmon 3.6 is already v3.0 ready if you
>> enable support.
>> Libpfm also has support in the v3 branch. I am planning on merging the
>> changes into the HEAD branch, that will minimize maintenance overhead.
>> We are getting there...
>> This SF.Net email is sponsored by the Moblin Your Move Developer's
>> Build the coolest Linux based applications with Moblin SDK & win great
>> Grand prize is a trip for two to an Open Source event anywhere in the
>> perfmon2-devel mailing list