summaryrefslogtreecommitdiff
path: root/tools/perf/scripts/python
diff options
context:
space:
mode:
authorMichal Wajdeczko <michal.wajdeczko@intel.com>2026-08-14 19:17:37 +0200
committerRodrigo Vivi <rodrigo.vivi@intel.com>2026-08-14 14:55:36 -0400
commit4d3dd0c9464bd342506e075598b3db25c9ee75b3 (patch)
tree7a54e17afa751c91937d0e19e94379d47532b9df /tools/perf/scripts/python
parent9dae5c3b00f3f5e26e22d18156a1a10d8a783640 (diff)
downloadlinux-next-4d3dd0c9464bd342506e075598b3db25c9ee75b3.tar.gz
linux-next-4d3dd0c9464bd342506e075598b3db25c9ee75b3.zip
drm/xe/log: Index all SIGID printk messages
When CONFIG_PRINTK_INDEX is enabled, it is expected that all device level printk messages are indexed for audit. While usually this is done automatically behind the scenes when code is using regular dev_printk macros, since we are generating different dmesg messages inside xe_log_emit() based on the severity, component and location, we only get those entries in /sys/kernel/debug/printk/index/xe: <3> drivers/gpu/drm/xe/xe_log.c:142 log_dmesg_vprintk "%s %s: [drm] *ERROR* %pV" <6> drivers/gpu/drm/xe/xe_log.c:140 log_dmesg_vprintk "%s %s: [drm] %pV" Explicitly generate printk index using dev_printk_index_emit() with some generic prefix that includes the SIGID tag. Suggested-by: Jani Nikula <jani.nikula@intel.com> Signed-off-by: Michal Wajdeczko <michal.wajdeczko@intel.com> Cc: Jani Nikula <jani.nikula@intel.com> Cc: Rodrigo Vivi <rodrigo.vivi@intel.com> Reviewed-by: Mallesh Koujalagi <mallesh.koujalagi@intel.com> Link: https://patch.msgid.link/20260814171801.13347-12-michal.wajdeczko@intel.com Signed-off-by: Rodrigo Vivi <rodrigo.vivi@intel.com>
Diffstat (limited to 'tools/perf/scripts/python')
0 files changed, 0 insertions, 0 deletions