On Mon, Jan 17, 2022 at 04:51:37PM -0800, Philip Guenther wrote: > On Mon, Jan 17, 2022 at 5:02 AM Klemens Nanni <[email protected]> wrote: > > > These don't hurt on !VMM architectures but I was still surprised to see > > them on e.g. sparc64: > > > > # arch -s ; btrace -l | grep vmm > > sparc64 > > tracepoint:vmm:guest_enter > > tracepoint:vmm:guest_exit > > > > Like some network drivers, we could use __amd64__ to limit those to > > amd64 and save a few bits in all other kernels. > > > > Is this approach feasible or should we just ignore such one-offs? > > > > If there's a non-trivial number of trace points in drivers, then it would > suggest that such tracepoints should be added/registered/pick-a-term by the > driver's attach routine.
This needs a little bit of refactor around probe registration. I plan to commit the initial `#ifdef __amd64__' diff with "OK pv" soon unless I hear objections.
