* firmware tracing
@ 2011-03-03 7:29 Zhiwei Ying
2011-03-04 18:02 ` Frank Ch. Eigler
0 siblings, 1 reply; 2+ messages in thread
From: Zhiwei Ying @ 2011-03-03 7:29 UTC (permalink / raw)
To: systemtap
Hi,
Has anyone thought about using systemtap to trace firmware code? Any
information?
Thanks,
Zhiwei
^ permalink raw reply [flat|nested] 2+ messages in thread
* Re: firmware tracing
2011-03-03 7:29 firmware tracing Zhiwei Ying
@ 2011-03-04 18:02 ` Frank Ch. Eigler
0 siblings, 0 replies; 2+ messages in thread
From: Frank Ch. Eigler @ 2011-03-04 18:02 UTC (permalink / raw)
To: Zhiwei Ying; +Cc: systemtap
zhiwei.ying wrote:
> Has anyone thought about using systemtap to trace firmware code? Any
> information?
To the extent the firmware is of the form that the host kernel
interprets, like ACPI, that's straightforward. One'd probe key points
in the interpreter. If the firmware is binary code for some embedded
microcontroller, and is run without the participation of the host CPU,
then I can't think of simple uses of systemtap to trace the firmware.
Tracing interactions (host code that deals with interrupts, PCI
transactions, DMA) should be doable though.
- FChE
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2011-03-04 18:02 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2011-03-03 7:29 firmware tracing Zhiwei Ying
2011-03-04 18:02 ` Frank Ch. Eigler
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).