From owner-freebsd-hackers  Wed Aug 21 06:19:56 1996
Return-Path: owner-hackers
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.5/8.7.3) id GAA14136
          for hackers-outgoing; Wed, 21 Aug 1996 06:19:56 -0700 (PDT)
Received: from cheops.anu.edu.au (avalon@cheops.anu.edu.au [150.203.76.24])
          by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id GAA14111
          for <hackers@freebsd.org>; Wed, 21 Aug 1996 06:19:49 -0700 (PDT)
Message-Id: <199608211319.GAA14111@freefall.freebsd.org>
Received: by cheops.anu.edu.au
	(1.37.109.16/16.2) id AA233393564; Wed, 21 Aug 1996 23:19:24 +1000
From: Darren Reed <avalon@coombs.anu.edu.au>
Subject: Re: Chris Torek: Re: i386 interrupt counters
To: jkh@time.cdrom.com (Jordan K. Hubbard)
Date: Wed, 21 Aug 1996 23:19:24 +1000 (EST)
Cc: hackers@freebsd.org, current-users@netbsd.org, torek@BSDI.COM
In-Reply-To: <15241.840630110@time.cdrom.com> from "Jordan K. Hubbard" at Aug 21, 96 05:21:50 am
X-Mailer: ELM [version 2.4 PL23]
Content-Type: text
Sender: owner-hackers@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

In some mail from Jordan K. Hubbard, sie said:
> FYI..
> ------- Forwarded Message
> 
> From: Chris Torek <torek@BSDI.COM>
> Message-Id: <199608210823.CAA02423@forge.BSDI.COM>
> To: explorer@flame.org, soda@sra.co.jp
> Subject: Re: i386 interrupt counters
> Cc: explorer@cygnus.com, port-i386@NetBSD.ORG, tech-kern@NetBSD.ORG
> Sender: owner-port-i386@NetBSD.ORG
> Precedence: list
> X-Loop: port-i386@NetBSD.ORG
> 
> FWIW:
> 
> >> BTW, do you use "struct evcnt" to implement it ? (see sparc port)
> 
> >No, but I suspect I should be, no?  ;)
> 
> I always intended to have `systat -vmstat' display the event
> counters in the `Interrupts' column (probably relabelling the
> column).  There should be a sysctl to retrieve them from the
> kernel, too.
> 
> Chris
> 
> ------- End of Forwarded Message

Checkout pstat(2) under HP-UX 9 and 10 (there is only a man page on 10).

For what its worth, I've written a version of w(1) using pstat(2) that
worked as well as the original except it wasn't setuid-root.  I'm sure
the same could be done for ps(1) on HP-UX and there is a top-style tool
called "yamm" for HP-UX that doesn't need to be setuid root.  I also
believe that some of the vmstat/systat type tools also use this interface.

I think pstat(2) is an excellent idea, so long as you don't believe that
the information needed by ps/w, etc, doesn't need to be private.

Darren