Andi Kleen wrote: >> And the functions they call? >> > > Yes. But you only really need it for the actual callback, not the bulk > of stop_machine_run() (which calls scheduler and lots of other stuff) > The actual callback should be pretty limited already so it shouldn't > be a big limitation. > > -Andi > Hmm. Seems dangerous to rely on this, because functions could change from inline to out of line without people noticing that it affects this very corner case for kprobes + paravirt + stop_machine. Is there a way to cascade the __kprobes declaration to all called functions, perhaps with a static checker, like sparse? Zach
