From: andrey mirtchovski <andrey@lanl.gov>
To: 9fans@cse.psu.edu
Subject: [9fans] kprof
Date: Sun, 21 Apr 2002 10:30:30 -0600 [thread overview]
Message-ID: <20020421162852.D7ECA19988@mail.cse.psu.edu> (raw)
i'm trying to modify kprof to provide a syscall tree the same way
'prof -d' does, but i can't figure out how to handle the data
accumulated in devkprof.c's _kproftimer().
i understand the current way it works -- storing the total time the
kernel has spent in a certain function, but what i can't figure out is
how to store the actual PC values for the entire timespan between a
start and a stop command.
one way is to create a (presumably large!) array and incrementally
store the current PC value at each call to _kproftimer(), but is that
a decent solution? am i right in assuming (based on observations :)
that no syscall can be executed in _kproftimer()?
andrey
next reply other threads:[~2002-04-21 16:30 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-21 16:30 andrey mirtchovski [this message]
2002-04-21 16:41 rob pike, esq.
2002-04-21 16:51 andrey mirtchovski
2002-04-21 16:53 rob pike, esq.
2002-04-21 19:13 forsyth
2002-04-21 20:35 andrey mirtchovski
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=20020421162852.D7ECA19988@mail.cse.psu.edu \
--to=andrey@lanl.gov \
--cc=9fans@cse.psu.edu \
/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).