public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Timothy Miller <miller@techsource.com>
To: Mike Fedyk <mfedyk@matchmail.com>
Cc: John Bradford <john@grabjohn.com>,
	root@chaos.analogic.com,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: kernel 'simulator' and wave-form analysis tool?
Date: Mon, 08 Mar 2004 11:33:40 -0500	[thread overview]
Message-ID: <404CA064.6040108@techsource.com> (raw)
In-Reply-To: <404A900B.4020105@matchmail.com>



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.
>>
>>
>>
>> Doesn't Valgrind already do most of what you want?
> 
> 
> Can you valgrind a UML process?
> 
> Tim, what will this give you that a stack trace won't?
> 
> 

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.


  parent reply	other threads:[~2004-03-08 16:20 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 [this message]
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=404CA064.6040108@techsource.com \
    --to=miller@techsource.com \
    --cc=john@grabjohn.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mfedyk@matchmail.com \
    --cc=root@chaos.analogic.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