Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.kernel > #1576744
| From | Tom Zanussi <tom.zanussi@linux.intel.com> |
|---|---|
| Newsgroups | linux.kernel |
| Subject | [RFC][PATCH 12/21] tracing: Account for variables in named trigger compatibility |
| Date | 2017-02-08 18:30 +0100 |
| Message-ID | <t8Ee6-3aO-25@gated-at.bofh.it> (permalink) |
| References | <t8Ee5-3aO-3@gated-at.bofh.it> |
| Organization | linux.* mail to news gateway |
Named triggers must also have the same set of variables in order to be
considered compatible - update the trigger match test to account for
that.
The reason for this requirement is that named triggers with variables
are meant to allow one or more events to set the same variable.
Signed-off-by: Tom Zanussi <tom.zanussi@linux.intel.com>
---
kernel/trace/trace_events_hist.c | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/kernel/trace/trace_events_hist.c b/kernel/trace/trace_events_hist.c
index e707577..889455e 100644
--- a/kernel/trace/trace_events_hist.c
+++ b/kernel/trace/trace_events_hist.c
@@ -1576,6 +1576,10 @@ static bool hist_trigger_match(struct event_trigger_data *data,
return false;
if (key_field->is_signed != key_field_test->is_signed)
return false;
+ if ((key_field->var_name && !key_field_test->var_name) ||
+ (!key_field->var_name && key_field_test->var_name) ||
+ strcmp(key_field->var_name, key_field_test->var_name) != 0)
+ return false;
}
for (i = 0; i < hist_data->n_sort_keys; i++) {
--
1.9.3
Back to linux.kernel | Previous | Next — Next in thread | Find similar | Unroll thread
[RFC][PATCH 12/21] tracing: Account for variables in named trigger compatibility Tom Zanussi <tom.zanussi@linux.intel.com> - 2017-02-08 18:30 +0100 Re: [RFC][PATCH 12/21] tracing: Account for variables in named trigger compatibility Namhyung Kim <namhyung@kernel.org> - 2017-02-13 07:10 +0100
csiph-web