Path: utzoo!utgpu!water!watmath!clyde!rutgers!ames!pasteur!ucbvax!sdcsvax!ucsdhub!jack!crash!jeh
From: jeh@crash.cts.com (Jamie Hanrahan)
Newsgroups: comp.os.vms
Subject: Re: monitor modes (on a per-process basis)
Summary: Not provided in standard VMS
Keywords: monitor modes
Message-ID: <2434@crash.cts.com>
Date: 28 Jan 88 19:55:24 GMT
References: <2504@emory.uucp>
Reply-To: jeh@crash.CTS.COM (Jamie Hanrahan)
Organization: CMKRNL Press, San Diego, CA
Lines: 12

In article <2504@emory.uucp> osdbm@emory.uucp (Brendan Moriarity {EUCC}) writes:
>	... it would be useful to break down the actual processor time spent
>	in each mode for the particular process being benchmarked. 

I agree, it certainly *would* be useful!  Alas, VMS doesn't keep track of
things to this level of detail.  The DEC layered product called SPM might,
but as we don't have it here I don't know.  

It's certainly possible to write a little hardware clock intercept routine
that will track this information for you, but only if you're comfortable
with writing elevated-IPL code.  If anyone is interested, let me know, and
I'll give you an outline.