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: <1273561210.30322.15.camel@minggr.sh.intel.com>
Date:	Tue, 11 May 2010 15:00:10 +0800
From:	Lin Ming <ming.m.lin@...el.com>
To:	Ingo Molnar <mingo@...e.hu>
Cc:	Peter Zijlstra <peterz@...radead.org>,
	Frederic Weisbecker <fweisbec@...il.com>,
	"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 14:51 +0800, Ingo Molnar wrote:
> * Lin Ming <ming.m.lin@...el.com> wrote:
> 
> > On Tue, 2010-05-11 at 14:38 +0800, Peter Zijlstra wrote:
> > > 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.
> > 
> > So the concept of "PMU" is really broadened here?
> > Not just only the performance monitoring hardware in CPU?
> 
> We _really_ dont want to call it a 'PMU' but 'events coming from an event 
> source'.
> 
> The reason is that a PMU is an existing term that is quite attached to a CPU - 
> while many hardware events come not from a PMU. Interrupts, error conditions, 
> hotplug events, etc. etc.
> 
> Furthermore, the name 'PMU' is even less correct for software events.
> 
> So lets stick with 'events' and with some container that originates them. 
> (event_source) Ok?

Yeah, understand.
"events coming from an event source" is a good clarification.

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

Powered by Openwall GNU/*/Linux Powered by OpenVZ