| 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
| ||
|
Date: Tue, 11 May 2010 08:38:55 +0200 From: Peter Zijlstra <peterz@...radead.org> To: Frederic Weisbecker <fweisbec@...il.com> Cc: Lin Ming <ming.m.lin@...el.com>, Ingo Molnar <mingo@...e.hu>, "eranian@...il.com" <eranian@...il.com>, "Gary.Mohr@...l.com" <Gary.Mohr@...l.com>, Corey Ashford <cjashfor@...ux.vnet.ibm.com>, "arjan@...ux.intel.com" <arjan@...ux.intel.com>, "Zhang, Yanmin" <yanmin_zhang@...ux.intel.com>, Paul Mackerras <paulus@...ba.org>, "David S. Miller" <davem@...emloft.net>, Russell King <rmk+kernel@....linux.org.uk>, Paul Mundt <lethal@...ux-sh.org>, lkml <linux-kernel@...r.kernel.org> Subject: Re: [RFC][PATCH 2/9] perf: core, remove hw_perf_event_init On Tue, 2010-05-11 at 01:09 +0200, Frederic Weisbecker wrote: > Which module do you have in mind that could register a pmu? > And I don't understand the problem with pci-hotplug. Well, the DRM drivers for one, but basically the trend is for every aspect of the machine to include PMUs of some form, this includes bus bridges and fancy devices. The point about PCI-hotplug is that GPUs live on the PCI bus and once they start adding their PMU drivers we need to be able to unplug them. Same for when the PCI bridge devices start featuring PMU implementations. -- 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