From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Mike Kravetz <kravetz@us.ibm.com>
Cc: linuxppc-dev@ozlabs.org, Paul Mackerras <paulus@samba.org>
Subject: Re: Collecting hypervisor call stats
Date: Thu, 01 Jun 2006 15:26:16 +1000 [thread overview]
Message-ID: <1149139576.28307.28.camel@localhost.localdomain> (raw)
In-Reply-To: <20060531225813.GC7909@w-mikek2.ibm.com>
On Wed, 2006-05-31 at 15:58 -0700, Mike Kravetz wrote:
> On Thu, Jun 01, 2006 at 08:40:50AM +1000, Paul Mackerras wrote:
> > I think that gathering those statistics would be useful. I suggest
> > you use a per-cpu array for them, to reduce the performance impact.
>
> Yes, that is a must do.
>
> We need to get a timestamp before and after the call. mftb should do
> the trick. Also, I'd prefer to have the code that stuffs the values
> into the array be C. So, the decision is to have the assembly code
> call out to the C routine -OR- create wrappers for the assembly routines.
> I much prefer C wrappers to touching the assembly.
Argh... yet another use of mftb for which I'll need a cell specific
workaround :(
Ben.
next prev parent reply other threads:[~2006-06-01 5:26 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-31 20:41 Collecting hypervisor call stats Mike Kravetz
2006-05-31 21:25 ` Geoff Levand
2006-05-31 22:40 ` Paul Mackerras
2006-05-31 22:58 ` Mike Kravetz
2006-06-01 5:26 ` Benjamin Herrenschmidt [this message]
2006-06-01 18:14 ` Arnd Bergmann
2006-06-01 21:57 ` Benjamin Herrenschmidt
2006-06-01 4:34 ` Jimi Xenidis
2006-06-01 5:12 ` Christopher Yeoh
2006-06-06 16:46 ` Mike Kravetz
2006-06-07 1:08 ` Christopher Yeoh
2006-06-07 22:57 ` Segher Boessenkool
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=1149139576.28307.28.camel@localhost.localdomain \
--to=benh@kernel.crashing.org \
--cc=kravetz@us.ibm.com \
--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).