From: Timothy Miller <miller@techsource.com>
To: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: kernel 'simulator' and wave-form analysis tool?
Date: Fri, 05 Mar 2004 12:05:50 -0500 [thread overview]
Message-ID: <4048B36E.8000605@techsource.com> (raw)
I wouldn't be surprised if someone's already done this, but...
I'm a chip designer, and when we design a chip, before we put it in
silicon, we use simulator tools that emulate the logic we designed. One
of the most important parts of the simulator is the wave-form analyzer.
We run the simulator for some period of time, and then we can look at
the history of every signal in the design.
Well, I've been looking at Bochs, and it has this 'instrumentation'
facility which you can use to track everything that goes on in its
simulation of an x86 processor. If I were to put a hook in to track all
memory writes, then I could record all memory activity (I could hook
much more!). When a crash occurs, someone could use the analogue to the
wave-form tool to trace execution back to the event that caused the
problem (because, for instance, heap corruption causes crashes much
later than the bug).
Would it be a productive use of my time to work on this?
next reply other threads:[~2004-03-05 16:53 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-05 17:05 Timothy Miller [this message]
[not found] ` <4048B36E.8000605@techsource.com.suse.lists.linux.kernel>
2004-03-05 17:48 ` kernel 'simulator' and wave-form analysis tool? Andi Kleen
2004-03-05 18:04 ` Richard B. Johnson
2004-03-05 18:52 ` Timothy Miller
2004-03-06 11:13 ` John Bradford
2004-03-07 2:59 ` Mike Fedyk
2004-03-07 18:55 ` Jeff Dike
2004-03-08 16:33 ` Timothy Miller
2004-03-12 21:38 ` Herbert Poetzl
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=4048B36E.8000605@techsource.com \
--to=miller@techsource.com \
--cc=linux-kernel@vger.kernel.org \
/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