This is the mail archive of the
systemtap@sourceware.org
mailing list for the systemtap project.
Re: [PATCH] kprobes for s390 architecture
- From: fche at redhat dot com (Frank Ch. Eigler)
- To: Heiko Carstens <heiko dot carstens at de dot ibm dot com>
- Cc: Martin Schwidefsky <schwidefsky at de dot ibm dot com>, Jan Glauber <jan dot glauber at de dot ibm dot com>, systemtap at sources dot redhat dot com
- Date: 07 Jul 2006 15:51:23 -0400
- Subject: Re: [PATCH] kprobes for s390 architecture
- References: <20060623150344.GL9446@osiris.boeblingen.de.ibm.com> <OF44DB398C.F7A51098-ON88257196.007CD277-88257196.007DC8F0@us.ibm.com> <20060623222106.GA25410@osiris.ibm.com> <20060624113641.GB10403@osiris.ibm.com> <1151421789.5390.65.camel@localhost> <20060628055857.GA9452@osiris.boeblingen.de.ibm.com> <20060707172333.GA12068@localhost.localdomain> <20060707172555.GA10452@osiris.ibm.com>
Heiko Carstens <heiko.carstens@de.ibm.com> writes:
> [...]
> > It works, and I guess at this point is the only way to do it. I'll send out a
> > full patch with this and the other cleanups later.
>
> How fast is this if you have to exchange several hundred instructions?
That's a very appropriate question. Related to it is in general how
fast is it to insert and remove ordinary breakpoints on even non-s390
platforms. Several RH folks recently found that
probe kernel.function("*") {}
took only a few seconds to insert the probes, but a few *minutes* to
remove them at session shutdown.
- FChE