From: "David S. Miller" <davem@davemloft.net>
To: ak@suse.de
Cc: Adnan.Khaleel@newisys.com, linux-kernel@vger.kernel.org
Subject: Re: Instruction Tracing for Linux
Date: Fri, 08 Jul 2005 12:23:34 -0700 (PDT) [thread overview]
Message-ID: <20050708.122334.66180889.davem@davemloft.net> (raw)
In-Reply-To: <p738y0hp0zc.fsf@verdi.suse.de>
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.
One great example is how they did this on Sparc sun4d machines
at Sun using SKY which was written by Gordon Irlam. You can
read about it at:
http://www.base.com/gordoni/sky.html
Basically, the "simulator" would take advantage of Sparc's
delay slot branching to explicitly execute one instruction
from the kernel's code stream at a time.
So it would branch to the kernel's current PC, and in the delay
slot branch back into the simulator.
The only special case is that it needs two temporary registers, global
registers %g2 and %g3, to pull off this trick. So if the instruction
needed to actually use either register %g2 or %g3, it was emulated in
software instead of actually being executed.
next prev parent reply other threads:[~2005-07-08 19:27 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 ` Andi Kleen
2005-07-08 9:20 ` Marcelo Tosatti
2005-07-08 19:23 ` David S. Miller [this message]
2005-07-08 19:31 ` Andi Kleen
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=20050708.122334.66180889.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=Adnan.Khaleel@newisys.com \
--cc=ak@suse.de \
--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
all inboxes | Powered by JetHome®