Add the mm_numa_cid field to the rseq_update event, allowing tracers to
follow which mm_numa_cid is observed by user-space, and whether negative
mm_numa_cid values are visible in case of internal scheduler
implementation issues.
Signed-off-by: Mathieu Desnoyers <mathieu.desnoyers@xxxxxxxxxxxx>
---
include/trace/events/rseq.h | 6 ++++--
1 file changed, 4 insertions(+), 2 deletions(-)
diff --git a/include/trace/events/rseq.h b/include/trace/events/rseq.h
index 823b47d1ba1e..95f33d2c0714 100644
--- a/include/trace/events/rseq.h
+++ b/include/trace/events/rseq.h
@@ -18,16 +18,18 @@ TRACE_EVENT(rseq_update,
__field(s32, cpu_id)
__field(s32, node_id)
__field(s32, mm_cid)
+ __field(s32, mm_numa_cid)
),
TP_fast_assign(
__entry->cpu_id = raw_smp_processor_id();
__entry->node_id = cpu_to_node(__entry->cpu_id);
__entry->mm_cid = task_mm_cid(t);
+ __entry->mm_numa_cid = task_mm_numa_cid(t);
),
- TP_printk("cpu_id=%d node_id=%d mm_cid=%d", __entry->cpu_id,
- __entry->node_id, __entry->mm_cid)
+ TP_printk("cpu_id=%d node_id=%d mm_cid=%d mm_numa_cid=%d", __entry->cpu_id,
+ __entry->node_id, __entry->mm_cid, __entry->mm_numa_cid)
);
TRACE_EVENT(rseq_ip_fixup,
--
2.25.1
