Hi Joe, > > Perhaps "responsibility" is a better description. This would introduce > an attribute that someone's userspace utility is relying on. It should > at least have a kselftest to ensure a random patch in 2027 doesn't break > it. I sent this patch to see the what the community thinks about this attribute (although it think it is necessary and this will be more convenient for users). If this patch is seems to be good, I will add a kselftest to this attribute. As Miroslav and Petr said, keeping klp_ftrace_handler() as fast as possible is also important, which I need to find a way to keep it fast (or just setting the state to be true instead of a judgement?). > The kernel docs provide a lot of explanation of the complete ftracing > interface. It's pretty power stuff, though you may also go the other > direction and look into using the trace-cmd front end to simplify all of > the sysfs manipulation. Julia Evans wrote a blog [1] a while back that > provides a some more examples. > > [1] https://jvns.ca/blog/2017/03/19/getting-started-with-ftrace/ > > -- > Joe Nice of you! Thanks! I will learn it! Regards, Wardenjohn
