From: Mike Kravetz <kravetz@us.ibm.com>
To: Geoff Levand <geoffrey.levand@am.sony.com>
Cc: linuxppc-dev@ozlabs.org, Paul Mackerras <paulus@samba.org>
Subject: Re: [PATCH] powerpc: Instrument Hypervisor Calls
Date: Mon, 14 Aug 2006 16:41:46 -0700 [thread overview]
Message-ID: <20060814234146.GA17027@w-mikek2.ibm.com> (raw)
In-Reply-To: <44E108B0.4070207@am.sony.com>
On Mon, Aug 14, 2006 at 04:35:12PM -0700, Geoff Levand wrote:
> Mike Kravetz wrote:
> > +config HCALL_STATS
> > + bool "Hypervisor call instrumentation"
> > + depends on PPC_PSERIES && DEBUG_FS
> > + help
> > + Adds code to keep track of the number of hypervisor calls made and
> > + the amount of time spent in hypervisor calls: both wall time (based
> > + on time base) and cpu time (based on PURR). A directory named
> > + hcall_inst is added at the root of the debugfs filesystem.
>
> Could we keep this more generic and not mention platform specific
> things like PURR?
Not sure if I follow. PURR will be used/displayed if available. Time
based statistics will always be available.
I can change the description to make this clear. Or, are you asking
that this not be mentioned at all? Based on previous discussions, I
added the ability to display both wall and cpu time if available.
Thanks,
--
Mike
next prev parent reply other threads:[~2006-08-14 23:41 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-14 23:21 [PATCH] powerpc: Instrument Hypervisor Calls Mike Kravetz
2006-08-14 23:35 ` Geoff Levand
2006-08-14 23:41 ` Mike Kravetz [this message]
2006-08-15 2:01 ` Geoff Levand
2006-08-15 2:34 ` Mike Kravetz
2006-08-15 1:03 ` Stephen Rothwell
2006-08-15 2:32 ` Mike Kravetz
2006-08-15 3:12 ` Stephen Rothwell
2006-08-15 3:32 ` Dave Boutcher
-- strict thread matches above, loose matches on Subject: below --
2006-08-16 16:04 Mike Kravetz
2006-08-24 6:55 ` Paul Mackerras
2006-08-25 18:52 ` Mike Kravetz
2006-09-06 23:23 Mike Kravetz
2006-09-07 0:34 ` Paul Mackerras
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=20060814234146.GA17027@w-mikek2.ibm.com \
--to=kravetz@us.ibm.com \
--cc=geoffrey.levand@am.sony.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).