This is the mail archive of the
systemtap@sources.redhat.com
mailing list for the systemtap project.
Re: Hitachi djprobe mechanism
- From: Karim Yaghmour <karim at opersys dot com>
- To: "Keshavamurthy, Anil S" <anil dot s dot keshavamurthy at intel dot com>
- Cc: Satoshi Oshima <soshima at redhat dot com>, Richard J Moore <richardj_moore at uk dot ibm dot com>, systemtap at sources dot redhat dot com, Andi Kleen <ak at suse dot de>, Mathieu Desnoyers <compudj at krystal dot dyndns dot org>, Masami Hiramatsu <hiramatu at sdl dot hitachi dot co dot jp>, Masami Hiramatsu <masami dot hiramatsu at gmail dot com>, michel dot dagenais at polymtl dot ca, Roland McGrath <roland at redhat dot com>, sugita at sdl dot hitachi dot co dot jp
- Date: Mon, 01 Aug 2005 17:18:33 -0400
- Subject: Re: Hitachi djprobe mechanism
- Organization: Opersys inc.
- References: <44BDAFB888F59F408FAE3CC35AB4704101E98CFF@orsmsx409>
- Reply-to: karim at opersys dot com
Keshavamurthy, Anil S wrote:
> So in effect, we just can't look for instruction size greater than 5
> bytes and insert probe there.
True. This is why I was saying "... that's if there aren't other
limitations..."
> This djprobe will push the need for a stronger static
> analysizer/translator in selecting the probe point.
Does this mean that you think we could use djprobe on anything less
than 5 bytes?
Karim
--
Author, Speaker, Developer, Consultant
Pushing Embedded and Real-Time Linux Systems Beyond the Limits
http://www.opersys.com || karim@opersys.com || 1-866-677-4546