From: Andi Kleen <ak@suse.de>
To: Adnan Khaleel <Adnan.Khaleel@newisys.com>
Cc: ak@suse.de, linux-kernel@vger.kernel.org
Subject: Re: Instruction Tracing for Linux
Date: Sat, 9 Jul 2005 00:12:14 +0200 [thread overview]
Message-ID: <20050708221213.GU21330@wotan.suse.de> (raw)
In-Reply-To: <DC392CA07E5A5746837A411B4CA2B713010D7791@sekhmet.ad.newisys.com>
On Fri, Jul 08, 2005 at 03:49:47PM -0500, Adnan Khaleel wrote:
> Thanks for your suggestions. I have been working with Simics, SimNow and Bochs. I've had mixed luck with all of them. Although Simics should be the most promising, I've really had
> an uphill struggle with it especially when it comes to x86-64. I've been playing around with Bochs and most likely will end up using that but it has its drawbacks as well.
I haven't tested any recent versions, but the original development
was near mostly done with Simics and it did work well for me.
iirc there was a recent bug that the optimized memcpy or memset
in the glibc didn't like a CPU returning 0 bytes of cache size and
Simics did that. You might have run into that. It should be
fixed now.
Bochs used to be quite buggy on the x86-64 department and didn't do
multi processor, but that also might have changed. It is significantly
slower than the others.
>
> Even if I can't trace the kernel, is there anything available for just the user space stuff?
The AMD CodeAnalyst for Linux has a simulator that first collects
a trace and then runs that in a CPU model. I assume it does
first single stepping. It's unfortunately binary only.
If slow single stepping is enough it's reasonably easy to write
something yourself too. I have old example source that implements
single stepping.
However I doubt any of them are capable of running the bigger
benchmarks.
-Andi
next prev parent reply other threads:[~2005-07-08 22:15 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-08 20:49 Instruction Tracing for Linux Adnan Khaleel
2005-07-08 22:02 ` Miquel van Smoorenburg
2005-07-08 22:12 ` Andi Kleen [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-07-08 22:46 Adnan Khaleel
2005-07-08 22:47 ` Andi Kleen
[not found] <DC392CA07E5A5746837A411B4CA2B713010D7790@sekhmet.ad.newisys.com.suse.lists.linux.kernel>
2005-07-08 19:11 ` Andi Kleen
2005-07-08 9:20 ` Marcelo Tosatti
2005-07-08 19:23 ` David S. Miller
2005-07-08 19:31 ` Andi Kleen
2005-07-08 16:51 Adnan Khaleel
2005-07-08 17:27 ` Richard B. Johnson
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=20050708221213.GU21330@wotan.suse.de \
--to=ak@suse.de \
--cc=Adnan.Khaleel@newisys.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