From: Jaswinder Singh Rajput <jaswinder@kernel.org>
To: Paul Mackerras <paulus@samba.org>
Cc: Ingo Molnar <mingo@elte.hu>, 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, 01 Jul 2009 18:55:46 +0530 [thread overview]
Message-ID: <1246454746.3072.10.camel@ht.satnam> (raw)
In-Reply-To: <19019.22396.776453.297335@cargo.ozlabs.ibm.com>
On Wed, 2009-07-01 at 22:33 +1000, Paul Mackerras 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 are the vector-related events we have on POWER6:
>
> MRK_VMX0_LD_WRBACK Marked VMX0 load writeback valid
> MRK_VMX1_LD_WRBACK Marked VMX1 load writeback valid
> MRK_VMX_COMPLEX_ISSUED Marked VMX instruction issued to complex
> MRK_VMX_FLOAT_ISSUED Marked VMX instruction issued to float
> MRK_VMX_PERMUTE_ISSUED Marked VMX instruction issued to permute
> MRK_VMX_SIMPLE_ISSUED Marked VMX instruction issued to simple
> MRK_VMX_ST_ISSUED Marked VMX store issued
> VMX0_INST_ISSUED VMX0 instruction issued
> VMX0_LD_ISSUED VMX0 load issued
> VMX0_LD_WRBACK VMX0 load writeback valid
> VMX0_STALL VMX0 stall
> VMX1_INST_ISSUED VMX1 instruction issued
> VMX1_LD_ISSUED VMX1 load issued
> VMX1_LD_WRBACK VMX1 load writeback valid
> VMX1_STALL VMX1 stall
> VMX_COMPLEX_ISSUED VMX instruction issued to complex
> VMX_FLOAT_ISSUED VMX instruction issued to float
> VMX_FLOAT_MULTICYCLE VMX multi-cycle floating point instruction issued
> VMX_PERMUTE_ISSUED VMX instruction issued to permute
> VMX_RESULT_SAT_0_1 VMX valid result with sat bit is set (0->1)
> VMX_RESULT_SAT_1 VMX valid result with sat=1
> VMX_SIMPLE_ISSUED VMX instruction issued to simple
> VMX_ST_ISSUED VMX store issued
>
> I'm not sure what the exact distinction is between VMX0 and VMX1.
> I'll find out.
>
I am just guessing for powerpc, normally different units are for
different purpose like some do addition/multiplication and others do
division.
Like in Intel Corei7/Nehalem :
UOPS_EXECUTED.PORT0: Counts number of Uops executed
that were issued on port 0. Port 0
handles integer arithmetic, SIMD
and FP add Uops.
UOPS_EXECUTED.PORT1: Counts number of Uops executed
that were issued on port 1. Port 1
handles integer arithmetic, SIMD,
integer shift, FP multiply and FP
divide Uops.
Can you provide me the link of the Hardware manual so that I can check
it out.
Thanks,
--
JSR
prev parent reply other threads:[~2009-07-01 13:26 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
2009-07-01 13:25 ` Jaswinder Singh Rajput [this message]
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=1246454746.3072.10.camel@ht.satnam \
--to=jaswinder@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--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