linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: David Miller <davem@davemloft.net>
To: linuxppc-dev@ozlabs.org
Cc: paulus@samba.org
Subject: perf_counter vs. oprofile
Date: Wed, 21 Jan 2009 21:26:34 -0800 (PST)	[thread overview]
Message-ID: <20090121.212634.237965647.davem@davemloft.net> (raw)


Paul, I just noticed that right now if perf counter is enabled, the
oprofile module load will always fail because the powerpc perf counter
support unconditionally grabs the PMC hardware using
reserve_pmc_hardware() in an arch_initcall()

There really needs to be a way to segregate these multiple users of
the PMC device.  For example, if I'm not using the perf counter
APIs at all I should be able to use oprofile if I want to.

Anyways, just FYI...

             reply	other threads:[~2009-01-22  5:26 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-22  5:26 David Miller [this message]
2009-01-22  7:06 ` perf_counter vs. oprofile Paul Mackerras
2009-01-22  7:12   ` David Miller

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=20090121.212634.237965647.davem@davemloft.net \
    --to=davem@davemloft.net \
    --cc=linuxppc-dev@ozlabs.org \
    --cc=paulus@samba.org \
    /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;
as well as URLs for NNTP newsgroup(s).