Cleanup: event_notifier -> notify in comments

[lttng-modules.git] / src / probes / lttng-kprobes.c

diff --git a/src/probes/lttng-kprobes.c b/src/probes/lttng-kprobes.c
index 4e80f1ef62e3acf5ae61c949c8a5af3be7eb4a25..82433bd84c0793c9a1cd93ab40335caf5d475113 100644 (file)
--- a/src/probes/lttng-kprobes.c
+++ b/src/probes/lttng-kprobes.c
@@ -54,11 +54,13 @@ int lttng_kprobes_event_notifier_handler_pre(struct kprobe *p, struct pt_regs *r
 {
        struct lttng_event_notifier *event_notifier =
                container_of(p, struct lttng_event_notifier, u.kprobe.kp);
+       struct lttng_kernel_notifier_ctx notif_ctx;
 
        if (unlikely(!READ_ONCE(event_notifier->enabled)))
                return 0;
 
-       event_notifier->send_notification(event_notifier);
+       notif_ctx.eval_capture = LTTNG_READ_ONCE(event_notifier->eval_capture);
+       event_notifier->send_notification(event_notifier, NULL, NULL, &notif_ctx);
 
        return 0;
 }
@@ -170,7 +172,7 @@ int _lttng_kprobes_register(const char *symbol_name,
        lttng_kp->kp.addr = (void *) (unsigned long) addr;
 
        /*
-        * Ensure the memory we just allocated don't event_notifier page faults.
+        * Ensure the memory we just allocated don't notify page faults.
         * Well.. kprobes itself puts the page fault handler on the blacklist,
         * but we can never be too careful.
         */