Lines Matching refs:events
61 * allowing new hook families and their events.
67 * 2) add events to the registered family with calls to hook_event_add.
75 * It is a requirement that the provider of hook events work in the reverse
77 * 1) remove events from each hook family created earlier
80 * When doing teardown of both events and families, a check is made to see
92 * ONLY the caller that adds the family and the events ever has a direct
173 * can be received through the physical_in, etc, events. This is achieved
181 * a notification callback is added, a series of fake callback events
835 hei->hei_kstats.events.value.ui64++;
967 * Check if the family is in use by the presence of either events
1215 * action that simulates register events.
1369 * kstats just count the events as they happen, the total number of
1378 { "events", KSTAT_DATA_UINT64 }
2508 * was expecting. This then allows the simulation of HN_UNREGISTER events