This is the mail archive of the systemtap@sourceware.org mailing list for the systemtap project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: firmware tracing

From: fche at redhat dot com (Frank Ch. Eigler)
To: Zhiwei Ying <zhiwei dot ying at gmail dot com>
Cc: systemtap <systemtap at sources dot redhat dot com>
Date: Fri, 04 Mar 2011 13:01:44 -0500
Subject: Re: firmware tracing
References: <AANLkTinHcG2ZmMwPGy2Lk4AQ7dxtYHC_J30x4WZ92it=@mail.gmail.com>

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

References:
- firmware tracing
  - From: Zhiwei Ying

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]