From: "stephane eranian" <eranian@googlemail.com>
To: Ingo Molnar <mingo@elte.hu>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
linux-next@vger.kernel.org, paulus@samba.org,
Andrew Morton <akpm@linux-foundation.org>,
Thomas Gleixner <tglx@linutronix.de>,
"H. Peter Anvin" <hpa@zytor.com>
Subject: Re: linux-next: concerns over the perfmon3 tree
Date: Wed, 26 Nov 2008 14:25:08 +0100 [thread overview]
Message-ID: <7c86c4470811260525m5bd691fbi4e067cd4ff60ee11@mail.gmail.com> (raw)
In-Reply-To: <20081126104726.GA8580@elte.hu>
Ingo,
On Wed, Nov 26, 2008 at 11:47 AM, Ingo Molnar <mingo@elte.hu> wrote:
>
> * Stephen Rothwell <sfr@canb.auug.org.au> wrote:
>
>> Hi Stephane,
>>
>> Given the concerns expressed by Ingo, I have dropped the perfmon3
>> tree from linux-next until they have been addressed. Hopefully that
>> will not be loo long. Let us all know how we can help with this.
>
> Thanks, we'll try to finish the review ASAP (today+tomorrow) so that
> it can be added back in 1-2 days. And it's sensible to keep it in the
> separate perfmon3 tree as well (as long as it's not rebased) - that's
> a convenient initial structure for new features.
>
I think I am missing something about rebasing. Are you saying you want
the patches to stay with the same tree until it is reviewed thoroughly? So
far I have used Linus' v2.6.28-rcXX tree as it evolves at a pace I can follow.
Is that okay?
> ( and the powerpc bits would be nice as well, they seem to be missing
> from the current lineup - the more architectures keep hitting on
> that code, the better the end result. )
>
The fully featured perfmon3 code (available as a branch of my kernel.org tree)
has all the architectures we currently support. There is some overlap with the
patchset posted on LKML. I focused on x86 because this is the key architecture
with a lot of demands. It should not be very difficult to derive the
powerpc patchset
from the fully featured git branch, same goes for MIPS, and SPARC. IA-64 will be
a bit more challenging because they already have a much older version
of perfmon2.
Switching IA-64 to perfmon3 now, would cause lots of perfmon2 features
to disappear
(e.g., sampling, system-wide).
next prev parent reply other threads:[~2008-11-26 13:25 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-26 10:34 linux-next: concerns over the perfmon3 tree Stephen Rothwell
2008-11-26 10:47 ` Ingo Molnar
2008-11-26 13:25 ` stephane eranian [this message]
2008-11-26 13:27 ` 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=7c86c4470811260525m5bd691fbi4e067cd4ff60ee11@mail.gmail.com \
--to=eranian@googlemail.com \
--cc=akpm@linux-foundation.org \
--cc=eranian@gmail.com \
--cc=hpa@zytor.com \
--cc=linux-next@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=paulus@samba.org \
--cc=sfr@canb.auug.org.au \
--cc=tglx@linutronix.de \
/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