linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Mike Kravetz <kravetz@us.ibm.com>
To: Arnd Bergmann <arnd@arndb.de>
Cc: Bryan Rosenburg <rosnbrg@us.ibm.com>,
	linuxppc-dev@ozlabs.org, Nathan Lynch <ntl@pobox.com>,
	Paul Mackerras <paulus@samba.org>,
	Christopher Yeoh <cyeoh@samba.org>
Subject: Re: [PATCH 2/3] powerpc: Instrument Hypervisor Calls: add wrappers
Date: Thu, 15 Jun 2006 07:58:26 -0700	[thread overview]
Message-ID: <20060615145826.GA3461@monkey.ibm.com> (raw)
In-Reply-To: <200606151309.40360.arnd@arndb.de>

On Thu, Jun 15, 2006 at 01:09:39PM +0200, Arnd Bergmann wrote:
> On Thursday 15 June 2006 01:52, Mike Kravetz wrote:
> > I'm really wondering what would be the best way to make these stats
> > available to userspace.  As mentioned, putting them into sysfs would
> > violate the one value/one file rule.  The use of /proc is discouraged.
> > debugfs was mentioned, but I have never used it.  Noticed that debugfs
> > was enabled in the default config (at least for pseries).  Looks like
> > that would be the best alternative.  Agree?
> 
> Debugfs sounds good. If you use one file per hcall, it's probably as
> easy as

But does debugfs have the same one value/one file rule?  Thought I could
dump all the data in a single debugfs file.

-- 
Mike

  reply	other threads:[~2006-06-15 14:58 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-06-14  3:47 [PATCH 0/3] powerpc: Instrument Hypervisor Calls Mike Kravetz
2006-06-14  3:50 ` [PATCH 1/3] powerpc: Instrument Hypervisor Calls: merge headers Mike Kravetz
2006-06-14  3:52 ` [PATCH 2/3] powerpc: Instrument Hypervisor Calls: add wrappers Mike Kravetz
2006-06-14  7:23   ` Arnd Bergmann
2006-06-14 14:42   ` Nathan Lynch
2006-06-14 22:33     ` Paul Mackerras
2006-06-14 22:40       ` Nathan Lynch
2006-06-14 23:52         ` Mike Kravetz
2006-06-15 11:09           ` Arnd Bergmann
2006-06-15 14:58             ` Mike Kravetz [this message]
2006-06-15 16:06               ` Arnd Bergmann
2006-06-16 16:11       ` Mike Kravetz
2006-06-14  3:54 ` [PATCH 0/3] powerpc: Instrument Hypervisor Calls: add sysfs files Mike Kravetz
2006-06-14 14:22   ` Nathan Lynch
2006-06-15 11:45     ` Christopher Yeoh
2006-06-14 14:30   ` Dave C Boutcher
2006-06-14 14:39 ` [RFC] New hcall mechanism Was: [PATCH 0/3] powerpc: Instrument Hypervisor Calls Jimi Xenidis
  -- strict thread matches above, loose matches on Subject: below --
2006-06-22 22:56 Mike Kravetz
2006-06-22 22:58 ` [PATCH 2/3] powerpc: Instrument Hypervisor Calls: add wrappers Mike Kravetz
2006-07-14 23:37 [PATCH 0/3] powerpc: Instrument Hypervisor Calls Mike Kravetz
2006-07-14 23:40 ` [PATCH 2/3] powerpc: Instrument Hypervisor Calls: add wrappers Mike Kravetz
2006-07-15  0:15   ` Nathan Lynch
2006-07-15  0:41     ` Mike Kravetz
2006-07-15  8:03       ` Nathan Lynch
2006-07-18 20:47 [PATCH 0/3] powerpc: Instrument Hypervisor Calls 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

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=20060615145826.GA3461@monkey.ibm.com \
    --to=kravetz@us.ibm.com \
    --cc=arnd@arndb.de \
    --cc=cyeoh@samba.org \
    --cc=linuxppc-dev@ozlabs.org \
    --cc=ntl@pobox.com \
    --cc=paulus@samba.org \
    --cc=rosnbrg@us.ibm.com \
    /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).