Displaying 3 results from an estimated 3 matches for "trapstat".
Did you mean:
tapstate
2006 Oct 31
0
6310485 gcc and trapstat don''t get along
Author: dmick
Repository: /hg/zfs-crypto/gate
Revision: aaf08404ec592e56684b19ac5e3773c0d3155d0c
Log message:
6310485 gcc and trapstat don''t get along
6310536 gcc and sfmmu header don''t get along
6310555 gcc and memlists don''t get along
Files:
update: usr/src/uts/common/os/mem_config.c
update: usr/src/uts/common/os/memlist_new.c
update: usr/src/uts/sfmmu/vm/hat_sfmmu.h
update: usr/src/uts/sun4/io/tr...
2007 Feb 05
1
trap info from dtrace ???
Can dtrace help with collecting any of the following, in otherwords are
there any existing counters to be exploited, or am I going to have to make
my own custom Solaris build with additional counters...
currently I can get this detailed trap information from our SPARC simulator,
for example here are some ints-per-sec during a benchmark-of-interest:
sending-source
2005 Nov 18
6
expected system load from DTrace scripts/probes
Does anyone out there have any thoughts on the type of load common
DTrace scripts would cause on a system if run 24x7? I know "common
DTrace scripts" and their underlining probe calls a vague statement. So
for the lack of a common and establish set of scripts in the OS, I''ll
use the most popular right for my question...the DTraceToolkit from
Brendan Gregg. Which by the