projects
/
lttng-tools.git
/ blobdiff
commit
grep
author
committer
pickaxe
?
search:
re
summary
|
shortlog
|
log
|
commit
|
commitdiff
|
tree
raw
|
inline
| side by side
DBG: add debug statement for trigger not bound to any object
[lttng-tools.git]
/
src
/
bin
/
lttng-sessiond
/
notification-thread.h
diff --git
a/src/bin/lttng-sessiond/notification-thread.h
b/src/bin/lttng-sessiond/notification-thread.h
index 134804f9d0718a76415e898f556e612921c95f9f..c80bb691db52263c9075a31e21f968037811f51b 100644
(file)
--- a/
src/bin/lttng-sessiond/notification-thread.h
+++ b/
src/bin/lttng-sessiond/notification-thread.h
@@
-108,9
+108,14
@@
struct notification_thread_handle {
* channels through their struct channel_info (ref-counting is used).
*
* - triggers_ht:
* channels through their struct channel_info (ref-counting is used).
*
* - triggers_ht:
- * associates a
condition
to a struct lttng_trigger_ht_element.
+ * associates a
trigger
to a struct lttng_trigger_ht_element.
* The hash table holds the ownership of the
* lttng_trigger_ht_elements along with the triggers themselves.
* The hash table holds the ownership of the
* lttng_trigger_ht_elements along with the triggers themselves.
+ * - triggers_by_name_uid_ht:
+ * associates a trigger (name, uid) tuple to
+ * a struct lttng_trigger_ht_element.
+ * The hash table does not hold any ownership and is used strictly
+ * for lookup on registration.
*
* The thread reacts to the following internal events:
* 1) creation of a tracing channel,
*
* The thread reacts to the following internal events:
* 1) creation of a tracing channel,
@@
-154,6
+159,7
@@
struct notification_thread_handle {
* notification_trigger_clients_ht,
* - add trigger to channel_triggers_ht (if applicable),
* - add trigger to session_triggers_ht (if applicable),
* notification_trigger_clients_ht,
* - add trigger to channel_triggers_ht (if applicable),
* - add trigger to session_triggers_ht (if applicable),
+ * - add trigger to triggers_by_name_uid_ht
* - add trigger to triggers_ht
* - evaluate the trigger's condition right away to react if that condition
* is true from the beginning.
* - add trigger to triggers_ht
* - evaluate the trigger's condition right away to react if that condition
* is true from the beginning.
@@
-163,6
+169,7
@@
struct notification_thread_handle {
* - remove the trigger from the notification_trigger_clients_ht,
* - remove trigger from channel_triggers_ht (if applicable),
* - remove trigger from session_triggers_ht (if applicable),
* - remove the trigger from the notification_trigger_clients_ht,
* - remove trigger from channel_triggers_ht (if applicable),
* - remove trigger from session_triggers_ht (if applicable),
+ * - remove trigger from triggers_by_name_uid_ht
* - remove trigger from triggers_ht
*
* 5) Reception of a channel monitor sample from the consumer daemon
* - remove trigger from triggers_ht
*
* 5) Reception of a channel monitor sample from the consumer daemon
@@
-210,6
+217,11
@@
struct notification_thread_state {
struct cds_lfht *channels_ht;
struct cds_lfht *sessions_ht;
struct cds_lfht *triggers_ht;
struct cds_lfht *channels_ht;
struct cds_lfht *sessions_ht;
struct cds_lfht *triggers_ht;
+ struct cds_lfht *triggers_by_name_uid_ht;
+ struct {
+ uint64_t next_tracer_token;
+ uint64_t name_offset;
+ } trigger_id;
notification_client_id next_notification_client_id;
struct action_executor *executor;
};
notification_client_id next_notification_client_id;
struct action_executor *executor;
};
This page took
0.024133 seconds
and
4
git commands to generate.