On Tue, May 21, 2024 at 1:04 AM Petr Mladek <pmladek@xxxxxxxx> wrote: [...] > > > > Yes, but the information you get is limited compared to what is available > > now. You would obtain the information that a patched function was called > > but ftrace could also give you the context and more. > > Another motivation to use ftrace for testing is that it does not > affect the performance in production. > > We should keep klp_ftrace_handler() as fast as possible so that we > could livepatch also performance sensitive functions. At LPC last year, we discussed about adding a counter to each klp_func, like: struct klp_func { ... u64 __percpu counter; ... }; With some static_key (+ sysctl), this should give us a way to estimate the overhead of livepatch. If we have the counter, this patch is not needed any more. Does this (adding the counter) sound like something we still want to pursue? Thanks, Song