Kprobes Support for ARM arch

[Quentin Barnes]

>Hi All,
>
>Recently we completed the kprobes support for ARM architecture
>targetted at 2.6.16 kernel. I have uploaded these patches in the 
>below CELF wiki page along with few test programs.
>This implementation is tested using 2.6.16-24 kernel for 
>OMAP5912 OSK reference platform. 
>
>The patch is available in the below CELF wiki page
>http://tree.celinuxforum.org/CelfPubWiki/PatchArchive
>
>The patch can be downloaded directly from here
>http://tree.celinuxforum.org/CelfPubWiki/PatchArchive?action=AttachFile&do=get&target=kprobes-arm-patches-2.6.16.24.tgz
>
>This implementation supports only kprobes and doesnot
>support any other variants like jprobes, kretprobes etc.
>Also it doesnot support branch/jump instructions probing.
>
>I noticed some discussions regarding ARM kprobes in the
>archive. We are open to suggestions and how this implementation can
>be improved. 

Abhishek Sagar and I have been working together on a joint ARM
kprobes effort for some time.

We have kprobes, jprobes, kretprobes, and boosting support(*)
hobbling along now for ARM.  The port is also SMP clean and
preemption safe.  It is ported against 2.6.19.1.  We're pretty much
code complete and doing cleanup, some manual optimizations, and
testing now.  We're planning on releasing our patch probably about
the end of this month.

If you like, I can send you our work-in-progress for your review.

Quentin


*) The boosting model I've implemented is not the standard boosting
   model, but it effectively does the same thing my eliminating the
   second breakpoint exception.  This approach works in all cases,
   not for just some instructions, so the second breakpoint is never
   necessary.

>Best Regards
>Madhvesh
>
>=============================
>Madhvesh Sulibhavi
>Sony India Software Centre
>Bangalore
>=============================
>
>Note: My official mail id is there in the CC list. Since "disclaimer notice" in the mail
>footer could not be rectified, i am making this announcement using above mail
>id. You can reach me from that mail id also.