From: Ingo Molnar <mingo@elte.hu>
To: Paul Mackerras <paulus@samba.org>
Cc: Jaswinder Singh Rajput <jaswinder@kernel.org>,
Thomas Gleixner <tglx@linutronix.de>,
Peter Zijlstra <peterz@infradead.org>,
x86 maintainers <x86@kernel.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH -tip] perf_counter: Add Generalized Hardware FPU support for AMD
Date: Wed, 1 Jul 2009 15:12:17 +0200 [thread overview]
Message-ID: <20090701131217.GA13524@elte.hu> (raw)
In-Reply-To: <19019.22396.776453.297335@cargo.ozlabs.ibm.com>
* Paul Mackerras <paulus@samba.org> wrote:
> Ingo Molnar writes:
>
> > 19583739 vec-adds ( 2.01x scaled)
> > 20856051 vec-muls ( 2.01x scaled)
> > 20856051 vec-divs ( 2.01x scaled)
> > 25100224054 vec-idle-cycles ( 1.99x scaled)
> > 12540131 vec-busy-cycles ( 1.99x scaled)
> > 42286702 vec-ops ( 2.01x scaled)
> >
> > Paulus: would this categorization fit PowerPC too?
>
> Conceptually that looks nice, but unfortunately we don't have
> events that correspond to that categorization on any PowerPC with
> vector hardware (VMX/Altivec). POWER6 seems to have the most
> vector events, and they are mostly divided up along the lines of
> simple / complex / permute / load / store operations, and whether
> they are integer or floating-point operations.
Here's what we have on x86:
20177177044 vec-adds (scaled from 66.63%)
34101687027 vec-muls (scaled from 66.64%)
3984060862 vec-divs (scaled from 66.71%)
26349684710 vec-idle-cycles (scaled from 66.65%)
9052001905 vec-stall-cycles (scaled from 66.66%)
76440734242 vec-ops (scaled from 66.71%)
Could at least the idle/busy/stall/total generic stats be filled in
on powerpc, with a reasonable enough approximation? Those
utilization metrics are the most important ones when one tries to
figure out how well utilized the vector units are.
Ingo
next prev parent reply other threads:[~2009-07-01 13:12 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-29 9:33 [PATCH -tip] perf_counter: Add Generalized Hardware FPU support for AMD Jaswinder Singh Rajput
2009-06-30 10:11 ` Ingo Molnar
2009-06-30 13:20 ` Jaswinder Singh Rajput
2009-06-30 14:56 ` Jaswinder Singh Rajput
2009-06-30 22:42 ` Ingo Molnar
2009-06-30 23:14 ` Alan Cox
2009-07-01 12:33 ` Paul Mackerras
2009-07-01 13:12 ` Ingo Molnar [this message]
2009-07-01 13:25 ` Jaswinder Singh Rajput
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=20090701131217.GA13524@elte.hu \
--to=mingo@elte.hu \
--cc=jaswinder@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=paulus@samba.org \
--cc=peterz@infradead.org \
--cc=tglx@linutronix.de \
--cc=x86@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