public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@elte.hu>
To: Peter Zijlstra <peterz@infradead.org>
Cc: "Luck, Tony" <tony.luck@intel.com>,
	Paul Mackerras <paulus@samba.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] ia64 support for tools/perf/
Date: Wed, 18 Nov 2009 20:39:27 +0100	[thread overview]
Message-ID: <20091118193927.GA30470@elte.hu> (raw)
In-Reply-To: <1258563396.3918.698.camel@laptop>


* Peter Zijlstra <peterz@infradead.org> wrote:

> On Tue, 2009-11-17 at 09:25 -0800, Luck, Tony wrote:
> > > Btw., are you planning HAVE_PERF_EVENTS support for IA64? (It's nice 
> > > stuff, i can only recommend it! ;-)
> > 
> > My first goal is getting the s/w events hooked up and working.  I'm 
> > still wondering about how to get the h/w counters to co-exist with 
> > perfmon (which has been part of ia64 API for many years).
> 
> A first approach could be to make them mutually exclusive at runtime. 
> When there's a perf_event user, perfmon users get FAIL and vs.
> 
> This is basically the state for x86 perf_event vs oprofile atm.

Yep, this is probably the least intrusive approach. Mixing the 
implementations beyond trivial exclusion would probably be pain.

	Ingo

  reply	other threads:[~2009-11-18 19:39 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-11-17 17:05 [PATCH] ia64 support for tools/perf/ Luck, Tony
2009-11-17 17:18 ` [tip:perf/core] perf tools: Add " tip-bot for Luck, Tony
2009-11-17 17:21 ` [PATCH] " Ingo Molnar
2009-11-17 17:25   ` Luck, Tony
2009-11-18 16:56     ` Peter Zijlstra
2009-11-18 19:39       ` Ingo Molnar [this message]
2009-11-19  5:30 ` [tip:perf/core] perf tools: Add " tip-bot for Luck, Tony

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=20091118193927.GA30470@elte.hu \
    --to=mingo@elte.hu \
    --cc=linux-kernel@vger.kernel.org \
    --cc=paulus@samba.org \
    --cc=peterz@infradead.org \
    --cc=tony.luck@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