From: Mike Kravetz <kravetz@us.ibm.com>
To: Paul Mackerras <paulus@samba.org>
Cc: linuxppc-dev@ozlabs.org
Subject: Re: [PATCH 0/3] powerpc: Instrument Hypervisor Calls
Date: Tue, 18 Jul 2006 20:36:18 -0700 [thread overview]
Message-ID: <20060719033618.GA3944@monkey.ibm.com> (raw)
In-Reply-To: <17597.19430.983453.919592@cargo.ozlabs.ibm.com>
On Wed, Jul 19, 2006 at 07:00:22AM +1000, Paul Mackerras wrote:
> Mike Kravetz writes:
> > A small update from the last version. By popular demand, both
> > wall time (mftb) and cpu cycles(PURR) are collected for each call.
> > It is interesting to see these two values side by side in the
> > output files.
>
> Did you see the patch from Anton that I posted a week or so ago, which
> reduces the number of plpar_hcall_* functions? I'd rather the
> instrumentation stuff was based on that.
Agreed. I missed the patch from last week, but saw the one from Anton
that was posted today. Future instrumentation patches will assume this
change.
> My other comment is this: wouldn't it actually turn out simpler if we
> read the timebase (and PURR, if we really want to do that too) in the
> assembly code that implements plpar_hcall_*?
I'll give that a try. My assembly skills are a bit rusty, so it may
take a little longer to produce something.
--
Mike
next prev parent reply other threads:[~2006-07-19 3:36 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-18 20:47 [PATCH 0/3] powerpc: Instrument Hypervisor Calls Mike Kravetz
2006-07-18 20:48 ` [PATCH 1/3] powerpc: Instrument Hypervisor Calls: merge headers Mike Kravetz
2006-07-18 20:49 ` [PATCH 2/3] powerpc: Instrument Hypervisor Calls: add wrappers Mike Kravetz
2006-07-18 22:34 ` Olof Johansson
2006-07-18 23:18 ` Mike Kravetz
2006-07-19 3:33 ` Olof Johansson
2006-07-19 3:50 ` Mike Kravetz
2006-07-18 20:50 ` [PATCH 3/3] powerpc: Instrument Hypervisor Calls: add debugfs files Mike Kravetz
2006-07-18 21:00 ` [PATCH 0/3] powerpc: Instrument Hypervisor Calls Paul Mackerras
2006-07-19 3:36 ` Mike Kravetz [this message]
2006-07-19 22:11 ` Mike Kravetz
2006-07-18 21:29 ` Mike Kravetz
2006-07-18 22:38 ` Olof Johansson
-- strict thread matches above, loose matches on Subject: below --
2006-07-21 6:38 Mike Kravetz
2006-07-14 23:37 Mike Kravetz
2006-07-15 0:00 ` Arnd Bergmann
2006-07-15 0:06 ` Mike Kravetz
2006-07-15 15:30 ` Anton Blanchard
2006-07-15 16:42 ` Arnd Bergmann
2006-07-15 22:07 ` Anton Blanchard
2006-07-16 23:02 ` Luke Browning
2006-07-17 2:02 ` Luke Browning
2006-07-16 3:53 ` Olof Johansson
2006-07-16 22:53 ` Luke Browning
2006-07-16 23:09 ` Olof Johansson
2006-06-22 22:56 Mike Kravetz
2006-06-23 0:28 ` Segher Boessenkool
2006-07-10 20:35 ` Mike Kravetz
2006-07-10 20:49 ` Arnd Bergmann
2006-07-12 18:05 ` Mike Kravetz
2006-06-14 3:47 Mike Kravetz
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=20060719033618.GA3944@monkey.ibm.com \
--to=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).