linux-kernel - Re: [PATCH] perf_event: fix Ming's Intel NHM/WSM/SNB uncore PMU patch

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, 1 Sep 2011 14:45:39 +0200
From:	Stephane Eranian <eranian@...gle.com>
To:	Lin Ming <ming.m.lin@...el.com>
Cc:	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	"peterz@...radead.org" <peterz@...radead.org>,
	"mingo@...e.hu" <mingo@...e.hu>,
	"andi@...stfloor.org" <andi@...stfloor.org>,
	"acme@...stprotocols.net" <acme@...stprotocols.net>
Subject: Re: [PATCH] perf_event: fix Ming's Intel NHM/WSM/SNB uncore PMU patch

On Thu, Sep 1, 2011 at 2:38 PM, Lin Ming <ming.m.lin@...el.com> wrote:
> On Wed, 2011-08-31 at 20:41 +0800, Stephane Eranian wrote:
>> The following patch sits on top of Lin Ming's patch
>> which adds support for Intel uncore PMU on NHM/WSM/SNB.
>> The patch series was posted on LKML in July 2011.
>>
>> The patches fixes:
>>   - nhm_uncore_pmu_enable_all() to also enabled the fixed uncore counters
>>   - uncore_pmu_add() to schedule for the actual max number of generic counters
>>   - fixed the NHM/WSM vs. SNB MSRs for the fixed counter, they are swapped
>>
>> The patch adds the following improvement:
>>   - add an event group validation function, to check if a group can ever be
>>     schedule. This way, the behavior is consistent with core PMU event groups.
>>
>> Signed-off-by: Stephane Eranian <eranian@...gle.com>
>
> Can I merge this patch into my series with these change logs and your
> signed-off-by?
>
Yes.

> Thanks,
> Lin Ming
>
>
--
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/