linux-kernel - Re: [PATCH -tip] perf_counter: Add Generalized Hardware FPU support for AMD

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-Id: <1246454746.3072.10.camel@ht.satnam>
Date:	Wed, 01 Jul 2009 18:55:46 +0530
From:	Jaswinder Singh Rajput <jaswinder@...nel.org>
To:	Paul Mackerras <paulus@...ba.org>
Cc:	Ingo Molnar <mingo@...e.hu>, Thomas Gleixner <tglx@...utronix.de>,
	Peter Zijlstra <peterz@...radead.org>,
	x86 maintainers <x86@...nel.org>,
	LKML <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH -tip] perf_counter: Add Generalized Hardware FPU
 support for AMD

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

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/