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]
Date:	Thu, 18 Jun 2015 16:25:17 +0200
From:	Imre Palik <imrep.amz@...il.com>
To:	Peter Zijlstra <peterz@...radead.org>
CC:	Paul Mackerras <paulus@...ba.org>, Ingo Molnar <mingo@...hat.com>,
	Arnaldo Carvalho de Melo <acme@...nel.org>,
	Thomas Gleixner <tglx@...utronix.de>,
	"H. Peter Anvin" <hpa@...or.com>, x86@...nel.org,
	linux-kernel@...r.kernel.org, "Palik, Imre" <imrep@...zon.de>,
	Anthony Liguori <aliguori@...zon.com>
Subject: Re: [PATCH v3] perf: honoring the architectural performance monitoring
 version

On 06/16/15 11:21, Peter Zijlstra wrote:
> On Mon, Jun 15, 2015 at 04:22:32PM +0200, Imre Palik wrote:
>> From: "Palik, Imre" <imrep@...zon.de>
>>
>> Architectural performance monitoring version 1 doesn't support fixed
>> counters.  Currently, even if a hypervisor advertises support for
>> architectural performance monitoring version 1, perf may still tries to use
>> the fixed counters, as the constraints are set up based on the CPU model.
>>
>> This patch ensures that perf honors the architectural performance
>> monitoring version returned by CPUID, and it only uses the fixed counters
>> for version two and above.
>>
>> Some of the ideas in this patch are coming from Peter Zijlstra.
> 
> What's the difference from -v2? I'm not really seeing it.
> 

I made the mistake of sending two different versions as v2.  v3 is the same
as the second v2.

I sent this to clear up possible confusion.  Sorry if it caused more of it.
--
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/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ