From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Arnd Bergmann <arnd.bergmann@de.ibm.com>
Cc: linuxppc-dev@ozlabs.org, Paul Mackerras <paulus@samba.org>
Subject: Re: Collecting hypervisor call stats
Date: Fri, 02 Jun 2006 07:57:23 +1000 [thread overview]
Message-ID: <1149199043.16202.2.camel@localhost.localdomain> (raw)
In-Reply-To: <200606012014.20467.arnd.bergmann@de.ibm.com>
On Thu, 2006-06-01 at 20:14 +0200, Arnd Bergmann wrote:
> On Thursday 01 June 2006 07:26, Benjamin Herrenschmidt wrote:
> >
> > > 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
>
> I guess for statistics, we should rather avoid that overhead (and
> document the fact that we did on purpose).
Well.. if we can at one point "detect" the totally bogus value (the
timestamp going massively backward) and fix it up there, ok. Might be an
option.
> How fast is mftb really? Would that be significant compared to the
> time spent in a fast hcall?
Not sure, I would expect a few dozens cycles at least though...
Ben.
next prev parent reply other threads:[~2006-06-01 21:57 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
2006-06-01 18:14 ` Arnd Bergmann
2006-06-01 21:57 ` Benjamin Herrenschmidt [this message]
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=1149199043.16202.2.camel@localhost.localdomain \
--to=benh@kernel.crashing.org \
--cc=arnd.bergmann@de.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).