linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: "Ilya Lipovsky" <lipovsky@cs.bu.edu>
To: "'Andy Fleming'" <afleming@freescale.com>
Cc: linuxppc-embedded@ozlabs.org
Subject: RE: Question about oprofile
Date: Tue, 20 Mar 2007 19:07:29 -0400	[thread overview]
Message-ID: <004401c76b44$9b4b73f0$3a0d10ac@Radstone.Local> (raw)
In-Reply-To: <5C40F14F-81A8-4134-99A9-2B62BBD3AF05@freescale.com>

Has anyone considered doing something like lazy FPU/Altivec save/restore,
but only for PMC registers (depending on the PMM field in the MSR)... or is
it a lame idea :)?

-Ilya

-----Original Message-----
From: Andy Fleming [mailto:afleming@freescale.com] 
Sent: Tuesday, March 20, 2007 3:14 PM
To: Ilya Lipovsky
Cc: linuxppc-embedded@ozlabs.org
Subject: Re: Question about oprofile


On Mar 20, 2007, at 13:47, Ilya Lipovsky wrote:

> Hi,
>
>
>
> I am trying to understand how oprofile works, and so far I have a  
> question:
>
> When rfi'ing back into user context the PMM is cleared. However, if  
> PMM is cleared and then a context switch happens (say, to another  
> CPU-local thread) the counters keep getting incremented. Is that  
> right?
>
>
>
> If this is the case, then the PMC statistics account not just for  
> the current user thread, but also for other ones as well and thus  
> are not "pure."

oprofile does not support counting just on one thread.  The PMM bit  
is only used to make it so that the interrupt handler and setup code  
are not counted.  In order to count in one thread, you would need to  
modify the context switch code to allow the PMM bit to stay set on  
marked threads, and you would need to modify the oprofile code in  
arch/powerpc to only count when the mark bit is set (rather than when  
it is cleared).

Andy

  reply	other threads:[~2007-03-20 23:08 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-03-20 18:47 Question about oprofile Ilya Lipovsky
2007-03-20 19:13 ` Andy Fleming
2007-03-20 23:07   ` Ilya Lipovsky [this message]
2007-03-21 15:21 ` STACK & HEAP Charles Krinke

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='004401c76b44$9b4b73f0$3a0d10ac@Radstone.Local' \
    --to=lipovsky@cs.bu.edu \
    --cc=afleming@freescale.com \
    --cc=linuxppc-embedded@ozlabs.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).