On Thu, 22 Jun 2017 08:01:08 +0000 "Ucan, Emre (ADITG/ESB)" <[email protected]> wrote:
> Hello Pekka, > > I think it is very hard do it in a generic way, because it is very > dependent on the kernel and architecture. We are using systemtap in > ADIT for similar purpose. You can add probe points without changing > the binary which you are debugging. Hi Emre, I thought so, thanks for confirming. I've also thought of new uses for weston-debug interface. The weston_debug_scope_cb begin callback could ensure there is a timer registered and from the timer callback print e.g. per-surface or per-output rendering statistics. The timer would be torn down when it fires and sees nothing is subscribed anymore. Thanks, pq > > -----Original Message----- > > From: Pekka Paalanen [mailto:[email protected]] > > Sent: Mittwoch, 21. Juni 2017 13:24 > > To: [email protected] > > Cc: Ucan, Emre (ADITG/ESB) > > Subject: Re: [RFC weston 0/9] weston-debug protocol, API, and tool > > > > On Sat, 3 Jun 2017 14:57:02 +0300 > > Pekka Paalanen <[email protected]> wrote: > > Hi, > > > > apropos, I have been entertaining a completely different idea: perf > > probe. > > > > Apparently one can set userspace probing points with 'perf probe' > > and then record them, which should be less overhead when not used > > than the weston-debug API. But there are many open questions I have > > not had the time to chase: .. > > I'm skeptical of this idea being useful, but thought I'd mention it > > just in case. OTOH, the weston-debug proposal is relatively easy to > > understand and use, and it should be very reliable, debug info or no.
pgphR2pQ7kgaI.pgp
Description: OpenPGP digital signature
_______________________________________________ wayland-devel mailing list [email protected] https://lists.freedesktop.org/mailman/listinfo/wayland-devel
