linux-kernel - Re: [PATCH 3/3] perf_counter: powerpc: supply more precise information on counter overflow events

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] [thread-next>] [day] [month] [year] [list]

Message-Id: <1242283892.26820.43.camel@twins>
Date:	Thu, 14 May 2009 08:51:32 +0200
From:	Peter Zijlstra <a.p.zijlstra@...llo.nl>
To:	Paul Mackerras <paulus@...ba.org>
Cc:	Ingo Molnar <mingo@...e.hu>, linux-kernel@...r.kernel.org,
	Corey Ashford <cjashfor@...ux.vnet.ibm.com>,
	Thomas Gleixner <tglx@...utronix.de>
Subject: Re: [PATCH 3/3] perf_counter: powerpc: supply more precise
 information on counter overflow events

On Thu, 2009-05-14 at 13:31 +1000, Paul Mackerras wrote:
> This uses values from the MMCRA, SIAR and SDAR registers on powerpc to
> supply more precise information for overflow events, including a data
> address when PERF_RECORD_ADDR is specified.
> 
> Since POWER6 uses different bit positions in MMCRA from earlier processors,
> this converts the struct power_pmu limited_pmc5_6 field, which only had
> 0/1 values, into a flags field and defines bit values for its previous
> use (PPMU_LIMITED_PMC5_6) and a new flag (PPMU_ALT_SIPR) to indicate
> that the processor uses the POWER6 bit positions rather than the earlier
> positions.  It also adds definitions in reg.h for the new and old positions
> of the bit that indicates that the SIAR and SDAR values come from the
> same instruction.
> 
> For the data address, the SDAR value is supplied if we are not doing
> instruction sampling.  In that case there is no guarantee that the address
> given in the PERF_RECORD_ADDR subrecord will correspond to the instruction
> whose address is given in the PERF_RECORD_IP subrecord.
> 
> If instruction sampling is enabled (e.g. because this counter is counting
> a marked instruction event), then we only supply the SDAR value for the
> PERF_RECORD_ADDR subrecord if it corresponds to the instruction whose
> address is in the PERF_RECORD_IP subrecord.  Otherwise we supply 0.

Very cool hardware feature! :-)

--
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/