| 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 PHC | |
|
Open Source and information security mailing list archives
| ||
|
Date: Tue, 16 Sep 2014 10:51:33 +0200 From: Stephane Eranian <eranian@...gle.com> To: Andi Kleen <ak@...ux.intel.com> Cc: LKML <linux-kernel@...r.kernel.org>, Peter Zijlstra <peterz@...radead.org>, "mingo@...e.hu" <mingo@...e.hu>, "Liang, Kan" <kan.liang@...el.com> Subject: Re: [PATCH] perf/x86/uncore: update support for client uncore IMC PMU On Mon, Sep 15, 2014 at 5:58 PM, Andi Kleen <ak@...ux.intel.com> wrote: > > On Mon, Sep 15, 2014 at 04:38:32PM +0200, Stephane Eranian wrote: > > > > This patch restructures the memory controller (IMC) uncore > > PMU support for client SNB/IVB/HSW processors. The main change > > is that it can now cope with more than one PCI device ID per > > processor model. There are many flavors of memory controllers > > for each processor. They have different PCI device ID, yet > > they behave the same w.r.t. the memory controller PMU that > > we are interested in. > > > > The patch now supports two distinct memory controllers for IVB > > processors: one for mobile, one for desktop. > > I haven't investigated yet, but on my Lenovo ULT Haswell laptop > the IMC PCI-ID doesn't exist, so the driver doesn't initialize. > Send me the PCI-ID for this memory controller and I will add it to V2 of the patch. Thanks. -- 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