From: Peter Zijlstra <peterz@infradead.org>
To: Frederic Weisbecker <fweisbec@gmail.com>
Cc: Lin Ming <ming.m.lin@intel.com>, Ingo Molnar <mingo@elte.hu>,
"eranian@gmail.com" <eranian@gmail.com>,
"Gary.Mohr@Bull.com" <Gary.Mohr@bull.com>,
Corey Ashford <cjashfor@linux.vnet.ibm.com>,
"arjan@linux.intel.com" <arjan@linux.intel.com>,
"Zhang, Yanmin" <yanmin_zhang@linux.intel.com>,
Paul Mackerras <paulus@samba.org>,
"David S. Miller" <davem@davemloft.net>,
Russell King <rmk+kernel@arm.linux.org.uk>,
Paul Mundt <lethal@linux-sh.org>,
lkml <linux-kernel@vger.kernel.org>
Subject: Re: [RFC][PATCH 2/9] perf: core, remove hw_perf_event_init
Date: Tue, 11 May 2010 08:38:55 +0200 [thread overview]
Message-ID: <1273559935.5605.3418.camel@twins> (raw)
In-Reply-To: <20100510230911.GB5895@nowhere>
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.
next prev parent reply other threads:[~2010-05-11 6:39 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-10 9:26 [RFC][PATCH 2/9] perf: core, remove hw_perf_event_init Lin Ming
2010-05-10 9:40 ` Peter Zijlstra
2010-05-10 10:17 ` Lin Ming
2010-05-10 10:19 ` Peter Zijlstra
2010-05-10 10:22 ` Lin Ming
2010-05-10 12:27 ` Frederic Weisbecker
2010-05-10 12:54 ` Peter Zijlstra
2010-05-10 23:09 ` Frederic Weisbecker
2010-05-11 6:38 ` Peter Zijlstra [this message]
2010-05-11 6:44 ` Lin Ming
2010-05-11 6:51 ` Ingo Molnar
2010-05-11 7:00 ` Lin Ming
2010-05-11 9:18 ` Peter Zijlstra
2010-05-11 6:50 ` Frederic Weisbecker
2010-05-10 9:42 ` Peter Zijlstra
2010-05-10 10:15 ` Lin Ming
2010-05-10 12:24 ` Frederic Weisbecker
2010-05-12 2:11 ` Lin Ming
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1273559935.5605.3418.camel@twins \
--to=peterz@infradead.org \
--cc=Gary.Mohr@bull.com \
--cc=arjan@linux.intel.com \
--cc=cjashfor@linux.vnet.ibm.com \
--cc=davem@davemloft.net \
--cc=eranian@gmail.com \
--cc=fweisbec@gmail.com \
--cc=lethal@linux-sh.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ming.m.lin@intel.com \
--cc=mingo@elte.hu \
--cc=paulus@samba.org \
--cc=rmk+kernel@arm.linux.org.uk \
--cc=yanmin_zhang@linux.intel.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox