From: Peter Zijlstra <peterz@infradead.org>
To: Lin Ming <ming.m.lin@intel.com>
Cc: linux-kernel@vger.kernel.org, Ingo Molnar <mingo@elte.hu>,
Robert Richter <robert.richter@amd.com>,
Frederic Weisbecker <fweisbec@gmail.com>,
Don Zickus <dzickus@redhat.com>,
Cyrill Gorcunov <gorcunov@gmail.com>,
arjan@linux.intel.com, "Fu, Michael" <michael.fu@intel.com>
Subject: Re: perf, how to support multiple x86 hw pmus?
Date: Mon, 16 Aug 2010 10:25:13 +0200 [thread overview]
Message-ID: <1281947113.1926.1004.camel@laptop> (raw)
In-Reply-To: <1281946154.6555.46.camel@minggr.sh.intel.com>
On Mon, 2010-08-16 at 16:09 +0800, Lin Ming wrote:
> Hi, all
>
> Here multiple x86 hw pmus means, for example, Intel "core" and "uncore"
> pmu. "core" pmu is to collect per cpu data, cpu-cycles, branch-misses,
> etc. "uncore" pmu is to collect per package data, L3 cache, Intel QPI,
> integrated memory controller, etc.
>
> I am going to add Intel uncore pmu support to perf. To reduce code
> duplicate, "uncore" pmu should reuse most of the "core" pmu code. But
> currently, the x86 core pmu code(arch/x86/kernel/cpu/perf_event.c) only
> supports one pmu, with a definition as below.
>
> static struct x86_pmu x86_pmu __read_mostly;
>
> Many functions use above global definition "x86_pmu". It seems to me
> that we need to re-structure x86 pmu code to support multiple hw pmus.
>
> Any idea?
Yes, see my patch series http://lkml.org/lkml/2010/7/9/96 reworking the
pmu interface.
After that and some patches adding per pmu contexts adding multiple
hardware pmus should be simple.
uncore should not share any code with the regular pmu, since they're
mostly unrelated.
next prev parent reply other threads:[~2010-08-16 8:25 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-16 8:09 Lin Ming
2010-08-16 8:25 ` Peter Zijlstra [this message]
2010-08-16 8:39 ` Lin Ming
2010-08-16 9:12 ` Peter Zijlstra
2010-08-16 9:33 ` 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=1281947113.1926.1004.camel@laptop \
--to=peterz@infradead.org \
--cc=arjan@linux.intel.com \
--cc=dzickus@redhat.com \
--cc=fweisbec@gmail.com \
--cc=gorcunov@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=michael.fu@intel.com \
--cc=ming.m.lin@intel.com \
--cc=mingo@elte.hu \
--cc=robert.richter@amd.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
Powered by JetHome