From: Andi Kleen <ak@suse.de>
To: "David S. Miller" <davem@davemloft.net>
Cc: ak@suse.de, Adnan.Khaleel@newisys.com, linux-kernel@vger.kernel.org
Subject: Re: Instruction Tracing for Linux
Date: Fri, 8 Jul 2005 21:31:05 +0200 [thread overview]
Message-ID: <20050708193105.GT21330@wotan.suse.de> (raw)
In-Reply-To: <20050708.122334.66180889.davem@davemloft.net>
On Fri, Jul 08, 2005 at 12:23:34PM -0700, David S. Miller wrote:
> From: Andi Kleen <ak@suse.de>
> Date: 08 Jul 2005 21:11:03 +0200
>
> > While some CPUs (like Intel P4) have ways to do such hardware
> > tracing I know of no free tool that uses it. There are some user
> > space tools to collect at user space, but they probably won't help you.
>
> FWIW, even without explicit tracing support in the CPU it
> is possible to get these kinds of traces nontheless.
x86 has single step by default, but doing full tracing with that
would be difficult and slow. With the simulators it is really
easy though - i used that extensively while bringing up x86-64.
-Andi
next prev parent reply other threads:[~2005-07-08 19:35 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <DC392CA07E5A5746837A411B4CA2B713010D7790@sekhmet.ad.newisys.com.suse.lists.linux.kernel>
2005-07-08 19:11 ` Instruction Tracing for Linux Andi Kleen
2005-07-08 9:20 ` Marcelo Tosatti
2005-07-08 19:23 ` David S. Miller
2005-07-08 19:31 ` Andi Kleen [this message]
2005-07-08 22:46 Adnan Khaleel
2005-07-08 22:47 ` Andi Kleen
-- strict thread matches above, loose matches on Subject: below --
2005-07-08 20:49 Adnan Khaleel
2005-07-08 22:02 ` Miquel van Smoorenburg
2005-07-08 22:12 ` 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=20050708193105.GT21330@wotan.suse.de \
--to=ak@suse.de \
--cc=Adnan.Khaleel@newisys.com \
--cc=davem@davemloft.net \
--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