public inbox for linux-ia64@vger.kernel.org
 help / color / mirror / Atom feed
From: David Mosberger <davidm@napali.hpl.hp.com>
To: linux-ia64@vger.kernel.org
Subject: RE: [Linux-ia64] [PATCH]  Support for alternative kernel profiler
Date: Thu, 10 Jan 2002 23:37:17 +0000	[thread overview]
Message-ID: <marc-linux-ia64-105590698805803@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-105590698805742@msgid-missing>

>>>>> On Thu, 10 Jan 2002 15:26:58 -0800, "Luck, Tony" <tony.luck@intel.com> said:

  Tony> We don't currently have any way for different software
  Tony> packages to share the performance counters, so it's very
  Tony> likely that there would be interactions with Stephane's PMU
  Tony> code (e.g. I rewrite cr.pmv to a new vector and re-write all
  Tony> of the pmc[] and pmd[] registers for my own purposes ... this
  Tony> will upset Stephane's code, similarly my code does not expect
  Tony> anyone else to touch any PMU registers, or fiddle with
  Tony> psr.pp/dcr.pp).

  Tony> It would probably be safest to turn off CONFIG_PERFMON in a
  Tony> kernel that is going to load an alternate profiler ... my
  Tony> profiler seems to cope ok provided nobody calls
  Tony> sys_perfmonctl().

This hardly seems like an ideal solution.  If you just want to keep
your patch for yourself, that's probably OK, but if it is to become
part of the kernel, we should look into a way for safely sharing the
PMU.  The first obvious way to try is to do the profiling you want on
top of perfmon.

	--david


      parent reply	other threads:[~2002-01-10 23:37 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-01-05  1:03 [Linux-ia64] [PATCH] Support for alternative kernel profiler in a module Luck, Tony
2002-01-09 21:37 ` [Linux-ia64] [PATCH] Support for alternative kernel profiler Luck, Tony
2002-01-10 19:25 ` David Mosberger
2002-01-10 19:27 ` David Mosberger
2002-01-10 23:26 ` Luck, Tony
2002-01-10 23:37 ` David Mosberger [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=marc-linux-ia64-105590698805803@msgid-missing \
    --to=davidm@napali.hpl.hp.com \
    --cc=linux-ia64@vger.kernel.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