From: "Miquel van Smoorenburg" <miquels@cistron.nl>
To: linux-kernel@vger.kernel.org
Subject: Re: Instruction Tracing for Linux
Date: Fri, 8 Jul 2005 22:02:47 +0000 (UTC) [thread overview]
Message-ID: <damt67$2a3$1@news.cistron.nl> (raw)
In-Reply-To: DC392CA07E5A5746837A411B4CA2B713010D7791@sekhmet.ad.newisys.com
In article <DC392CA07E5A5746837A411B4CA2B713010D7791@sekhmet.ad.newisys.com>,
Adnan Khaleel <Adnan.Khaleel@newisys.com> 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.
>
>Even if I can't trace the kernel, is there anything available for just
>the user space stuff?
You might be able to get valgrind or cachegrind to do what you need..
Mike.
next prev parent reply other threads:[~2005-07-08 22:20 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 [this message]
2005-07-08 22:12 ` Andi Kleen
-- 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='damt67$2a3$1@news.cistron.nl' \
--to=miquels@cistron.nl \
--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