On 28.05.25 07:35, Tal Zussman wrote:
When the TLB_REMOTE_WRONG_CPU enum was introduced for the tlb_flush
tracepoint, the enum was not exported to userspace. Add it to the
appropriate macro definition to enable parsing by userspace tools, as
per [0].
[0] Link: https://lore.kernel.org/all/[email protected]
Fixes: 2815a56e4b72 ("x86/mm/tlb: Add tracepoint for TLB flush IPI to stale
CPU")
Signed-off-by: Tal Zussman <[email protected]>
---
include/trace/events/tlb.h | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/include/trace/events/tlb.h b/include/trace/events/tlb.h
index b4d8e7dc38f8..725a75720a23 100644
--- a/include/trace/events/tlb.h
+++ b/include/trace/events/tlb.h
@@ -13,7 +13,8 @@
EM( TLB_REMOTE_SHOOTDOWN, "remote shootdown" ) \
EM( TLB_LOCAL_SHOOTDOWN, "local shootdown" ) \
EM( TLB_LOCAL_MM_SHOOTDOWN, "local mm shootdown" ) \
- EMe( TLB_REMOTE_SEND_IPI, "remote ipi send" )
+ EM( TLB_REMOTE_SEND_IPI, "remote ipi send" ) \
+ EMe( TLB_REMOTE_WRONG_CPU, "remote wrong CPU" )
Reviewed-by: David Hildenbrand <[email protected]>
--
Cheers,
David / dhildenb
