mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Lin Ming <ming.m.lin@intel.com>
To: Peter Zijlstra <peterz@infradead.org>
Cc: "linux-kernel@vger.kernel.org" <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" <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 17:33:54 +0800	[thread overview]
Message-ID: <1281951234.6555.65.camel@minggr.sh.intel.com> (raw)
In-Reply-To: <1281949925.1926.1081.camel@laptop>

On Mon, 2010-08-16 at 17:12 +0800, Peter Zijlstra wrote:
> On Mon, 2010-08-16 at 16:39 +0800, Lin Ming wrote:
> > > After that and some patches adding per pmu contexts adding multiple
> > > hardware pmus should be simple.
> > 
> > I didn't see the per pmu contexts patches, are you still working on
> > them?
> > 
> Yes, although 3 weeks of holidays and a week of LinuxCon didn't help to
> finish that work ;-)
> 
> I hope to be back to that soon ;-)

Really thanks for your work, that makes uncore support much easier.

> 
> > > 
> > > uncore should not share any code with the regular pmu, since they're
> > > mostly unrelated.
> > 
> > But should they share code like collect_events, schedule_events,
> > x86_perf_event_set_period(with some modification) etc...?
> > 
> Maybe, I'd have to look at the uncore stuff again, I can't remember if
> it has much in the way of event scheduling constraints and if the
> counter programming is close enough to the regular pmu to make it worth
> sharing code over.

I looked at the Nehalem uncore stuff and it does not have event
constraints. Each event can be monitored with any uncore counter.

The counter programming is close to regular pmu. It has
PERFEVTSELx/GLOBAL_STATUS/GLOBAL_OVF_CTRL/FIXED_CTR_CTRL like regular
pmu.



      reply	other threads:[~2010-08-16  9:34 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
2010-08-16  8:39   ` Lin Ming
2010-08-16  9:12     ` Peter Zijlstra
2010-08-16  9:33       ` Lin Ming [this message]

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=1281951234.6555.65.camel@minggr.sh.intel.com \
    --to=ming.m.lin@intel.com \
    --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=mingo@elte.hu \
    --cc=peterz@infradead.org \
    --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