linux-kernel - Re: [RFC PATCH 2/3 v3] perf: Implement Nehalem uncore 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 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: <1291922670.6803.47.camel@twins>
Date:	Thu, 09 Dec 2010 20:24:30 +0100
From:	Peter Zijlstra <a.p.zijlstra@...llo.nl>
To:	Lin Ming <ming.m.lin@...el.com>
Cc:	Stephane Eranian <eranian@...gle.com>,
	Andi Kleen <andi@...stfloor.org>, Ingo Molnar <mingo@...e.hu>,
	Frederic Weisbecker <fweisbec@...il.com>,
	Arjan van de Ven <arjan@...radead.org>,
	lkml <linux-kernel@...r.kernel.org>
Subject: Re: [RFC PATCH 2/3 v3] perf: Implement Nehalem uncore pmu

On Thu, 2010-12-02 at 13:20 +0800, Lin Ming wrote:
> +++ b/arch/x86/kernel/cpu/perf_event.c

> @@ -1362,6 +1357,7 @@ int __init init_hw_perf_events(void)
>  
>         switch (boot_cpu_data.x86_vendor) {
>         case X86_VENDOR_INTEL:
> +               init_uncore_pmu();
>                 err = intel_pmu_init();
>                 break;
>         case X86_VENDOR_AMD: 

Since you're otherwise fully separated from the regular cpu driver,
could you also grow your own early_initcall() ?
--
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/