linux-kernel - Re: [PATCH] perf/x86/uncore: update support for client uncore IMC PMU

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

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

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

Date:	Mon, 15 Sep 2014 08:58:37 -0700
From:	Andi Kleen <ak@...ux.intel.com>
To:	Stephane Eranian <eranian@...gle.com>
Cc:	linux-kernel@...r.kernel.org, peterz@...radead.org, mingo@...e.hu,
	kan.liang@...el.com
Subject: Re: [PATCH] perf/x86/uncore: update support for client uncore IMC PMU

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.

So either it's the BIOS disabling it, or it's a different ID there
too.

BTW any reason you didn't enable the CBOX/ARB PMUs originally for HSW?
At least ARB events are useful for some things.

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