From: Ingo Molnar <mingo@elte.hu>
To: Paul Mackerras <paulus@samba.org>
Cc: linux-kernel@vger.kernel.org, Thomas Gleixner <tglx@linutronix.de>
Subject: Re: [PATCH 0/9] Performance counters for POWER
Date: Fri, 9 Jan 2009 14:47:27 +0100 [thread overview]
Message-ID: <20090109134727.GA902@elte.hu> (raw)
In-Reply-To: <18791.10652.298501.863657@cargo.ozlabs.ibm.com>
* Paul Mackerras <paulus@samba.org> wrote:
> The following series of patches extends Ingo and Thomas's performance
> counter framework to add support for 64-bit POWER processors. Currently
> I have the PPC970 family and POWER6 done.
Cool stuff!
> The approach I have taken is to do the constraint checking and the
> search through the space of alternative event codes as each group of
> counters is added at the time a task is scheduled in. That means we are
> potentially doing the search several times in a row, with interrupts
> disabled. I think it will be OK since there are only a few events that
> have alternatives (and not many of them), and the constraint checking is
> fast since it is just simple integer operations. However, one of the
> things I plan to do is to instrument that code to find out how long it
> takes in the worst case. (If it takes too long then I will need some
> major changes to the generic code.)
Sounds like a very good approach to me. I think the core code wants to be
optimistic towards the non-presence of scheduling constraints. So as
hardware improves and evolves [which we all hope it does], so will
hopefully the constraint related overhead become smaller.
> This series is also available via git at:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/paulus/perfcounters.git
>
> in the master branch.
Great work Paul!
Do timec.c and kerneltop.c work fine for you by any chance? If yes, could
you send us some sample output that you get with them on your power
testbox(es)?
Also, would this be the right moment for me to pull from you?
Your modifications to kernel/perf_counter.c are all fixes and sensible
extensions, and i expect the x86 side should continue to work just fine,
so i'd like to pull this ASAP :-)
Ingo
next prev parent reply other threads:[~2009-01-09 13:47 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-09 10:40 [PATCH 0/9] Performance counters for POWER Paul Mackerras
2009-01-09 13:28 ` Peter Zijlstra
2009-01-10 0:30 ` Paul Mackerras
2009-01-09 13:47 ` Ingo Molnar [this message]
2009-01-09 23:38 ` Paul Mackerras
2009-01-11 1:48 ` Ingo Molnar
2009-01-10 5:51 ` Paul Mackerras
2009-01-11 1:44 ` Ingo Molnar
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=20090109134727.GA902@elte.hu \
--to=mingo@elte.hu \
--cc=linux-kernel@vger.kernel.org \
--cc=paulus@samba.org \
--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