All of lore.kernel.org
 help / color / mirror / Atom feed
From: Christian Ehrhardt <ehrhardt@linux.vnet.ibm.com>
To: kvm-ppc@vger.kernel.org
Subject: Re: [kvm-ppc-devel] Oprofile kvmppc - mini howto and restrictions
Date: Mon, 07 Apr 2008 07:49:20 +0000	[thread overview]
Message-ID: <47F9D200.5010506@linux.vnet.ibm.com> (raw)
In-Reply-To: <47F60A95.4030401@linux.vnet.ibm.com>

Josh Boyer wrote:
> On Fri, 2008-04-04 at 08:46 -0500, Hollis Blanchard wrote:
>> On Friday 04 April 2008 06:01:41 Christian Ehrhardt wrote:
>>> Note the bad thing, atm oprofile on ppc440 seems not to have hw perf
>>> counters available. Therefore it is covered with the fallback
>>> timer-interrupt. But this has drawbacks: =>from the oprfile info page:
>>> "In 2.6 kernels on CPUs without OProfile support for the hardware
>>> performance counters, the driver falls back to using the timer interrupt
>>> for profiling. Like the RTC mode in 2.4 kernels, this is not able to
>>> profile code that has interrupts disabled. Note that there are no
>>> configuration parameters for setting this, unlike the RTC and hardware
>>> performance counter setup."
>>>
>>> So oprofile works but without real cpu perf counters it will be nearly
>>> useless, because we have interrupts disabled in most code we want to
>>> profile. I need to look out for some beta support (or write my own) for
>>> ppc440 cpu perf counters to enable that for us :(
>> I don't see any performance counters in the 440 user manuals.
> 
> There aren't any that I'm aware of.  The only performance monitor I've
> seen on 440 chip is for the PLB, and I don't believe that is useful for
> your purposes.
> 
> josh

Yes after checking the spec's I agree that there just is no useful perf
monitor to use for us on the core we have.
The major question Hollis already asked me is how these timers behave
when we use it to profile the code that have interrupt enabled e.g. "would
the timers that actual expire while interrupts are disabled trigger on the
code line where we enable interrupts".
Atm I'm not sure about that, but I think it will behave like that. The
timer mechanism oprofile uses does not set up an own timer, it uses
register_timer_hook which is enabled with CONFIG_PROFILING. This is
basically called for each timer_interrupt. And I think as timer interrupts,
profiling will be postponed until MSR[EE] is enabled - comments welcome.

-- 

Grüsse / regards, 
Christian Ehrhardt
IBM Linux Technology Center, Open Virtualization

-------------------------------------------------------------------------
This SF.net email is sponsored by the 2008 JavaOne(SM) Conference 
Register now and save $200. Hurry, offer ends at 11:59 p.m., 
Monday, April 7! Use priority code J8TLD2. 
http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone
_______________________________________________
kvm-ppc-devel mailing list
kvm-ppc-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/kvm-ppc-devel

      parent reply	other threads:[~2008-04-07  7:49 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-04-04 11:01 [kvm-ppc-devel] Oprofile kvmppc - mini howto and restrictions (atm) Christian Ehrhardt
2008-04-04 13:46 ` [kvm-ppc-devel] Oprofile kvmppc - mini howto and restrictions Hollis Blanchard
2008-04-07  7:49 ` Christian Ehrhardt [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=47F9D200.5010506@linux.vnet.ibm.com \
    --to=ehrhardt@linux.vnet.ibm.com \
    --cc=kvm-ppc@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.