From: Herbert Poetzl <herbert@13thfloor.at>
To: Timothy Miller <miller@techsource.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: kernel 'simulator' and wave-form analysis tool?
Date: Fri, 12 Mar 2004 22:38:55 +0100 [thread overview]
Message-ID: <20040312213855.GA8832@MAIL.13thfloor.at> (raw)
In-Reply-To: <404CA064.6040108@techsource.com>
On Mon, Mar 08, 2004 at 11:33:40AM -0500, Timothy Miller wrote:
>
>
> Mike Fedyk wrote:
> >John Bradford wrote:
> >
> >>>I must have been unclear. I was not suggesting adding hardware. I
> >>>was suggesting that we could run Linux under Bochs, which is a
> >>>software x86 emulator. Being what it is, hooks can be added to track
> >>>"cpu activity" is it occurs within the emulator. This is all a
> >>>simulation. The key idea I was suggesting was to log processor
> >>>activity (of the emulator) and develop a viewer program which would
> >>>help people visualize the activity.
sounds good and useful to me, have a look at
other simulators/emulators too, for example
I use QEMU[1] to test linux kernels, because
it is much simpler and faster than Bochs (YMMV)
best,
Herbert
> If your stack gets hosed by a bug, a simulator with a complete history
> of memory writes will help you discover the problem.
>
> I know nothing about Valgrind.
[1] http://fabrice.bellard.free.fr/qemu/
prev parent reply other threads:[~2004-03-12 21:38 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-05 17:05 kernel 'simulator' and wave-form analysis tool? Timothy Miller
[not found] ` <4048B36E.8000605@techsource.com.suse.lists.linux.kernel>
2004-03-05 17:48 ` 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 [this message]
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=20040312213855.GA8832@MAIL.13thfloor.at \
--to=herbert@13thfloor.at \
--cc=linux-kernel@vger.kernel.org \
--cc=miller@techsource.com \
/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