DRM.debug on DYNAMIC_DEBUG, add trace events
Subsystems (10)
Jim Cromie
maintainerv2 cover DRM.debug on DYNAMIC_DEBUG, add trace events
DRM.debug API is 23 macros, issuing 10 exclusive categories of debug messages. By rough count, they are used 5140 times in the kernel. These all call drm_dbg or drm_devdbg, which call drm_debug_enabled(), which checks bits in global __drm_debug. Some of these are page-flips and vblanks, and get called often.
DYNAMIC_DEBUG (with CONFIG_JUMP_LABEL) is built to avoid this kind of work, with NOOPd jump/callsites.
This patchset is RFC because:
- it touches 2.5 subsystems: dyndbg, drm, tracefs (new events)
- dyndbg class support is built for drm, needs it for validation
- new api, used by drm
- big memory impact, with 5100 new pr-debug callsites.
- drm class bikeshedding opportunities
- others, names etc.
DYNAMIC_DEBUG:
Adapt to directly represent 32 exclusive classes / categories. All existing users get _CLASS_DFLT:31, reserving 0-30 for opt-in.
dynamic_debug_register_classes(): Tells dyndbg that caller/client is using .class_id's 0..N, and wants them exposed and manipulatable with
names: DRM_UT_KMS etc.
Client invokes DYNAMIC_DEBUG_CLASSES to define the name->id map, then registers it during its initialization.
Then, when a dyndbg command-query has "class FOO":
echo class DRM_UT_KMS +p > /proc/dynamic_debug/control
ddebug_change() will 1st ddebug_validate_classname() for each module, using its registered class-maps; only modules which know DRM_UT_KMS will get those callsite adjustments. This "protects" each module's class-id space, unlike "class 4" query syntax.
Add bitmap support for:
echo 0x02 > /sys/module/drm/parameters/debug
Add symbolic bitmap, because we have the class-names:
echo +DRM_UT_KMS,+DRM_UT_ATOMIC > /sys/module/drm/parameters/debug
Add test_dynamic_debug, to prove out the API.
which is (used 3x to prove class-id ranges):
- DYNAMIC_DEBUG_CLASSES(var, ... [3 class-name-literals each])
- dynamic_debug_register_classes(var)
- dynamic_debug_unregister_classes(var)
also (6x):
+module_param_cb(<node-name>, ¶m_ops_dyndbg_classes, /[pt][123]_bitmap/, 0600);
Bits 0,1,2 of each of the 6 bitmaps control the 3 named classes in each of 3 groups, toggling their p,T bits respectively.
RFC:
dynamic_debug_register_classes() cannot act early enough to be in effect at module-load. So this will not work as you'd reasonably expect:
modprobe test_dynamic_debug dyndbg='+pfm; class FOO +pfmlt'
The 1st query:+pfm will be enabled during load, but in the 2nd query, "class FOO" will be unknown at load time. Early class enablement would be nice. DYNAMIC_DEBUG_CLASSES is a static initializer, which is certainly early enough, but Im missing a trick, suggestions?
Wildcarding on classname is possible, maybe useful:
echo +DRM_UT_\* > /sys/module/drm/parameters/debug
If contemplated in earnest, it should consider the difference between "DRM_*" and "*_KMS", wrt observing across class hierarchies, as well as decide whether that echo means 1st match, or all matching names.
__pr_debug_cls(cls, fmt,...) is just for testing, drm doesnt need it.
DRM adaptation:
Basically, these patches add another layer of macro indirection, which by CONFIG_DRM_USE_DYNAMIC_DEBUG=y, wraps drm_*dbg() in dyndbg's callsite Factory macro, and adds the new descriptor arg to the funcs.
With these patches, drm.debugs appear as controllable *pr-dbg* callsites:
[ 11.804352] dyndbg: register_classes: drm [ 11.920715] dyndbg: 234 debug prints in module drm_kms_helper [ 11.932135] dyndbg: 2 debug prints in module ttm [ 11.936119] dyndbg: 8 debug prints in module video [ 12.537543] dyndbg: 1756 debug prints in module i915 [ 12.555045] dyndbg: register_classes: i915 [ 12.666727] AMD-Vi: AMD IOMMUv2 functionality not available on this .. [ 13.735310] dyndbg: 3859 debug prints in module amdgpu
amdgpu's large count includes:
582 direct uses/mentions of pr_debug
43 defns of DC_LOG_*, which use either pr_debug or DRM_DEBUG_*
~1000 uses of DC_LOG_*
1116 uses of dml_print in drivers/gpu/drm/amd
15 drm_dbg_\\w+ drivers/gpu/drm/amd
273 DRM_DEBUG_\\w+ drivers/gpu/drm/amd i915 has:
1072 drm_dbg_\\w+ drivers/gpu/drm/i915/ | wc -l
200 DRM_DEBUG_\\w+ drivers/gpu/drm/i915/
46 pr_debug drivers/gpu/drm/i915/
144 gvt_dbg_\\w+ drivers/gpu/drm/i915/gvt, using pr_debugThis impacts the data footprint, so everything new/drm is dependent on DRM_USE_DYNAMIC_DEBUG=y.
RFC for DRM:
- decoration flags "fmlt" do not work on drm_*dbg().
(drm_*dbg() dont use pr_debug, they *become* one flavor of them) this could (should?) be added, and maybe tailored for drm.
some of the device prefixes are very long, a "d" flag could optionalize them.
- api use needs review wrt drm life-cycle.
enum drm_debug_category and DYNAMIC_DEBUG_CLASSES could be together?
- class-names could stand review, perhaps extension "drm:core:" etc have appeared (maybe just from me) or a "plan" to look at it later
- i915 & amdgpu have pr_debugs (DC_LOG_*, gvt_dbg_*) that have class-ish prefixes that are separate from, but similar to DRM_UT_*, and could stand review and possible unification with reformed or extended drm categories.
- the change to enum drm_debug_category from bitmask values to 0..31 means that we foreclose this possiblility:
drm_dbg(DRM_UT_CORE|DRM_UT_KMS, "wierd double-cat experiment");
- nouveau has very few drm.debug calls,
has NV_DEBUG, VMM_DEBUG, nvkm_printk_, I havent looked deeply.
DYNDBG/DRM -> TRACEFS
My 1st try was motivated by Sean Paul's patch - DRM.trace:
https://patchwork.freedesktop.org/patch/445549/?series=78133&rev=5
Those used trace_printk, so were not good for upstream.
Vincent Whitchurch's code:
https://lore.kernel.org/lkml/[email protected]/
added similar features, by sending printk:console events from dyndbg. It met with a good reception from Steve Rostedt, so I re-started with that.
The biggest addition (from UI viewpoint) is 4 new trace-events, 2 each from dyndbg (pr_debug, dev_dbg) and drm (drm_dbg, drm_dev_dbg); 2 have dev, other 2 avoid storing nulls. Im unsure that 4 distinctions is valuable, but it seemed most obvious to reflect them straight thru to tracefs.
RFC: the event/message formats are a bit of a mash-up;
in /sys/kernel/tracing:
drm/drm_debug/format:print fmt: "%s", __get_str(msg)
drm/drm_devdbg/format:print fmt: "cat:%d, %s %s", \ REC->drm_debug_category, dev_name(REC->dev), __get_str(msg)
The 1st prints just the mesg itself, 2nd prints category as int; it'd be better if DRM.class-name replaced (not just augmented) the event-name "drm_devdbg" in the trace, is that possible ?
dyndbg/prdbg/format:
print fmt: "%s.%s %s", REC->desc->modname, REC->desc->function, __get_str(msg) dyndbg/devdbg/format:
print fmt: "%s.%s %s", REC->desc->modname, REC->desc->function, __get_str(msg)
These add a prefix string similar to dyndbg's decorations, except they don't use dyndbg's "fmlt" decoration flags.
There are also 3 vblank trace-events already,
declared in: drivers/gpu/drm/drm_trace.h
15:TRACE_EVENT(drm_vblank_event,
35:TRACE_EVENT(drm_vblank_event_queued,
52:TRACE_EVENT(drm_vblank_event_delivered,
STATUS
kernel-test-robot tested this patchset (on 5.18-rc6). github:[jimc:blead] BUILD SUCCESS 6c59e52ac81dd81ac7da4522a5e15b7ac488d5b5 May 15, 2022, 8:39 AM (1 day ago)
Ive been testing, mostly on virtme, mostly with this:
#!/bin/bash
# test class FOO handling of dynamic-debug
alias lmt='modprobe test_dynamic_debug dyndbg=+pmf' alias rmt='rmmod test_dynamic_debug'
alias look='grep test_dynamic_debug /proc/dynamic_debug/control'
lookfor() {
grep $1 /proc/dynamic_debug/control
}
vx() {
echo $* > /sys/module/dynamic_debug/parameters/verbose
}
# amdgpu has ~2200 pr-debugs (before drm-debug-on-dyndbg), # use them to prove modprobe <mod> dyndbg=+p works
test_param_dyndbg() {
modprobe amdgpu dyndbg=+pfm
let count=$(grep =pmf /proc/dynamic_debug/control | grep amdgpu | wc -l)
if [ $count -gt 200 ] ; then
echo amdgpu has $count pr-dbgs
return 0
else
echo failed $count
return -1
fi
}
out=$(test_param_dyndbg)
echo out:$out $?
[ $? -eq 0 ] || exit $?
qry_cmd() {
echo "QCMD: $* >control" >&2
echo $* > /proc/dynamic_debug/control
}
# enable dyndbg tracing
dynable() {
grep -P \\d $SKT/events/dyndbg/{.,*}/enable
echo 1 > $SKT/events/dyndbg/enable
grep -P \\d $SKT/events/dyndbg/{.,*}/enable
}# enable drm tracing
drmable() {
grep -P \\d $SKT/events/drm/{.,*}/enable
echo 1 > $SKT/events/drm/enable
grep -P \\d $SKT/events/drm/{.,*}/enable
}function doit() {
cat /sys/module/test_dynamic_debug/parameters/do_prints
}
# test class FOO behavior of test_dynamic_debug module
ttest_module__() {
flg=$1
dmesg -C
modprobe test_dynamic_debug dyndbg=+pfm
doit for cls in FOO BAR BUZZ; do
qry_cmd module test_dynamic_debug class $cls $flg doit
done
doit
for cls in Foo Bar Buzz; do
qry_cmd module test_dynamic_debug class $cls $flg doit
done
doit
for cls in bing bong boom; do
qry_cmd module test_dynamic_debug class $cls $flg doit
done
doit
dmesg | grep class
}
ttest_module() {
ttest_module__ +p
ttest_module__ -p
#ttest_module__ +T
#ttest_module__ -T
}#dynable
#drmable
ttest_module
grep test_dyn /proc/dynamic_debug/control
# use/test bitmaps
set_tddm_() {
val=$1;
knob=$2;
echo "TDDM: $val >$knob" >&2
echo $val > /sys/module/test_dynamic_debug/parameters/$knob
cat /sys/module/test_dynamic_debug/parameters/$knob
}CLS_1="FOO -FOO +FOO -FOO BAR -BAR +BAR -BAR BUZZ -BUZZ +BUZZ -BUZZ" CLS_2=" Foo Bar Buzz -Foo -Bar -Buzz +Foo +Bar +Buzz -Foo -Bar -Buzz" CLS_3=" bing bong boom -bing -bong -boom +bing +bong +boom -bing -bong -boom"
tddm_sysnode_classes__() {
targ=$1
shift
cls=$*
for bitsym in $cls;
do
set_tddm_ $bitsym $targ
done
}# work all 3 sysfs bitmaps
for sysnode in c1_syslog_bits c2_syslog_bits c3_syslog_bits; do
for val in 0 1 2 4 8 0;
do
tddm_sysnode_classes__ $sysnode $val
done
done
tddm_sysnode_classes__ c1_syslog_bits $CLS_1tddm_sysnode_classes__ c2_syslog_bits $CLS_2tddm_sysnode_classes__ c3_syslog_bits $CLS_3
echo "show unknown: c3-names on c1-knob" >&2tddm_sysnode_classes__ c1_trace_bits $CLS_3
echo "flags look inverted" >&2tddm_sysnode_classes__ c1_syslog_bits $CLS_1
CLS_1_=FOO,-FOO,+FOO,-FOO,BAR,-BAR,+BAR,-BAR,BUZZ,-BUZZ,+BUZZ,-BUZZ CLS_2_=Foo,Bar,Buzz,-Foo,-Bar,-Buzz,+Foo,+Bar,+Buzz,-Foo,-Bar,-Buzz
# leading err doesnt wreck the rest CLS_3_=,bing,bong,boom,-bing,-bong,-boom,+bing,+bong,+boom,-bing,-bong,-boom
tddm_sysnode_classes__ c1_syslog_bits $CLS_1_tddm_sysnode_classes__ c2_syslog_bits $CLS_2_tddm_sysnode_classes__ c3_syslog_bits $CLS_3_
Jim Cromie (27):
dyndbg: fix static_branch manipulation
dyndbg: show both old and new in change-info
dyndbg: fix module.dyndbg handling
dyndbg: drop EXPORTed dynamic_debug_exec_queries
dyndbg: add exclusive class_id to pr_debug callsites
dyndbg: add dynamic_debug_(un)register_classes
dyndbg: validate class FOO on module
dyndbg: add drm.debug style bitmap support Doc/dyndbg: document new class class_name query support
dyndbg: let query-modname override defaulting modname
dyndbg: support symbolic class-names in bitmap
dyndbg: change zero-or-one classes-map to maps list
dyndbg: add __pr_debug_cls(class, fmt, ...)
dyndbg: add test_dynamic_debug module
drm: POC drm on dyndbg - map class-names to drm_debug_category's drm/print: POC drm on dyndbg - use bitmap
drm_print: condense enum drm_debug_category
drm_print: interpose drm_*dbg with forwarding macros
drm_print: wrap drm_*_dbg in dyndbg descriptor factory macro
drm_print: refine drm_debug_enabled for jump-label
drm_print: prefer bare printk KERN_DEBUG on generic fn
drm_print: add _ddebug desc to drm_*dbg prototypes
dyndbg: add _DPRINTK_FLAGS_ENABLED
dyndbg: add _DPRINTK_FLAGS_TRACE
dyndbg: add write-events-to-tracefs code
dyndbg: 4 new trace-events: pr_debug, dev_dbg, drm_{,dev}debug dyndbg/drm: POC add tracebits sysfs-knob
.../admin-guide/dynamic-debug-howto.rst | 12 + MAINTAINERS | 1 + drivers/gpu/drm/Kconfig | 12 + drivers/gpu/drm/Makefile | 2 + drivers/gpu/drm/amd/amdgpu/amdgpu_drv.c | 3 + drivers/gpu/drm/drm_drv.c | 5 + drivers/gpu/drm/drm_print.c | 69 ++- drivers/gpu/drm/i915/i915_module.c | 11 + drivers/gpu/drm/nouveau/nouveau_drm.c | 4 + include/drm/drm_drv.h | 26 + include/drm/drm_print.h | 84 ++- include/linux/dynamic_debug.h | 136 ++++- include/trace/events/drm.h | 68 +++ include/trace/events/dyndbg.h | 74 +++ lib/Kconfig.debug | 11 + lib/Makefile | 1 + lib/dynamic_debug.c | 487 +++++++++++++++--- lib/test_dynamic_debug.c | 172 +++++++ 18 files changed, 1049 insertions(+), 129 deletions(-) create mode 100644 include/trace/events/drm.h create mode 100644 include/trace/events/dyndbg.h create mode 100644 lib/test_dynamic_debug.c
Signature · 1 line
2.35.1
Jim Cromie
maintainerPATCH v2 1/27 dyndbg: fix static_branch manipulation
In https://lore.kernel.org/lkml/[email protected]/
Vincent's patch commented on, and worked around, a bug toggling static_branch's, when a 2nd PRINTK-ish flag was added. The bug results in a premature static_branch_disable when the 1st of 2 flags was disabled.
The cited commit computed newflags, but then in the JUMP_LABEL block, failed to use that result, instead using just one of the terms in it. Using newflags instead made the code work properly.
This is Vincents test-case, reduced. It needs the 2nd flag to demonstrate the bug, but it's explanatory here.
pt_test() {
echo 5 > /sys/module/dynamic_debug/verbose
site="module tcp" # just one callsite
echo " $site =_ " > /proc/dynamic_debug/control # clear it
# A B ~A ~B
for flg in +T +p "-T #broke here" -p; do
echo " $site $flg " > /proc/dynamic_debug/control
done;
# A B ~B ~A
for flg in +T +p "-p #broke here" -T; do
echo " $site $flg " > /proc/dynamic_debug/control
done
}pt_test
---
.drop @stable, no exposed bug.
.add jbaron ack
--- lib/dynamic_debug.c | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-)
lib/dynamic_debug.c +3 -2
@@ -211,10 +211,11 @@ static int ddebug_change(const struct ddebug_query *query,continue ;#ifdef CONFIG_JUMP_LABEL if (dp->flags & _DPRINTK_FLAGS_PRINT) { -if (!(modifiers->flags & _DPRINTK_FLAGS_PRINT)) +if (!(newflags & _DPRINTK_FLAGS_PRINT))static_branch_disable (&dp->key.dd_key_true); - }else if (modifiers->flags & _DPRINTK_FLAGS_PRINT) + }else if (newflags & _DPRINTK_FLAGS_PRINT) {static_branch_enable (&dp->key.dd_key_true); + }#endif dp->flags = newflags; v4pr_info("changed %s:%d [%s]%s =%s\n",
Signature · 1 line
2.35.3
Jim Cromie
maintainerPATCH v2 2/27 dyndbg: show both old and new in change-info
In reply to Jim Cromieprint "old -> new" flag values in the info("change") message.
no functional change.
--- lib/dynamic_debug.c | 11 ++++++----- 1 file changed, 6 insertions(+), 5 deletions(-)
lib/dynamic_debug.c +6 -5
@@ -156,7 +156,7 @@ static int ddebug_change(const struct ddebug_query *query,struct ddebug_table *dt;unsigned int newflags;unsigned int nfound =0 ; -struct flagsbuf fbuf; +struct flagsbuf fbuf, nbuf;/* search for matching ddebugs */ mutex_lock (&ddebug_lock);
@@ -217,11 +217,12 @@ static int ddebug_change(const struct ddebug_query *query, static_branch_enable(&dp->key.dd_key_true); }#endif +v4pr_info ("changed %s:%d [%s]%s %s -> %s\n" , +trim_prefix (dp->filename), dp->lineno, + dt->mod_name, dp->function, +ddebug_describe_flags (dp->flags, &fbuf), +ddebug_describe_flags (newflags, &nbuf)); dp->flags = newflags; -v4pr_info ("changed %s:%d [%s]%s =%s\n" , -trim_prefix (dp->filename), dp->lineno, - dt->mod_name, dp->function, -ddebug_describe_flags (dp->flags, &fbuf)); } }mutex_unlock (&ddebug_lock);
Signature · 1 line
2.35.3
Jim Cromie
maintainerPATCH v2 3/27 dyndbg: fix module.dyndbg handling
In reply to Jim CromieFor CONFIG_DYNAMIC_DEBUG=N, the ddebug_dyndbg_module_param_cb() stub-fn is too permissive:
bash-5.1# modprobe drm JUNKdyndbg
bash-5.1# modprobe drm dyndbgJUNK
[ 42.933220] dyndbg param is supported only in CONFIG_DYNAMIC_DEBUG builds [ 42.937484] ACPI: bus type drm_connector registered
This caused no ill effects, because unknown parameters are either ignored by default (with an "unknown parameter" warning, see below), or ignored because dyndbg allows its no-effect use on non-dyndbg builds.
That said, the code has an explicit feedback message, which should be issued accurately. Fix with strcmp, for exact param-name match.
Here is fixed behavior:
bash-5.1# modprobe drm dyndbgJUNK
[ 20.127473] drm: unknown parameter 'dyndbgJUNK' ignored [ 20.128835] ACPI: bus type drm_connector registered bash-5.1# rmmod drm [ 37.961656] ACPI: bus type drm_connector unregistered bash-5.1# modprobe drm dyndbg [ 42.933220] dyndbg param is supported only in CONFIG_DYNAMIC_DEBUG builds [ 42.937484] ACPI: bus type drm_connector registered
--- include/linux/dynamic_debug.h | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
include/linux/dynamic_debug.h +1 -1
@@ -201,7 +201,7 @@ static inline int ddebug_remove_module(const char *mod)static inline int ddebug_dyndbg_module_param_cb (char *param,char *val,const char *modname) { -if (strstr (param,"dyndbg" )) { +if (!strcmp (param,"dyndbg" )) {/* avoid pr_warn(), which wants pr_fmt() fully defined */ printk (KERN_WARNING "dyndbg param is supported only in " "CONFIG_DYNAMIC_DEBUG builds\n" );
Signature · 1 line
2.35.3
Jim Cromie
maintainerPATCH v2 4/27 dyndbg: drop EXPORTed dynamic_debug_exec_queries
In reply to Jim CromieThis exported fn is unused, and is effectively obsoleted by a forthcoming commit, so remove it.
The export was added to let drm control pr_debugs, as part of using them to avoid drm_debug_enabled overheads. But following patches implement the drm.debug interface, and adapt drm to just use it, so nobody will never need the export.
This also drops the CONFIG_DYNAMIC_DEBUG=N stub-func, and its pr_warn(), which I avoided in 2012, then added in 2020 :-/
--- include/linux/dynamic_debug.h | 8 -------- lib/dynamic_debug.c | 29 ----------------------------- 2 files changed, 37 deletions(-)
include/linux/dynamic_debug.h +0 -8
@@ -55,9 +55,6 @@ struct _ddebug {#if defined(CONFIG_DYNAMIC_DEBUG_CORE ) -/* exported for module authors to exercise >control */ -int dynamic_debug_exec_queries (const char *query,const char *modname); -int ddebug_add_module (struct _ddebug *tab,unsigned int n,const char *modname);extern int ddebug_remove_module (const char *mod_name);
@@ -221,11 +218,6 @@ static inline int ddebug_dyndbg_module_param_cb(char *param, char *val, rowsize, groupsize, buf, len, ascii); \ } while (0) -static inline int dynamic_debug_exec_queries(const char *query, const char *modname) -{ -pr_warn ("kernel not built with CONFIG_DYNAMIC_DEBUG_CORE\n" ); -return 0 ; -}#endif /* !CONFIG_DYNAMIC_DEBUG_CORE */
lib/dynamic_debug.c +0 -29
@@ -555,35 +555,6 @@ static int ddebug_exec_queries(char *query, const char *modname)return nfound; } -/** -* dynamic_debug_exec_queries - select and change dynamic-debug prints -* @query: query-string described in admin-guide/dynamic-debug-howto -* @modname: string containing module name, usually &module.mod_name -* -* This uses the >/proc/dynamic_debug/control reader, allowing module -* authors to modify their dynamic-debug callsites. The modname is -* canonically struct module.mod_name, but can also be null or a -* module-wildcard, for example: "drm*". -*/ -int dynamic_debug_exec_queries (const char *query,const char *modname) -{ -int rc; -char *qry;/* writable copy of query */ - -if (!query) { -pr_err ("non-null query/command string expected\n" ); -return -EINVAL ; - } - qry =kstrndup (query,PAGE_SIZE ,GFP_KERNEL ); -if (!qry) -return -ENOMEM ; - - rc =ddebug_exec_queries (qry, modname); -kfree (qry); -return rc; -} -EXPORT_SYMBOL_GPL (dynamic_debug_exec_queries); -#define PREFIX_SIZE 64static int remaining (int wrote)
Signature · 1 line
2.35.3
Jim Cromie
maintainerPATCH v2 5/27 dyndbg: add exclusive class_id to pr_debug callsites
In reply to Jim CromieDRM issues ~10 exclusive categories of debug messages; to represent this directly in dyndbg, add a new field: struct _ddebug.class_id:5.
We only need 4 bits for drm, and with that reserved, we have 2 to spare on 32 bit builds; lets take one extra (5 bits total), and keep a spare bit. 32 classes-per-bitmap is a practical usability limit anyway with a bitmap interface:
#> echo 0x012345678 > /sys/module/drm/parameters/debug
All existing callsites are initialized with _DPRINTK_CLASS_DFLT, which is 2^5-1. This reserves 0-30 for use in new categorized/class'd pr_debugs, which fits perfectly with natural enums (ints: 0..N).
To achieve this, DEFINE_DYNAMIC_DEBUG_METADATA_CLS(cls,...) is added, and DEFINE_DYNAMIC_DEBUG_METADATA is altered to call it with the default. The factory macro chain between there and pr_debug is adjusted similarly.
No behavior change.
--- include/linux/dynamic_debug.h | 54 ++++++++++++++++++++++++++--------- 1 file changed, 41 insertions(+), 13 deletions(-)
include/linux/dynamic_debug.h +41 -13
@@ -6,6 +6,8 @@#include <linux/jump_label.h> #endif +#include <linux/build_bug.h> +/* * An instance of this structure is created in a special * ELF section at every dynamic debug callsite. At runtime,
@@ -21,6 +23,9 @@ struct _ddebug {const char *filename;const char *format; unsigned int lineno:18; +#define CLS_BITS 5 + unsigned int class_id:CLS_BITS; +#define _DPRINTK_CLASS_DFLT ((1 << CLS_BITS) - 1)/* * The flags field controls the behaviour at the callsite. * The bits here are changed dynamically when the user
@@ -84,7 +89,7 @@ void __dynamic_ibdev_dbg(struct _ddebug *descriptor,const struct ib_device *ibdev, const char *fmt, ...); -#define DEFINE_DYNAMIC_DEBUG_METADATA (name, fmt) \ +#define DEFINE_DYNAMIC_DEBUG_METADATA_CLS (name, cls, fmt) \ static struct _ddebug __aligned(8) \ __section("__dyndbg") name = { \ .modname = KBUILD_MODNAME, \
@@ -93,8 +98,14 @@ void __dynamic_ibdev_dbg(struct _ddebug *descriptor, .format = (fmt), \ .lineno = __LINE__, \ .flags = _DPRINTK_FLAGS_DEFAULT, \ + .class_id = cls, \ _DPRINTK_KEY_INIT \ - } + }; \ +BUILD_BUG_ON_MSG (cls > _DPRINTK_CLASS_DFLT, \ + "classid value overflow") + +#define DEFINE_DYNAMIC_DEBUG_METADATA (name, fmt) \ + DEFINE_DYNAMIC_DEBUG_METADATA_CLS(name, _DPRINTK_CLASS_DFLT, fmt)#ifdef CONFIG_JUMP_LABEL
@@ -125,18 +136,26 @@ void __dynamic_ibdev_dbg(struct _ddebug *descriptor,#endif /* CONFIG_JUMP_LABEL */ -#define __dynamic_func_call (id, fmt, func, ...) do { \ - DEFINE_DYNAMIC_DEBUG_METADATA(id, fmt); \ - if (DYNAMIC_DEBUG_BRANCH(id)) \ - func(&id, ##__VA_ARGS__); \ +#define __dynamic_func_call_cls (id, cls, fmt, func, ...) do { \ + DEFINE_DYNAMIC_DEBUG_METADATA_CLS(id, cls, fmt); \ + if (DYNAMIC_DEBUG_BRANCH(id)) \ + func(&id, ##__VA_ARGS__); \ } while (0) -#define __dynamic_func_call_no_desc (id, fmt, func, ...) do { \ - DEFINE_DYNAMIC_DEBUG_METADATA(id, fmt); \ - if (DYNAMIC_DEBUG_BRANCH(id)) \ - func(__VA_ARGS__); \ +#define __dynamic_func_call_no_desc_cls (id, cls, fmt, func, ...) do { \ + DEFINE_DYNAMIC_DEBUG_METADATA_CLS(id, cls, fmt); \ + if (DYNAMIC_DEBUG_BRANCH(id)) \ + func(__VA_ARGS__); \ } while (0) +#define __dynamic_func_call (id, fmt, func, ...) \ + __dynamic_func_call_cls(id, _DPRINTK_CLASS_DFLT, \ + fmt, func, ##__VA_ARGS__) + +#define __dynamic_func_call_no_desc (id, fmt, func, ...) \ + __dynamic_func_call_no_desc_cls(id, _DPRINTK_CLASS_DFLT, \ + fmt, func, ##__VA_ARGS__) +/* * "Factory macro" for generating a call to func, guarded by a * DYNAMIC_DEBUG_BRANCH. The dynamic debug descriptor will be
@@ -145,15 +164,24 @@ void __dynamic_ibdev_dbg(struct _ddebug *descriptor,* the varargs. Note that fmt is repeated in invocations of this * macro. */ +#define _dynamic_func_call_cls (cls, fmt, func, ...) \ + __dynamic_func_call_cls(__UNIQUE_ID(ddebug), cls, fmt, func, ##__VA_ARGS__)#define _dynamic_func_call (fmt, func, ...) \ - __dynamic_func_call(__UNIQUE_ID(ddebug), fmt, func, ##__VA_ARGS__) + _dynamic_func_call_cls(_DPRINTK_CLASS_DFLT, fmt, func, ##__VA_ARGS__) +/* * A variant that does the same, except that the descriptor is not * passed as the first argument to the function; it is only called * with precisely the macro's varargs. */ -#define _dynamic_func_call_no_desc (fmt, func, ...) \ - __dynamic_func_call_no_desc(__UNIQUE_ID(ddebug), fmt, func, ##__VA_ARGS__) +#define _dynamic_func_call_no_desc_cls (fmt, cat, func, ...) \ + __dynamic_func_call_no_desc_cls(__UNIQUE_ID(ddebug), cat, \ + fmt, func, ##__VA_ARGS__) + +#define _dynamic_func_call_no_desc (fmt, func, ...) \ + __dynamic_func_call_no_desc_cls(__UNIQUE_ID(ddebug), \ + _DPRINTK_CLASS_DFLT, \ + fmt, func, ##__VA_ARGS__)#define dynamic_pr_debug (fmt, ...) \ _dynamic_func_call(fmt, __dynamic_pr_debug, \
Signature · 1 line
2.35.3
Jim Cromie
maintainerPATCH v2 6/27 dyndbg: add dynamic_debug_(un)register_classes
In reply to Jim CromieAdd dynamic_debug_register_classes() to API, allowing user modules (builtin and loadable) to register class_names for the .class_id's they are using. Knowing classes is 1st step to validating with them. Add dynamic_debug_unregister_classes() also.
Add struct ddebug_known_classes_map: maps known class_name strings to .class_id[0..N], where N<31. .base allows sharing of that range.
A wrapper macro: DYNAMIC_DEBUG_CLASSES(_var, _modmatch, _base, classes) defines and initializes that struct var, _maybe_unused is added so the decl doesn't draw warnings when dyndbg is not enabled; a small list of classnames is tolerable wasted space.
_var: user passes this into dynamic_debug_register_classes(var).
_base: usually 0, it allows splitting 31 classes into subranges, so that multiple sysfs-nodes can share the module's class-id space.
classes: list of strings with classnames, mapped to class-id=idx(+_base)
mod_name: KBUILD_MODNAME, available for builtins, loadables
mod: ref to loadable module. allows ==, distinguishing loadables.
When modules register known classnames, they opt-in to permit dyndbg to allow "class <name>" queries to manipulate their class'd pr_debugs (if any), default class_id pr_debugs are still controllable as before.
dynamic_debug_register_classes(&map) finds the module's ddebug_table record, and attaches the map to it. This makes it available to ddebug_change(), which will use it to validate class'd commands.
Sharing class-names across multiple modules is how those modules coordinate; all drm* and drivers would respond to:
#> echo class DRM_UT_CORE +p > /proc/dynamic_debug/control
Therefore no class-name uniqueness check is useful.
TODO: Eventually we need a list of registered classes, not just the zero-or-one implemented here. This will support multiple sysfs-nodes, one each for print-to-syslog, print-to-tracefs, or subranges using _base.
---
. fix register_classes() for !CONFIG_MODULES
. add maybe-unused to var decl in DYNAMIC_DEBUG_CLASSES . kdoc for DYNAMIC_DEBUG_CLASSES
. add dynamic_debug_unregister_classes
--- include/linux/dynamic_debug.h | 36 ++++++++++++++++++++++++ lib/dynamic_debug.c | 53 +++++++++++++++++++++++++++++++++++ 2 files changed, 89 insertions(+)
include/linux/dynamic_debug.h +36 -0
@@ -56,6 +56,34 @@ struct _ddebug {#endif } __attribute__((aligned(8))); +struct ddebug_known_classes_map { +struct list_head link; +struct module *mod; +const char *mod_name;/* needed for builtins */ +const int base;/* index of 1st .class_id, allows split/shared space */ +const int length; +const char *classes[];/* index maps .class_id */ +}; + +#define NUM_TYPE_ARGS (eltype, ...) \ + (sizeof((eltype[]) {__VA_ARGS__}) / sizeof(eltype)) +/** +* DYNAMIC_DEBUG_CLASSES - declare classnames known by a module +* @_var: passed to dynamic_debug_register_classes(_var) +* @_base: offset of 1st class-name. splits .class_id space +* @classes: class-names known/used by of .class_ids[_base.._base+length] +* +* @classes specifies names for the classids used by a module; dyndbg +* accepts "class <name>" commands if <name> is known and registered. +*/ +#define DYNAMIC_DEBUG_CLASSES (_var, _base, ...) \ + static __maybe_unused struct ddebug_known_classes_map _var = { \ + .mod = THIS_MODULE, \ + .mod_name = KBUILD_MODNAME, \ + .base = _base, \ + .length = NUM_TYPE_ARGS(char*, __VA_ARGS__), \ + .classes = { __VA_ARGS__ } \ + }#if defined(CONFIG_DYNAMIC_DEBUG_CORE )
@@ -206,6 +234,9 @@ void __dynamic_ibdev_dbg(struct _ddebug *descriptor, KERN_DEBUG, prefix_str, prefix_type, \ rowsize, groupsize, buf, len, ascii) +int dynamic_debug_register_classes (struct ddebug_known_classes_map *map); +void dynamic_debug_unregister_classes (struct ddebug_known_classes_map *map); +#else /* !CONFIG_DYNAMIC_DEBUG_CORE */ #include <linux/string.h>
@@ -247,6 +278,11 @@ static inline int ddebug_dyndbg_module_param_cb(char *param, char *val, } while (0) +static inline int dynamic_debug_register_classes(const struct ddebug_known_classes_map *map) +{return 0 ; } +static inline void dynamic_debug_unregister_classes (struct ddebug_known_classes_map *map) +{} +#endif /* !CONFIG_DYNAMIC_DEBUG_CORE */ #endif
lib/dynamic_debug.c +53 -0
65 lines not on this page · raw message
Signature · 1 line
2.35.3
Jim Cromie
maintainerPATCH v2 7/27 dyndbg: validate class FOO on module
In reply to Jim CromieAdd module-to-class validation, in
#> echo class DRM_UT_KMS +p > /proc/dynamic_debug/control
If a query has "class FOO", ddebug_validate_classname (called from ddebug_change) requires that FOO is known to module X, otherwize X is skipped entirely.
The choice of FOO is highly selective, giving isolation and/or coordinated sharing of FOOs. For example, only DRM modules should know and respond to DRM_UT_KMS.
So this, combined with module's opt-in declaration of known classes, effectively privatizes the .class_id space for each module (or coordinated set of modules).
Ignoring a bad query, with dynamic_debug.verbose=3:
(lots of modules will not know other module's classes)
bash-5.1# echo module drm class FOO +p > /proc/dynamic_debug/control
[ 54.507983] dyndbg: read 24 bytes from userspace [ 54.509549] dyndbg: query 0: "module drm class FOO +p" mod:* [ 54.511502] dyndbg: split into words: "module" "drm" "class" "FOO" "+p" [ 54.513672] dyndbg: op='+' [ 54.514575] dyndbg: flags=0x1 [ 54.515547] dyndbg: *flagsp=0x1 *maskp=0xffffffff [ 54.517112] dyndbg: parsed: func="" file="" module="drm" format="" lineno=0-0 class=FOO [ 54.519707] dyndbg: class: drm.FOO unknown [ 54.521302] dyndbg: no matches for query [ 54.522581] dyndbg: no-match: func="" file="" module="drm" format="" lineno=0-0 class=FOO [ 54.525236] dyndbg: processed 1 queries, with 0 matches, 0 errs
Also add a new column to control-file output, displaying the class-name when its not default. If a module has pr_debugs with non-default .class_id's, and has not registered them, "<unregistered>" is issued.
---
. split out validate_classnames()
--- lib/dynamic_debug.c | 70 +++++++++++++++++++++++++++++++++++++++------ 1 file changed, 62 insertions(+), 8 deletions(-)
lib/dynamic_debug.c +62 -8
@@ -56,6 +56,7 @@ struct ddebug_query {const char *module;const char *function;const char *format; +const char *class_string;unsigned int first_lineno, last_lineno; };
@@ -136,13 +137,40 @@ static void vpr_info_dq(const struct ddebug_query *query, const char *msg) fmtlen--; } -v3pr_info ("%s: func=\"%s\" file=\"%s\" module=\"%s\" format=\"%.*s\" lineno=%u-%u\n" , - msg, - query->function ?:"" , - query->filename ?:"" , - query->module ?:"" , - fmtlen, query->format ?:"" , - query->first_lineno, query->last_lineno); +v3pr_info ("%s: func=\"%s\" file=\"%s\" module=\"%s\" format=\"%.*s\" lineno=%u-%u class=%s\n" , + msg, + query->function ?:"" , + query->filename ?:"" , + query->module ?:"" , + fmtlen, query->format ?:"" , + query->first_lineno, query->last_lineno, query->class_string); +} + +/* return <0 if class-name is unknown/invalid, 0..CLASS_DFLT otherwise */ +static int ddebug_validate_classname (struct ddebug_table *dt,const char *class_string) +{ +int query_class = -ENOENT ; +int idx; + +if (!class_string) +/* all queries w/o class given work only on default class */ +return _DPRINTK_CLASS_DFLT; + +/* +* XXX single list will need to be a for-list +* so that modules can have 2 sets of class-decls +*/ +if (!dt->map) +return -ENOENT ; + + idx =match_string (dt->map->classes, dt->map->length, class_string); +if (idx <0 ) { +v3pr_info ("class: %s.%s unknown\n" , dt->mod_name, class_string); +return -ENOENT ; + } + query_class = idx + dt->map->base; + +return query_class; }/*
@@ -159,6 +187,7 @@ static int ddebug_change(const struct ddebug_query *query,unsigned int newflags;unsigned int nfound =0 ;struct flagsbuf fbuf, nbuf; +int query_class;/* search for matching ddebugs */ mutex_lock (&ddebug_lock);
@@ -169,9 +198,18 @@ static int ddebug_change(const struct ddebug_query *query, !match_wildcard(query->module, dt->mod_name)) continue; +/* validate class-string against module's known classes */ + query_class =ddebug_validate_classname (dt, query->class_string); +if (query_class <0 ) +continue ; +for (i =0 ; i < dt->num_ddebugs; i++) {struct _ddebug *dp = &dt->ddebugs[i]; +/* match against query-class, either valid input or default */ +if (query_class != dp->class_id) +continue ; +/* match against the source filename */ if (query->filename && !match_wildcard(query->filename, dp->filename) &&
@@ -424,6 +462,8 @@ static int ddebug_parse_query(char *words[], int nwords, }else if (!strcmp (keyword,"line" )) {if (parse_linerange (query, arg))return -EINVAL ; + }else if (!strcmp (keyword,"class" )) { + rc =check_set (&query->class_string, arg,"class" ); }else {pr_err ("unknown keyword \"%s\"\n" , keyword);return -EINVAL ;
@@ -851,6 +891,13 @@ static void *ddebug_proc_next(struct seq_file *m, void *p, loff_t *pos)return dp; } +static const char *ddebug_class_name (struct ddebug_iter *iter,struct _ddebug *dp) +{ +if (iter->table->map) +return iter->table->map->classes[dp->class_id]; +return NULL ; +} +/* * Seq_ops show method. Called several times within a read() * call from userspace, with ddebug_lock held. Formats the
@@ -862,6 +909,7 @@ static int ddebug_proc_show(struct seq_file *m, void *p)struct ddebug_iter *iter = m->private;struct _ddebug *dp = p;struct flagsbuf flags; +char const *class;if (p ==SEQ_START_TOKEN ) { seq_puts(m,
@@ -874,7 +922,13 @@ static int ddebug_proc_show(struct seq_file *m, void *p) iter->table->mod_name, dp->function, ddebug_describe_flags(dp->flags, &flags));seq_escape (m, dp->format,"\t\r\n\"" ); -seq_puts (m,"\"\n" ); +seq_puts (m,"\"" ); + +if (dp->class_id != _DPRINTK_CLASS_DFLT) { + class =ddebug_class_name (iter, dp); +seq_printf (m," class:%s" , class ?:"<unregistered>" ); + } +seq_puts (m,"\n" );return 0 ; }
Signature · 1 line
2.35.3
Jim Cromie
maintainerPATCH v2 8/27 dyndbg: add drm.debug style bitmap support
In reply to Jim CromieAdd kernel_param_ops and callbacks to implement a bitmap in a sysfs-node. IE, add these:
- int param_set_dyndbg_classes()
- int param_get_dyndbg_classes()
- struct kernel_param_ops param_ops_dyndbg_classes
Following the model of kernel/params.c STANDARD_PARAM_DEFS, these are non-static and exported.
get/set use an augmented kernel_param; the arg refs a new struct dyndbg_classes_param, initialized by the macro, containing:
BITS: a pointer to the user module's ulong holding the bits/state. By ref'g the client's bit-state, we coordinate with existing code that uses it, so it works unchanged; for example drm_debug_enabled(). The change to ulong allows use of BIT() etc.
FLAGS: dyndbg.flags toggled by bit-changes. Usually just "p".
MAP: a pointer to struct ddebug_known_classes, which maps those class-names to pr_debug.class_ids 0..N.
Using the sys-node, with dynamic_debug.verbose=1:
bash-5.1# echo 1 > /sys/module/drm/parameters/debug
[ 29.821298] dyndbg: set_dyndbg_classes: new 0x1 current 0x0 [ 29.822841] dyndbg: query 0: "class DRM_UT_CORE +p" mod:* [ 29.824348] dyndbg: no matches for query [ 29.825428] dyndbg: total matches: 0
--- include/linux/dynamic_debug.h | 17 ++++++++ lib/dynamic_debug.c | 81 +++++++++++++++++++++++++++++++++++ 2 files changed, 98 insertions(+)
include/linux/dynamic_debug.h +17 -0
@@ -85,6 +85,11 @@ struct ddebug_known_classes_map { .classes = { __VA_ARGS__ } \ } +struct ddebug_classes_bitmap_param { +unsigned long *bits; +char flags[8 ]; +const struct ddebug_known_classes_map *map; +};#if defined(CONFIG_DYNAMIC_DEBUG_CORE )
@@ -237,6 +242,10 @@ void __dynamic_ibdev_dbg(struct _ddebug *descriptor,int dynamic_debug_register_classes (struct ddebug_known_classes_map *map);void dynamic_debug_unregister_classes (struct ddebug_known_classes_map *map); +struct kernel_param ; +int param_set_dyndbg_classes (const char *instr,const struct kernel_param *kp); +int param_get_dyndbg_classes (char *buffer,const struct kernel_param *kp); +#else /* !CONFIG_DYNAMIC_DEBUG_CORE */ #include <linux/string.h>
@@ -283,6 +292,14 @@ static inline int dynamic_debug_register_classes(const struct ddebug_known_classstatic inline void dynamic_debug_unregister_classes (struct ddebug_known_classes_map *map) {} +struct kernel_param ; +static inline int param_set_dyndbg_classes (const char *instr,const struct kernel_param *kp) +{return 0 ; } +static inline int param_get_dyndbg_classes (char *buffer,const struct kernel_param *kp) +{return 0 ; } +#endif /* !CONFIG_DYNAMIC_DEBUG_CORE */ +extern const struct kernel_param_ops param_ops_dyndbg_classes; +#endif
lib/dynamic_debug.c +81 -0
87 lines not on this page · raw message
Signature · 1 line
2.35.3
Jim Cromie
maintainerPATCH v2 9/27 Doc/dyndbg: document new class class_name query support
In reply to Jim CromieThe added paragraph is slightly process oriented, rather than in language of guarantees; I thought the implications were clear enough.
It does perhaps undersell the selectivity gained with string class_names; only drm/* would sanely register DRM_UT_CORE etc, so doing multiple "module {drm*,amdgpu,i915}" queries is unnecessary.
--- Documentation/admin-guide/dynamic-debug-howto.rst | 11 +++++++++++ 1 file changed, 11 insertions(+)
Documentation/admin-guide/dynamic-debug-howto.rst +11 -0
@@ -35,6 +35,7 @@ Dynamic debug has even more useful features: - line number (including ranges of line numbers) - module name - format string + - class string (as known by each module) * Provides a debugfs control file: ``<debugfs>/dynamic_debug/control`` which can be read to display the complete list of known debug
@@ -142,6 +143,7 @@ against. Possible keywords are::: 'file' string | 'module' string | 'format' string | + 'class' string | 'line' line-range line-range ::= lineno |
@@ -203,6 +205,15 @@ format format "nfsd: SETATTR" // a neater way to match a format with whitespace format 'nfsd: SETATTR' // yet another way to match a format with whitespace +class + The given class_name is validated against each module, which may + have registered a list of known class_names. If the class_name is + found for a module, callsite matching and adjustment proceeds. + Examples:: + + class DRM_UT_KMS # unless DRM wants different + class JUNK # silent non-match + line The given line number or range of line numbers is compared against the line number of each ``pr_debug()`` callsite. A single
Signature · 1 line
2.35.3
Jim Cromie
maintainerPATCH v2 10/27 dyndbg: let query-modname override defaulting modname
In reply to Jim Cromiedyndbg's control-parser: ddebug_parse_query(), requires that search
terms: module, func, file, lineno, are not used 2x in a query; a thing cannot be named both foo and bar (not even wildcards, no OR is contemplated).
Amend the treatment of module; while still enforcing the 2x rule on it, set the default module at end, if none was given in the query itself, so the preset doesn't spoil the check.
Background:
ddebug_parse_query() got a modname arg to support boot-args with compound queries, all with "module aMod" added by default.
aMod.dyndbg="func foo +p; func bar +p"
With default module at end, this becomes possible; "module *" in the query overrides the default "module aMod".
aMod.dyndbg="module * class FOO +p"
This means aMod can modify (by explicit means) any FOO class'd pr_debugs in other modules. It is intended for use by DRM, which generally would want sub-system wide coordination.
--- lib/dynamic_debug.c | 11 +++++++---- 1 file changed, 7 insertions(+), 4 deletions(-)
lib/dynamic_debug.c +7 -4
@@ -425,10 +425,6 @@ static int ddebug_parse_query(char *words[], int nwords,return -EINVAL ; } -if (modname) -/* support $modname.dyndbg=<multiple queries> */ - query->module = modname; -for (i =0 ; i < nwords; i +=2 ) {char *keyword = words[i];char *arg = words[i+1 ];
@@ -471,6 +467,13 @@ static int ddebug_parse_query(char *words[], int nwords,if (rc)return rc; } +if (!query->module && modname) +/* +* support $modname.dyndbg=<multiple queries>, +* allowing query.module to override $modname +*/ + query->module = modname; +vpr_info_dq (query,"parsed" );return 0 ; }
Signature · 1 line
2.35.3
Jim Cromie
maintainerPATCH v2 11/27 dyndbg: support symbolic class-names in bitmap
In reply to Jim CromieExtend the sysfs-node bitmap support to accept class-names registered by the module, allowing:
#> echo DRM_UT_CORE,-DRM_UT_ATOMIC,+DRM_UT_KMS \
> /sys/module/drm/parameters/debugDo this in param_set_dyndbg_class_strings(), which is called from param_set_dyndbg_classes() when the input string isn't a integer.
---
. continue/skip on unknown class, so following symbols are processed. . better loadable module handling, no more KP_MOD_NAME
. add do_callback_changes
--- lib/dynamic_debug.c | 63 ++++++++++++++++++++++++++++++++++++++++++--- 1 file changed, 59 insertions(+), 4 deletions(-)
lib/dynamic_debug.c +59 -4
@@ -618,6 +618,61 @@ static int do_callback_changes(const struct ddebug_classes_bitmap_param *dcp,return matches; } +/* support for [+-] symbolic-name boolean list */ +static int param_set_dyndbg_class_strings (const char *instr,const struct kernel_param *kp) +{ +const struct ddebug_classes_bitmap_param *dcp = kp->arg; +unsigned long inbits; +int idx_rc, totct =0 ; +bool wanted; +char *cls, *p; + +if (!dcp || !dcp->map) { +pr_err ("set_dyndbg_classes: no bits=>queries map\n" ); +return -EINVAL ; + } + + cls =kstrdup (instr,GFP_KERNEL ); + p =strchr (cls,'\n' ); +if (p) + *p ='\0' ; + + inbits = *dcp->bits; +vpr_info ("set_dyndbg_class_strings: %s on 0x%lx\n" , cls, inbits); + +for (; cls; cls = p) { + p =strchr (cls,',' ); +if (p) + *p++ ='\0' ; + +if (*cls =='-' ) { + wanted = false; + cls++; + }else { + wanted = true; +if (*cls =='+' ) + cls++; + } + idx_rc =match_string (dcp->map->classes, dcp->map->length, cls); +if (idx_rc <0 ) { +pr_err ("%s not found for module: %s\n" , cls, dcp->map->mod_name); +continue ; + } +if (test_bit (idx_rc, &inbits) == wanted) { +v3pr_info ("no change on %s\n" , cls); +continue ; + } + +vpr_info ("set_dyndbg_classes: bit %d: %s\n" , idx_rc, dcp->map->classes[idx_rc]); + inbits ^=BIT (idx_rc); + totct +=do_callback_changes (dcp, idx_rc, &inbits); + } +kfree (cls); + *dcp->bits = inbits; +vpr_info ("total matches: %d\n" , totct); +return 0 ; +} +/** * param_set_dyndbg_classes - bits => categories >control setter * @instr: string echo>d to sysfs
@@ -639,10 +694,9 @@ int param_set_dyndbg_classes(const char *instr, const struct kernel_param *kp)return -EINVAL ; } rc =kstrtoul (instr,0 , &inbits); -if (rc) { -pr_err ("set_dyndbg_classes: expecting bits/integer\n" ); -return -EINVAL ; - } +if (rc) +return param_set_dyndbg_class_strings (instr, kp); +vpr_info ("set_dyndbg_classes: new 0x%lx current 0x%lx\n" , inbits, *dcp->bits);for (i =0 ; i < dcp->map->length; i++) {
@@ -650,6 +704,7 @@ int param_set_dyndbg_classes(const char *instr, const struct kernel_param *kp)if (test_bit (i, &inbits) ==test_bit (i, dcp->bits))continue ; +vpr_info ("set_dyndbg_classes: bit %d: %s\n" , i, dcp->map->classes[i]); totct +=do_callback_changes (dcp, i, &inbits); } *dcp->bits = inbits;
Signature · 1 line
2.35.3
Jim Cromie
maintainerPATCH v2 12/27 dyndbg: change zero-or-one classes-map to maps list
In reply to Jim CromieUpgrade single classes-map to list of them:
This allows multiple DYNAMIC_DEBUG_CLASSES(class-map)s per module, using _base to segment the 0..30 classid space.
alter struct ddebug table:
replace .classes (a &map) with maps (list-head)
dynamic_debug_register_classes(map) - adds new map to maps list.
dynamic_debug_unregister_classes(map) - deletes map after ID-check.
ddebug_validate_classname() - check all maps in list before failing.
ddebug_class_name() - which supports ```cat control``` now walks maps list, finds the map whose sub-range of .class_id's spans the one in the callsite, and returns that class-name.
---
. split out validate_classnames()
. fold in fixes for multi class-maps
--- lib/dynamic_debug.c | 76 +++++++++++++++++++++++++++++++-------------- 1 file changed, 52 insertions(+), 24 deletions(-)
lib/dynamic_debug.c +52 -24
@@ -43,10 +43,8 @@ extern struct _ddebug __start___dyndbg[];extern struct _ddebug __stop___dyndbg[];struct ddebug_table { -struct list_head link; +struct list_head link, maps;const char *mod_name; -/* a module can have multiple class-sets eventually, but not yet */ -struct ddebug_known_classes_map const *map;unsigned int num_ddebugs;struct _ddebug *ddebugs; };
@@ -149,28 +147,18 @@ static void vpr_info_dq(const struct ddebug_query *query, const char *msg)/* return <0 if class-name is unknown/invalid, 0..CLASS_DFLT otherwise */ static int ddebug_validate_classname (struct ddebug_table *dt,const char *class_string) { -int query_class = -ENOENT ; +struct ddebug_known_classes_map *map;int idx;if (!class_string) -/* all queries w/o class given work only on default class */ return _DPRINTK_CLASS_DFLT; -/* -* XXX single list will need to be a for-list -* so that modules can have 2 sets of class-decls -*/ -if (!dt->map) -return -ENOENT ; - - idx =match_string (dt->map->classes, dt->map->length, class_string); -if (idx <0 ) { -v3pr_info ("class: %s.%s unknown\n" , dt->mod_name, class_string); -return -ENOENT ; +list_for_each_entry (map, &dt->maps, link) { + idx =match_string (map->classes, map->length, class_string); +if (idx >=0 ) +return idx + map->base; } - query_class = idx + dt->map->base; - -return query_class; +return -ENOENT ; }/*
@@ -1032,8 +1020,14 @@ static void *ddebug_proc_next(struct seq_file *m, void *p, loff_t *pos)static const char *ddebug_class_name (struct ddebug_iter *iter,struct _ddebug *dp) { -if (iter->table->map) -return iter->table->map->classes[dp->class_id]; +struct ddebug_known_classes_map *map; + +list_for_each_entry (map, &iter->table->maps, link) { +if (dp->class_id < map->base || + dp->class_id >= map->base + map->length) +continue ; +return map->classes[dp->class_id - map->base]; + }return NULL ; }
@@ -1124,6 +1118,7 @@ int dynamic_debug_register_classes(struct ddebug_known_classes_map *map)struct ddebug_table *dt;int rc = -ENOENT ; +INIT_LIST_HEAD (&map->link);mutex_lock (&ddebug_lock);#ifdef CONFIG_MODULES if (map->mod) {
@@ -1131,7 +1126,7 @@ int dynamic_debug_register_classes(struct ddebug_known_classes_map *map)list_for_each_entry (dt, &ddebug_tables, link) {if (dt->mod_name == map->mod->name) { rc =0 ; - dt->map = map; +list_add (&map->link, &dt->maps);break ; } }
@@ -1142,7 +1137,7 @@ int dynamic_debug_register_classes(struct ddebug_known_classes_map *map)list_for_each_entry (dt, &ddebug_tables, link) {if (!strcmp (dt->mod_name, map->mod_name)) { rc =0 ; - dt->map = map; +list_add (&map->link, &dt->maps);break ; } }
@@ -1159,8 +1154,38 @@ EXPORT_SYMBOL(dynamic_debug_register_classes);void dynamic_debug_unregister_classes (struct ddebug_known_classes_map *map) { -vpr_info ("unregister_classes: %s\n" , map->mod_name); +int rc = -ENOENT ; + +mutex_lock (&ddebug_lock); +#ifdef CONFIG_MODULES +if (map->mod) { +struct ddebug_known_classes_map *dmap; +struct ddebug_table *dt; + +list_for_each_entry (dt, &ddebug_tables, link) { +if (dt->mod_name != map->mod->name) +continue ; +list_for_each_entry (dmap, &dt->maps, link) { +if (dmap != map) +continue ; + rc =0 ; +list_del (&map->link); +break ; + } + } + } +#endif +if (!map->mod) { +pr_err ("shouldn't be unloading a builtin module: %s\n" , + map->mod_name); + } +mutex_unlock (&ddebug_lock); +if (rc) +pr_warn ("unregister_classes: module %s not found\n" , map->mod_name); +else +vpr_info ("unregister_classes: %s\n" , map->mod_name); } +EXPORT_SYMBOL (dynamic_debug_unregister_classes);/* * Allocate a new ddebug_table for the given module
@@ -1186,6 +1211,9 @@ int ddebug_add_module(struct _ddebug *tab, unsigned int n, dt->num_ddebugs = n; dt->ddebugs = tab; +INIT_LIST_HEAD (&dt->link); +INIT_LIST_HEAD (&dt->maps); +mutex_lock (&ddebug_lock);list_add (&dt->link, &ddebug_tables);mutex_unlock (&ddebug_lock);
Signature · 1 line
2.35.3
Jim Cromie
maintainerPATCH v2 13/27 dyndbg: add __pr_debug_cls(class, fmt, ...)
In reply to Jim CromieFor selftest purposes, add __pr_debug_cls(class, fmt, ...)
I didn't think we'd need to define this, since DRM effectively has it already. But test_dynamic_debug needs it in order to demonstrate all the moving parts.
Note the __ prefix; its not intended for general use, and doesn't include any builtin-constant checks that could pertain. I'd prefer to see a use-case where copying the drm.debug model isn't better.
--- include/linux/dynamic_debug.h | 7 +++++++ 1 file changed, 7 insertions(+)
include/linux/dynamic_debug.h +7 -0
@@ -216,6 +216,10 @@ void __dynamic_ibdev_dbg(struct _ddebug *descriptor, _DPRINTK_CLASS_DFLT, \ fmt, func, ##__VA_ARGS__) +#define dynamic_pr_debug_cls (cls, fmt, ...) \ + _dynamic_func_call_cls(cls, fmt, __dynamic_pr_debug, \ + pr_fmt(fmt), ##__VA_ARGS__) +#define dynamic_pr_debug (fmt, ...) \ _dynamic_func_call(fmt, __dynamic_pr_debug, \ pr_fmt(fmt), ##__VA_ARGS__)
@@ -246,6 +250,9 @@ struct kernel_param;int param_set_dyndbg_classes (const char *instr,const struct kernel_param *kp);int param_get_dyndbg_classes (char *buffer,const struct kernel_param *kp); +#define __pr_debug_cls (cls, fmt, ...) \ + dynamic_pr_debug_cls(cls, fmt, ##__VA_ARGS__) +#else /* !CONFIG_DYNAMIC_DEBUG_CORE */ #include <linux/string.h>
Signature · 1 line
2.35.3
Jim Cromie
maintainerPATCH v2 14/27 dyndbg: add test_dynamic_debug module
In reply to Jim CromieDemonstrate dyndbg's "class FOO" and bitmap-to-classes support. This support is meant to plug into drm.debug system, and largely replace the use of drm_debug_enabled(category) with JUMP_LABELs.
Recap:
#> echo class DRM_UT_CORE +p > /proc/dynamic_debug/control
This is made "safe" because dyndbg skips it for any modules which don't know that class (havent called dynamic_debug_register_classes).
Other modules may use the same .class_id for a separate classified debug scheme.
Use the API:
- DYNAMIC_DEBUG_CLASSES(_var, classes), to declare static _var by name
- dynamic_debug_register_classes(_var)
- dynamic_debug_unregister_classes(_var)
Use these 3 times; with base = 0,8,16 respectively, to demonstrate the segmenting of the module's .class_id range [0..30]
For each of those 3 class-name-sets, add 2 sysfs-node-bitmaps, one each for p-syslog, and T-tracefs, the latter will work once dyndbg gets that patchset.
#> modprobe test_dynamic_debug dyndbg=+pfm
#> cat /sys/module/test_dynamic_debug/parameters/do_prints #> echo class FOO +pf > /proc/dynamic_debug/control #> echo class Foo +pfm > /proc/dynamic_debug/control #> cat /sys/module/test_dynamic_debug/parameters/do_prints
RFC:
This use case exposes a weak point in the api; the 2nd query command given in the dyndbg option will not work like the 1st:
#> modprobe test_dynamic_debug dyndbg='+pfm; class FOO +pfm'
This is because the option is processed early in module-load, well before the registration can attach the class-map to the module's ddebug_table entry.
--- MAINTAINERS | 1 + lib/Kconfig.debug | 11 +++ lib/Makefile | 1 + lib/test_dynamic_debug.c | 172 +++++++++++++++++++++++++++++++++++++++ 4 files changed, 185 insertions(+) create mode 100644 lib/test_dynamic_debug.c
MAINTAINERS +1 -0
@@ -6918,6 +6918,7 @@ M: Jason Baron <[email protected]> S: Maintained F: include/linux/dynamic_debug.h F: lib/dynamic_debug.c +F: lib/test_dynamic_debug.c DYNAMIC INTERRUPT MODERATION M: Tal Gilboa <[email protected]>
lib/Kconfig.debug +11 -0
@@ -2601,6 +2601,17 @@ config TEST_STATIC_KEYS If unsure, say N. +config TEST_DYNAMIC_DEBUG + tristate "Test DYNAMIC_DEBUG" + depends on m + depends on DYNAMIC_DEBUG + help + This module registers a tracer callback to count enabled + pr_debugs in a 'do_debugging' function, then alters their + enablements, calls the function, and compares counts. + + If unsure, say N. + config TEST_KMOD tristate "kmod stress tester" depends on m
lib/Makefile +1 -0
@@ -82,6 +82,7 @@ obj-$(CONFIG_TEST_SORT) += test_sort.o obj-$(CONFIG_TEST_USER_COPY) += test_user_copy.o obj-$(CONFIG_TEST_STATIC_KEYS) += test_static_keys.o obj-$(CONFIG_TEST_STATIC_KEYS) += test_static_key_base.o +obj-$(CONFIG_TEST_DYNAMIC_DEBUG) += test_dynamic_debug.o obj-$(CONFIG_TEST_PRINTF) += test_printf.o obj-$(CONFIG_TEST_SCANF) += test_scanf.o obj-$(CONFIG_TEST_BITMAP) += test_bitmap.o
lib/test_dynamic_debug.c new file +172 -0
172 lines not on this page · raw message
Signature · 1 line
2.35.3
Jim Cromie
maintainerPATCH v2 15/27 drm: POC drm on dyndbg - map class-names to drm_debug_category's
In reply to Jim CromieInvoke DYNAMIC_DEBUG_CLASSES from drm_drv.h. This declares a maybe-unused struct ddebug_known_classes_map var, initialized with:
. var: passed to dynamic_debug_register_classes()
. class-names: "DRM_UT_CORE", "DRM_UT_DRIVER", "DRM_UT_KMS", etc.
These names map to .class_id's by their index, ie: 0-30.
Then in 4 test-case drm-drivers (drm, i915, amdgpu, nouveau); call dynamic_debug_register_classes(var). i915 also gets an adaptor func, and calls it 1st in the array of initialization helpers, since early logging might be valuable for diagnosing setup problems.
Since these modules all use the same class-names, they all will respond together to class FOO changes:
#> echo class DRM_UT_KMS +p > /proc/dynamic_debug/control
NOTES:
DRM uses enum drm_debug_category across modules and common core, so our class-names => index map must apply across them too, hence drm_drv.h invokes the macro once for everyone.
DRM's enum drm_debug_category values need to sync with the index of their respective class-names here. Then .class_id == category, and dyndbg's class FOO mechanisms will work. Once enum drm_debug_category is naturalized (value inits dropped, yielding 0..N), then this condition holds true:
assert(!strcmp(classes[DRM_UT_KMS],"DRM_UT_KMS"));
Though DRM needs consistent categories across all modules, thats not generally needed; modules X and Y could define FOO differently (ie different corresponding .class_id) and things would work.
No callsites are actually selected here, since none are class'd yet.
bash-5.1# dmesg | grep register_class
[ 7.095579] dyndbg: register_classes: drm [ 7.557109] dyndbg: register_classes: i915 [ 8.096818] dyndbg: register_classes: amdgpu
--- drivers/gpu/drm/amd/amdgpu/amdgpu_drv.c | 3 +++ drivers/gpu/drm/drm_drv.c | 2 ++ drivers/gpu/drm/i915/i915_module.c | 11 +++++++++++ drivers/gpu/drm/nouveau/nouveau_drm.c | 4 ++++ include/drm/drm_drv.h | 14 ++++++++++++++ include/drm/drm_print.h | 4 ++++ 6 files changed, 38 insertions(+)
drivers/gpu/drm/amd/amdgpu/amdgpu_drv.c +3 -0
@@ -2765,6 +2765,8 @@ static int __init amdgpu_init(void)if (r) goto error_fence; +dynamic_debug_register_classes (&drm_debug_classes); +DRM_INFO ("amdgpu kernel modesetting enabled.\n" );amdgpu_register_atpx_handler ();amdgpu_acpi_detect ();
@@ -2787,6 +2789,7 @@ static void __exit amdgpu_exit(void)amdgpu_amdkfd_fini ();pci_unregister_driver (&amdgpu_kms_pci_driver);amdgpu_unregister_atpx_handler (); +dynamic_debug_unregister_classes (&drm_debug_classes);amdgpu_sync_fini ();amdgpu_fence_slab_fini ();mmu_notifier_synchronize ();
drivers/gpu/drm/drm_drv.c +2 -0
@@ -1045,6 +1045,8 @@ static int __init drm_core_init(void) {int ret; +dynamic_debug_register_classes (&drm_debug_classes); +drm_connector_ida_init ();idr_init (&drm_minors_idr);drm_memcpy_init_early ();
drivers/gpu/drm/i915/i915_module.c +11 -0
@@ -44,10 +44,21 @@ static int i915_check_nomodeset(void)return 0 ; } +static int i915_ddebug_classes_register (void ) +{ +return dynamic_debug_register_classes (&drm_debug_classes); +} +static void i915_ddebug_classes_unregister (void ) +{ +dynamic_debug_unregister_classes (&drm_debug_classes); +} +static const struct {int (*init)(void );void (*exit)(void ); } init_funcs[] = { + { .init = i915_ddebug_classes_register, + .exit = i915_ddebug_classes_unregister }, { .init = i915_check_nomodeset }, { .init = i915_active_module_init, .exit = i915_active_module_exit },
drivers/gpu/drm/nouveau/nouveau_drm.c +4 -0
@@ -1355,6 +1355,8 @@ nouveau_drm_init(void) driver_pci = driver_stub; driver_platform = driver_stub; +dynamic_debug_register_classes (&drm_debug_classes); +nouveau_display_options ();if (nouveau_modeset ==-1 ) {
@@ -1391,6 +1393,8 @@ nouveau_drm_exit(void)nouveau_backlight_dtor ();nouveau_unregister_dsm_handler (); +dynamic_debug_unregister_classes (&drm_debug_classes); +#ifdef CONFIG_NOUVEAU_PLATFORM_DRIVER platform_driver_unregister (&nouveau_platform_driver);#endif
include/drm/drm_drv.h +14 -0
@@ -29,6 +29,7 @@#include <linux/list.h> #include <linux/irqreturn.h> +#include <linux/dynamic_debug.h> #include <drm/drm_device.h>
@@ -43,6 +44,19 @@ struct drm_mode_create_dumb;struct drm_printer ;struct sg_table ; +/* these must comport with enum drm_debug_category values */ +DYNAMIC_DEBUG_CLASSES (drm_debug_classes,"*" ,0 , +"DRM_UT_CORE" , +"DRM_UT_DRIVER" , +"DRM_UT_KMS" , +"DRM_UT_PRIME" , +"DRM_UT_ATOMIC" , +"DRM_UT_VBL" , +"DRM_UT_STATE" , +"DRM_UT_LEASE" , +"DRM_UT_DP" , +"DRM_UT_DRMRES" ); +/** * enum drm_driver_feature - feature flags *
include/drm/drm_print.h +4 -0
@@ -274,6 +274,10 @@ static inline struct drm_printer drm_err_printer(const char *prefix)* # echo 0xf > /sys/module/drm/parameters/debug * */ +/* +* These must be kept in sync with the class-names given in drm_drv.h +* DYNAMIC_DEBUG_CLASSES +*/ enum drm_debug_category {/** * @DRM_UT_CORE: Used in the generic drm code: drm_ioctl.c, drm_mm.c,
Signature · 1 line
2.35.3
Jim Cromie
maintainerPATCH v2 16/27 drm/print: POC drm on dyndbg - use bitmap
In reply to Jim CromiePOC: adapt drm_print to use/test the bitmap callback support.
with dynamic_debug.verbose=1:
bash-5.1# echo 1 > /sys/module/drm/parameters/debug
[ 33.697039] dyndbg: set_dyndbg_classes: new 0x1 current 0x0 [ 33.697571] dyndbg: query 0: "class DRM_UT_CORE +p" mod:* [ 33.698072] dyndbg: no matches for query [ 33.698498] dyndbg: total matches: 0 bash-5.1# echo 2 > /sys/module/drm/parameters/debug [ 46.687012] dyndbg: set_dyndbg_classes: new 0x2 current 0x1 [ 46.687655] dyndbg: query 0: "class DRM_UT_CORE -p" mod:* [ 46.688280] dyndbg: no matches for query [ 46.688632] dyndbg: query 0: "class DRM_UT_DRIVER +p" mod:* [ 46.689122] dyndbg: no matches for query [ 46.689441] dyndbg: total matches: 0
This changes typeof __drm_debug to unsigned long from unsigned int, which dyndbg requires so it can use BIT().
It is currently dependent on CONFIG_DYNAMIC_DEBUG_CORE, which is only aproximately correct, it will need proper DRM dependence too.
--- drivers/gpu/drm/drm_print.c | 14 ++++++++++++-- include/drm/drm_print.h | 3 ++- 2 files changed, 14 insertions(+), 3 deletions(-)
drivers/gpu/drm/drm_print.c +12 -2
@@ -40,7 +40,7 @@* __drm_debug: Enable debug output. * Bitmask of DRM_UT_x. See include/drm/drm_print.h for details. */ -unsigned int __drm_debug; +unsigned long __drm_debug;EXPORT_SYMBOL (__drm_debug); MODULE_PARM_DESC(debug, "Enable debug output, where each bit enables a debug category.\n"
@@ -52,7 +52,17 @@ MODULE_PARM_DESC(debug, "Enable debug output, where each bit enables a debug cat"\t\tBit 5 (0x20) will enable VBL messages (vblank code)\n" "\t\tBit 7 (0x80) will enable LEASE messages (leasing code)\n" "\t\tBit 8 (0x100) will enable DP messages (displayport code)"); -module_param_named (debug, __drm_debug, int,0600 ); + +#if !defined(CONFIG_DYNAMIC_DEBUG_CORE ) +module_param_named (debug, __drm_debug, ulong,0600 ); +#else +static struct ddebug_classes_bitmap_param drm_debug_bitmap = { + .bits = &__drm_debug, + .flags ="p" , + .map = &drm_debug_classes, +}; +module_param_cb (debug, ¶m_ops_dyndbg_classes, &drm_debug_bitmap,0600 ); +#endif void __drm_puts_coredump (struct drm_printer *p,const char *str) {
include/drm/drm_print.h +2 -1
@@ -31,11 +31,12 @@#include <linux/seq_file.h> #include <linux/device.h> #include <linux/debugfs.h> +#include <linux/dynamic_debug.h> #include <drm/drm.h> /* Do *not* use outside of drm_print.[ch]! */ -extern unsigned int __drm_debug; +extern unsigned long __drm_debug;/** * DOC: print
Signature · 1 line
2.35.3
Jim Cromie
maintainerPATCH v2 17/27 drm_print: condense enum drm_debug_category
In reply to Jim Cromieenum drm_debug_category has 10 categories, but is initialized with bitmasks which require 10 bits of underlying storage. By using natural enumeration, and moving the BIT(cat) into drm_debug_enabled(), the enum fits in 4 bits, allowing the category to be represented directly in pr_debug callsites, via the ddebug.class_id field.
While this slightly pessimizes the bit-test in drm_debug_enabled(), using dyndbg with JUMP_LABEL will avoid the function entirely.
NOTE: this change forecloses the possibility of doing:
drm_dbg(DRM_UT_CORE|DRM_UT_KMS, "weird 2-cat experiment")
but thats already strongly implied by the use of the enum itself; its not a normal enum if it can be 2 values simultaneously.
--- include/drm/drm_print.h | 22 +++++++++++----------- 1 file changed, 11 insertions(+), 11 deletions(-)
include/drm/drm_print.h +11 -11
@@ -284,49 +284,49 @@ enum drm_debug_category {* @DRM_UT_CORE: Used in the generic drm code: drm_ioctl.c, drm_mm.c, * drm_memory.c, ... */ -DRM_UT_CORE =0x01 , +DRM_UT_CORE ,/** * @DRM_UT_DRIVER: Used in the vendor specific part of the driver: i915, * radeon, ... macro. */ -DRM_UT_DRIVER =0x02 , +DRM_UT_DRIVER ,/** * @DRM_UT_KMS: Used in the modesetting code. */ -DRM_UT_KMS =0x04 , +DRM_UT_KMS ,/** * @DRM_UT_PRIME: Used in the prime code. */ -DRM_UT_PRIME =0x08 , +DRM_UT_PRIME ,/** * @DRM_UT_ATOMIC: Used in the atomic code. */ -DRM_UT_ATOMIC =0x10 , +DRM_UT_ATOMIC ,/** * @DRM_UT_VBL: Used for verbose debug message in the vblank code. */ -DRM_UT_VBL =0x20 , +DRM_UT_VBL ,/** * @DRM_UT_STATE: Used for verbose atomic state debugging. */ -DRM_UT_STATE =0x40 , +DRM_UT_STATE ,/** * @DRM_UT_LEASE: Used in the lease code. */ -DRM_UT_LEASE =0x80 , +DRM_UT_LEASE ,/** * @DRM_UT_DP: Used in the DP code. */ -DRM_UT_DP =0x100 , +DRM_UT_DP ,/** * @DRM_UT_DRMRES: Used in the drm managed resources code. */ - DRM_UT_DRMRES = 0x200, +DRM_UT_DRMRES };static inline bool drm_debug_enabled (enum drm_debug_category category) { -return unlikely (__drm_debug & category); +return unlikely (__drm_debug &BIT (category)); }/*
Signature · 1 line
2.35.3
Jim Cromie
maintainerPATCH v2 18/27 drm_print: interpose drm_*dbg with forwarding macros
In reply to Jim Cromiechange drm_dev_dbg & drm_dbg to macros, which forward to the renamed functions (with __ prefix added).
Those functions sit below the categorized layer of macros implementing the DRM debug.category API, and implement most of it. These are good places to insert dynamic-debug jump-label mechanics, which will allow DRM to avoid the runtime cost of drm_debug_enabled().
no functional changes.
memory cost baseline: (unchanged)
bash-5.1# drms_load
[ 9.220389] dyndbg: 1 debug prints in module drm [ 9.224426] ACPI: bus type drm_connector registered [ 9.302192] dyndbg: 2 debug prints in module ttm [ 9.305033] dyndbg: 8 debug prints in module video [ 9.627563] dyndbg: 127 debug prints in module i915 [ 9.721505] AMD-Vi: AMD IOMMUv2 functionality not available on this system - This is not a bug. [ 10.091345] dyndbg: 2196 debug prints in module amdgpu [ 10.106589] [drm] amdgpu kernel modesetting enabled. [ 10.107270] amdgpu: CRAT table not found [ 10.107926] amdgpu: Virtual CRAT table created for CPU [ 10.108398] amdgpu: Topology: Add CPU node [ 10.168507] dyndbg: 3 debug prints in module wmi [ 10.329587] dyndbg: 3 debug prints in module nouveau
--- drivers/gpu/drm/drm_print.c | 10 +++++----- include/drm/drm_print.h | 9 +++++++-- 2 files changed, 12 insertions(+), 7 deletions(-)
drivers/gpu/drm/drm_print.c +5 -5
@@ -266,8 +266,8 @@ void drm_dev_printk(const struct device *dev, const char *level, }EXPORT_SYMBOL (drm_dev_printk); -void drm_dev_dbg (const struct device *dev,enum drm_debug_category category, -const char *format, ...) +void __drm_dev_dbg (const struct device *dev,enum drm_debug_category category, +const char *format, ...) {struct va_format vaf;va_list args;
@@ -288,9 +288,9 @@ void drm_dev_dbg(const struct device *dev, enum drm_debug_category category,va_end (args); } -EXPORT_SYMBOL (drm_dev_dbg); +EXPORT_SYMBOL (__drm_dev_dbg); -void __drm_dbg (enum drm_debug_category category,const char *format, ...) +void ___drm_dbg (enum drm_debug_category category,const char *format, ...) {struct va_format vaf;va_list args;
@@ -307,7 +307,7 @@ void __drm_dbg(enum drm_debug_category category, const char *format, ...)va_end (args); } -EXPORT_SYMBOL (__drm_dbg); +EXPORT_SYMBOL (___drm_dbg);void __drm_err (const char *format, ...) {
include/drm/drm_print.h +7 -2
@@ -339,7 +339,7 @@ __printf(3, 4)void drm_dev_printk (const struct device *dev,const char *level,const char *format, ...); __printf(3, 4) -void drm_dev_dbg (const struct device *dev,enum drm_debug_category category, +void __drm_dev_dbg (const struct device *dev,enum drm_debug_category category,const char *format, ...);/**
@@ -388,6 +388,9 @@ void drm_dev_dbg(const struct device *dev, enum drm_debug_category category, } \ }) +#define drm_dev_dbg (dev, cat, fmt, ...) \ + __drm_dev_dbg(dev, cat, fmt, ##__VA_ARGS__) +/** * DRM_DEV_DEBUG() - Debug output for generic drm code *
@@ -489,10 +492,12 @@ void drm_dev_dbg(const struct device *dev, enum drm_debug_category category,*/ __printf(2, 3) -void __drm_dbg (enum drm_debug_category category,const char *format, ...); +void ___drm_dbg (enum drm_debug_category category,const char *format, ...); __printf(1, 2)void __drm_err (const char *format, ...); +#define __drm_dbg (fmt, ...) ___drm_dbg(fmt, ##__VA_ARGS__) +/* Macros to make printk easier */ #define _DRM_PRINTK (once, level, fmt, ...) \
Signature · 1 line
2.35.3
Jim Cromie
maintainerPATCH v2 19/27 drm_print: wrap drm_*_dbg in dyndbg descriptor factory macro
In reply to Jim CromieFor CONFIG_DRM_USE_DYNAMIC_DEBUG=y, wrap __drm_dbg() & __drm_dev_dbg() in one of dyndbg's Factory macros: _dynamic_func_call_no_desc().
Next, those functions are adapted to accept a descriptor arg, and we drop the _no_desc suffix, then the (~4000) drm.debug callsites will be controllable by their class-names:
#> echo class DRM_UT_ATOMIC +p > /proc/dynamic_debug/control
CONFIG_DRM_USE_DYNAMIC_DEBUG=y/n is configurable because of the .data footprint cost of per-callsite control; 56 bytes/site * ~2k for i915, ~4k callsites for amdgpu. This is large enough that a kernel builder might not want it.
--- drivers/gpu/drm/Kconfig | 12 ++++++++++++ drivers/gpu/drm/Makefile | 2 ++ drivers/gpu/drm/drm_print.c | 2 +- include/drm/drm_print.h | 12 ++++++++++++ 4 files changed, 27 insertions(+), 1 deletion(-)
drivers/gpu/drm/Kconfig +12 -0
@@ -63,6 +63,18 @@ config DRM_DEBUG_MM If in doubt, say "N". +config DRM_USE_DYNAMIC_DEBUG + bool "use dynamic debug to implement drm.debug" + default y + depends on DRM + depends on DYNAMIC_DEBUG || DYNAMIC_DEBUG_CORE + depends on JUMP_LABEL + help + Use dynamic-debug to avoid drm_debug_enabled() runtime overheads. + Due to callsite counts in DRM drivers (~4k in amdgpu) and 56 + bytes per callsite, the .data costs can be substantial, and + are therefore configurable. + config DRM_DEBUG_SELFTEST tristate "kselftests for DRM" depends on DRM
drivers/gpu/drm/Makefile +2 -0
@@ -3,6 +3,8 @@ # Makefile for the drm device driver. This driver provides support for the # Direct Rendering Infrastructure (DRI) in XFree86 4.1.0 and higher. +CFLAGS-$(CONFIG_DRM_USE_DYNAMIC_DEBUG) += -DDYNAMIC_DEBUG_MODULE + drm-y := drm_aperture.o drm_auth.o drm_cache.o \ drm_file.o drm_gem.o drm_ioctl.o \ drm_drv.o \
drivers/gpu/drm/drm_print.c +1 -1
@@ -53,7 +53,7 @@ MODULE_PARM_DESC(debug, "Enable debug output, where each bit enables a debug cat"\t\tBit 7 (0x80) will enable LEASE messages (leasing code)\n" "\t\tBit 8 (0x100) will enable DP messages (displayport code)"); -#if !defined(CONFIG_DYNAMIC_DEBUG_CORE ) +#if !defined(CONFIG_DRM_USE_DYNAMIC_DEBUG )module_param_named (debug, __drm_debug, ulong,0600 );#else static struct ddebug_classes_bitmap_param drm_debug_bitmap = {
include/drm/drm_print.h +12 -0
@@ -388,8 +388,14 @@ void __drm_dev_dbg(const struct device *dev, enum drm_debug_category category, } \ }) +#if !defined(CONFIG_DRM_USE_DYNAMIC_DEBUG )#define drm_dev_dbg (dev, cat, fmt, ...) \ __drm_dev_dbg(dev, cat, fmt, ##__VA_ARGS__) +#else +#define drm_dev_dbg (dev, cat, fmt, ...) \ + _dynamic_func_call_no_desc(fmt, __drm_dev_dbg, \ + dev, cat, fmt, ##__VA_ARGS__) +#endif /** * DRM_DEV_DEBUG() - Debug output for generic drm code
@@ -496,7 +502,13 @@ void ___drm_dbg(enum drm_debug_category category, const char *format, ...); __printf(1, 2)void __drm_err (const char *format, ...); +#if !defined(CONFIG_DRM_USE_DYNAMIC_DEBUG )#define __drm_dbg (fmt, ...) ___drm_dbg(fmt, ##__VA_ARGS__) +#else +#define __drm_dbg (cat, fmt, ...) \ + _dynamic_func_call_no_desc(fmt, ___drm_dbg, \ + cat, fmt, ##__VA_ARGS__) +#endif /* Macros to make printk easier */
Signature · 1 line
2.35.3
Jim Cromie
maintainerPATCH v2 20/27 drm_print: refine drm_debug_enabled for jump-label
In reply to Jim CromieIn order to use dynamic-debug's jump-label optimization in drm-debug, its clarifying to refine drm_debug_enabled into 3 uses:
1. drm_debug_enabled - legacy, public
2. __drm_debug_enabled - optimized for dyndbg jump-label enablement.
3. _drm_debug_enabled - pr_debug instrumented, observable
1. The legacy version always checks the bits.
2. is privileged, for use by __drm_dbg(), __drm_dev_dbg(), which do an early return unless the category is enabled (free of call/NOOP side effects). For dyndbg builds, debug callsites are selectively "pre-enabled", so __drm_debug_enabled() short-circuits to true there. Remaining callers of 1 may be able to use 2, case by case.
3. is 1st wrapped in a macro, with a pr_debug, which reports each usage in /proc/dynamic_debug/control, making it observable in the logs. The macro lets the pr_debug see the real caller, not an inline function.
When plugged into 1, it identified ~10 remaining callers of the function, leading to the follow-on cleanup patch, and would allow activating the pr_debugs, estimating the callrate, and the potential savings by using the wrapper macro. It is unused ATM, but it fills out the picture.
--- drivers/gpu/drm/drm_print.c | 4 ++-- include/drm/drm_print.h | 28 ++++++++++++++++++++++++++++ 2 files changed, 30 insertions(+), 2 deletions(-)
drivers/gpu/drm/drm_print.c +2 -2
@@ -272,7 +272,7 @@ void __drm_dev_dbg(const struct device *dev, enum drm_debug_category category,struct va_format vaf;va_list args; -if (!drm_debug_enabled (category)) +if (!__drm_debug_enabled (category))return ;va_start (args, format);
@@ -295,7 +295,7 @@ void ___drm_dbg(enum drm_debug_category category, const char *format, ...)struct va_format vaf;va_list args; -if (!drm_debug_enabled (category)) +if (!__drm_debug_enabled (category))return ;va_start (args, format);
include/drm/drm_print.h +28 -0
@@ -324,11 +324,39 @@ enum drm_debug_category { DRM_UT_DRMRES }; +/* +* 3 name flavors of drm_debug_enabled: +* drm_debug_enabled - public/legacy, always checks bits +* _drm_debug_enabled - instrumented to observe call-rates, est overheads. +* __drm_debug_enabled - privileged - knows jump-label state, can short-circuit +*/ static inline bool drm_debug_enabled (enum drm_debug_category category) {return unlikely (__drm_debug &BIT (category)); } +/* +* Wrap fn in macro, so that the pr_debug sees the actual caller, not +* the inline fn. Using this name creates a callsite entry / control +* point in /proc/dynamic_debug/control. +*/ +#define _drm_debug_enabled (category) \ + ({ \ + pr_debug("todo: maybe avoid via dyndbg\n"); \ + drm_debug_enabled(category); \ + }) + +#if defined(CONFIG_DRM_USE_DYNAMIC_DEBUG ) +/* +* dyndbg is wrapping the drm.debug API, so as to avoid the runtime +* bit-test overheads of drm_debug_enabled() in those api calls. +* In this case, executed callsites are known enabled, so true. +*/ +#define __drm_debug_enabled (category) true +#else +#define __drm_debug_enabled (category) drm_debug_enabled(category) +#endif +/* * struct device based logging *
Signature · 1 line
2.35.3
Jim Cromie
maintainerPATCH v2 21/27 drm_print: prefer bare printk KERN_DEBUG on generic fn
In reply to Jim Cromiedrm_print.c calls pr_debug() just once, from __drm_printfn_debug(), which is a generic/service fn. The callsite is compile-time enabled by DEBUG in both DYNAMIC_DEBUG=y/n builds.
For dyndbg builds, reverting this callsite back to bare printk is correcting a few anti-features:
1- callsite is generic, serves multiple drm users.
its hardwired on currently
could accidentally: #> echo -p > /proc/dynamic_debug/control
2- optional "decorations" by dyndbg are unhelpful/misleading
they describe only the generic site, not end users
IOW, 1,2 are unhelpful at best, and possibly confusing.
reverting yields a nominal data and text shrink:
text data bss dec hex filename
462583 36604 54592 553779 87333 /kernel/drivers/gpu/drm/drm.ko 462515 36532 54592 553639 872a7 -dirty/kernel/drivers/gpu/drm/drm.ko
--- drivers/gpu/drm/drm_print.c | 5 ++--- 1 file changed, 2 insertions(+), 3 deletions(-)
drivers/gpu/drm/drm_print.c +2 -3
@@ -23,8 +23,6 @@* Rob Clark <[email protected]> */ -#define DEBUG /* for pr_debug() */ -#include <linux/stdarg.h> #include <linux/io.h>
@@ -172,7 +170,8 @@ EXPORT_SYMBOL(__drm_printfn_info);void __drm_printfn_debug (struct drm_printer *p,struct va_format *vaf) { -pr_debug ("%s %pV" , p->prefix, vaf); +/* pr_debug callsite decorations are unhelpful here */ +printk (KERN_DEBUG "%s %pV" , p->prefix, vaf); }EXPORT_SYMBOL (__drm_printfn_debug);
Signature · 1 line
2.35.3
Jim Cromie
maintainerPATCH v2 22/27 drm_print: add _ddebug desc to drm_*dbg prototypes
In reply to Jim CromieAdd a struct _ddebug ptr to drm_dbg() and drm_dev_dbg() protos, and upgrade their callers - the interposed macros added recently, to use _dynamic_func_call_no_desc(); ie drop the '_no_desc', since the factory macro's callees (these 2 functions) are now expecting the arg.
This makes those functions controllable like pr_debug(). It also means that they don't get to use the decorations implemented by pr_debug(). DRM already has standards for logging/messaging; tossing optional decorations on top may not help.
For CONFIG_DRM_USE_DYNAMIC_DEBUG=N, just pass null.
Note: desc->class_id is redundant with category parameter, but its availability is dependent on desc.
--- drivers/gpu/drm/drm_print.c | 23 +++++++++++++---------- include/drm/drm_print.h | 22 +++++++++++----------- 2 files changed, 24 insertions(+), 21 deletions(-)
drivers/gpu/drm/drm_print.c +13 -10
@@ -265,8 +265,8 @@ void drm_dev_printk(const struct device *dev, const char *level, }EXPORT_SYMBOL (drm_dev_printk); -void __drm_dev_dbg (const struct device *dev,enum drm_debug_category category, -const char *format, ...) +void __drm_dev_dbg (struct _ddebug *desc,const struct device *dev, +enum drm_debug_category category,const char *format, ...) {struct va_format vaf;va_list args;
@@ -274,22 +274,25 @@ void __drm_dev_dbg(const struct device *dev, enum drm_debug_category category,if (!__drm_debug_enabled (category))return ; +/* we know we are printing for either syslog, tracefs, or both */ va_start (args, format); vaf.fmt = format; vaf.va = &args; -if (dev) -dev_printk (KERN_DEBUG , dev,"[" DRM_NAME ":%ps] %pV" , -__builtin_return_address (0 ), &vaf); -else -printk (KERN_DEBUG "[" DRM_NAME ":%ps] %pV" , -__builtin_return_address (0 ), &vaf); - +if (dev) { +if (desc->flags && _DPRINTK_FLAGS_PRINT) +dev_printk (KERN_DEBUG , dev,"[" DRM_NAME ":%ps] %pV" , +__builtin_return_address (0 ), &vaf); + }else { +if (desc->flags && _DPRINTK_FLAGS_PRINT) +printk (KERN_DEBUG "[" DRM_NAME ":%ps] %pV" , +__builtin_return_address (0 ), &vaf); + }va_end (args); }EXPORT_SYMBOL (__drm_dev_dbg); -void ___drm_dbg (enum drm_debug_category category,const char *format, ...) +void ___drm_dbg (struct _ddebug *desc,enum drm_debug_category category,const char *format, ...) {struct va_format vaf;va_list args;
include/drm/drm_print.h +11 -11
@@ -366,9 +366,9 @@ static inline bool drm_debug_enabled(enum drm_debug_category category) __printf(3, 4)void drm_dev_printk (const struct device *dev,const char *level,const char *format, ...); -__printf(3, 4) -void __drm_dev_dbg (const struct device *dev,enum drm_debug_category category, -const char *format, ...); +__printf(4, 5) +void __drm_dev_dbg (struct _ddebug *desc,const struct device *dev, +enum drm_debug_category category,const char *format, ...);/** * DRM_DEV_ERROR() - Error output.
@@ -418,11 +418,11 @@ void __drm_dev_dbg(const struct device *dev, enum drm_debug_category category,#if !defined(CONFIG_DRM_USE_DYNAMIC_DEBUG )#define drm_dev_dbg (dev, cat, fmt, ...) \ - __drm_dev_dbg(dev, cat, fmt, ##__VA_ARGS__) + __drm_dev_dbg(NULL, dev, cat, fmt, ##__VA_ARGS__)#else #define drm_dev_dbg (dev, cat, fmt, ...) \ - _dynamic_func_call_no_desc(fmt, __drm_dev_dbg, \ - dev, cat, fmt, ##__VA_ARGS__) + _dynamic_func_call_cls(cat, fmt, __drm_dev_dbg, \ + dev, cat, fmt, ##__VA_ARGS__)#endif /**
@@ -525,17 +525,17 @@ void __drm_dev_dbg(const struct device *dev, enum drm_debug_category category,* Prefer drm_device based logging over device or prink based logging. */ -__printf(2, 3) -void ___drm_dbg (enum drm_debug_category category,const char *format, ...); +__printf(3, 4) +void ___drm_dbg (struct _ddebug *desc,enum drm_debug_category category,const char *format, ...); __printf(1, 2)void __drm_err (const char *format, ...);#if !defined(CONFIG_DRM_USE_DYNAMIC_DEBUG ) -#define __drm_dbg (fmt, ...) ___drm_dbg(fmt, ##__VA_ARGS__) +#define __drm_dbg (fmt, ...) ___drm_dbg(NULL, fmt, ##__VA_ARGS__)#else #define __drm_dbg (cat, fmt, ...) \ - _dynamic_func_call_no_desc(fmt, ___drm_dbg, \ - cat, fmt, ##__VA_ARGS__) + _dynamic_func_call_cls(cat, fmt, ___drm_dbg, \ + cat, fmt, ##__VA_ARGS__)#endif /* Macros to make printk easier */
Signature · 1 line
2.35.3
Jim Cromie
maintainerPATCH v2 23/27 dyndbg: add _DPRINTK_FLAGS_ENABLED
In reply to Jim CromieDistinguish the condition: _DPRINTK_FLAGS_ENABLED from the bit:_DPRINTK_FLAGS_PRINT (and define former as latter), in preparation to add another bit next: _DPRINTK_FLAGS_TRACE
And change JUMP_LABEL code block to use the more general _DPRINTK_FLAGS_ENABLED symbol. Also add a 'K' to get new symbol _DPRINTK_FLAGS_PRINTK, in order to break any stale uses.
--- drivers/gpu/drm/drm_print.c | 4 ++-- include/linux/dynamic_debug.h | 10 ++++++---- lib/dynamic_debug.c | 8 ++++---- 3 files changed, 12 insertions(+), 10 deletions(-)
drivers/gpu/drm/drm_print.c +2 -2
@@ -280,11 +280,11 @@ void __drm_dev_dbg(struct _ddebug *desc, const struct device *dev, vaf.va = &args;if (dev) { -if (desc->flags && _DPRINTK_FLAGS_PRINT) +if (desc->flags && _DPRINTK_FLAGS_PRINTK)dev_printk (KERN_DEBUG , dev,"[" DRM_NAME ":%ps] %pV" ,__builtin_return_address (0 ), &vaf); }else { -if (desc->flags && _DPRINTK_FLAGS_PRINT) +if (desc->flags && _DPRINTK_FLAGS_PRINTK)printk (KERN_DEBUG "[" DRM_NAME ":%ps] %pV" ,__builtin_return_address (0 ), &vaf); }
include/linux/dynamic_debug.h +6 -4
@@ -32,7 +32,7 @@ struct _ddebug {* writes commands to <debugfs>/dynamic_debug/control */ #define _DPRINTK_FLAGS_NONE 0 -#define _DPRINTK_FLAGS_PRINT (1<<0)/* printk() a message using the format */ +#define _DPRINTK_FLAGS_PRINTK (1 << 0)/* printk() a message using the format */ #define _DPRINTK_FLAGS_INCL_MODNAME (1<<1)#define _DPRINTK_FLAGS_INCL_FUNCNAME (1<<2)#define _DPRINTK_FLAGS_INCL_LINENO (1<<3)
@@ -42,8 +42,10 @@ struct _ddebug { (_DPRINTK_FLAGS_INCL_MODNAME | _DPRINTK_FLAGS_INCL_FUNCNAME |\ _DPRINTK_FLAGS_INCL_LINENO | _DPRINTK_FLAGS_INCL_TID) +#define _DPRINTK_FLAGS_ENABLED _DPRINTK_FLAGS_PRINTK +#if definedDEBUG -#define _DPRINTK_FLAGS_DEFAULT _DPRINTK_FLAGS_PRINT +#define _DPRINTK_FLAGS_DEFAULT _DPRINTK_FLAGS_PRINTK#else #define _DPRINTK_FLAGS_DEFAULT 0#endif
@@ -161,10 +163,10 @@ void __dynamic_ibdev_dbg(struct _ddebug *descriptor,#ifdef DEBUG #define DYNAMIC_DEBUG_BRANCH (descriptor) \ - likely(descriptor.flags & _DPRINTK_FLAGS_PRINT) + likely(descriptor.flags & _DPRINTK_FLAGS_ENABLED)#else #define DYNAMIC_DEBUG_BRANCH (descriptor) \ - unlikely(descriptor.flags & _DPRINTK_FLAGS_PRINT) + unlikely(descriptor.flags & _DPRINTK_FLAGS_ENABLED)#endif #endif /* CONFIG_JUMP_LABEL */
lib/dynamic_debug.c +4 -4
@@ -87,7 +87,7 @@ static inline const char *trim_prefix(const char *path) }static struct {unsigned flag:8 ;char opt_char; } opt_array[] = { - { _DPRINTK_FLAGS_PRINT,'p' }, + { _DPRINTK_FLAGS_PRINTK,'p' }, { _DPRINTK_FLAGS_INCL_MODNAME,'m' }, { _DPRINTK_FLAGS_INCL_FUNCNAME,'f' }, { _DPRINTK_FLAGS_INCL_LINENO,'l' },
@@ -238,10 +238,10 @@ static int ddebug_change(const struct ddebug_query *query,if (newflags == dp->flags)continue ;#ifdef CONFIG_JUMP_LABEL -if (dp->flags & _DPRINTK_FLAGS_PRINT) { -if (!(newflags & _DPRINTK_FLAGS_PRINT)) +if (dp->flags & _DPRINTK_FLAGS_ENABLED) { +if (!(newflags & _DPRINTK_FLAGS_ENABLED))static_branch_disable (&dp->key.dd_key_true); - }else if (newflags & _DPRINTK_FLAGS_PRINT) { + }else if (newflags & _DPRINTK_FLAGS_ENABLED) {static_branch_enable (&dp->key.dd_key_true); }#endif
Signature · 1 line
2.35.3
Jim Cromie
maintainerPATCH v2 24/27 dyndbg: add _DPRINTK_FLAGS_TRACE
In reply to Jim Cromieadd new flag, and OR it into _DPRINTK_FLAGS_ENABLED definition
--- include/linux/dynamic_debug.h | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-)
include/linux/dynamic_debug.h +3 -1
@@ -42,7 +42,9 @@ struct _ddebug { (_DPRINTK_FLAGS_INCL_MODNAME | _DPRINTK_FLAGS_INCL_FUNCNAME |\ _DPRINTK_FLAGS_INCL_LINENO | _DPRINTK_FLAGS_INCL_TID) -#define _DPRINTK_FLAGS_ENABLED _DPRINTK_FLAGS_PRINTK +#define _DPRINTK_FLAGS_TRACE (1 << 5) +#define _DPRINTK_FLAGS_ENABLED (_DPRINTK_FLAGS_PRINTK | \ + _DPRINTK_FLAGS_TRACE)#if definedDEBUG #define _DPRINTK_FLAGS_DEFAULT _DPRINTK_FLAGS_PRINTK
Signature · 1 line
2.35.3
Jim Cromie
maintainerPATCH v2 25/27 dyndbg: add write-events-to-tracefs code
In reply to Jim Cromieadds: ddebug_trace()
uses trace_console() temporarily to issue printk:console event uses internal-ish __ftrace_trace_stack code:
4-context buffer stack, barriers per Steve Rostedt
call it from new funcs:
ddebug_printk() - print to both syslog/tracefs ddebug_dev_printk() - dev-print to both syslog/tracefs
These handle both _DPRINTK_FLAGS_PRINTK and _DPRINTK_FLAGS_TRACE cases, allowing to vsnprintf the message once and use it for both, skipping past the KERN_DEBUG character for tracing.
Finally, adjust the callers: __ddebug_{pr_debug,{,net,ib}dev_dbg}, replacing printk and dev_printk with the new funcs above.
The _DPRINTK_FLAGS_TRACE flag character is 'T', so the following finds all callsites enabled for tracing:
grep -P =p?T /proc/dynamic_debug/control
This patch,~1,~2 are basically copies of:
https://lore.kernel.org/lkml/[email protected]/
with a few differences:
- s/dynamic_/ddebug_/ on Vincent's additions
- __printf attrs on the _printk funcs
- reuses trace_console() event, not adding a new "printk:dyndbg" event. next patch replaces this with 2 new events
--- .../admin-guide/dynamic-debug-howto.rst | 1 + drivers/gpu/drm/drm_print.c | 4 +- lib/dynamic_debug.c | 156 +++++++++++++++--- 3 files changed, 133 insertions(+), 28 deletions(-)
Documentation/admin-guide/dynamic-debug-howto.rst +1 -0
@@ -239,6 +239,7 @@ of the characters:: The flags are:: p enables the pr_debug() callsite. + T enables callsite to issue a dyndbg:* trace-event f Include the function name in the printed message l Include line number in the printed message m Include module name in the printed message
drivers/gpu/drm/drm_print.c +2 -2
@@ -280,11 +280,11 @@ void __drm_dev_dbg(struct _ddebug *desc, const struct device *dev, vaf.va = &args;if (dev) { -if (desc->flags && _DPRINTK_FLAGS_PRINTK) +if (desc->flags & _DPRINTK_FLAGS_PRINTK)dev_printk (KERN_DEBUG , dev,"[" DRM_NAME ":%ps] %pV" ,__builtin_return_address (0 ), &vaf); }else { -if (desc->flags && _DPRINTK_FLAGS_PRINTK) +if (desc->flags & _DPRINTK_FLAGS_PRINTK)printk (KERN_DEBUG "[" DRM_NAME ":%ps] %pV" ,__builtin_return_address (0 ), &vaf); }
lib/dynamic_debug.c +130 -26
234 lines not on this page · raw message
Signature · 1 line
2.35.3
Jim Cromie
maintainerPATCH v2 26/27 dyndbg: 4 new trace-events: pr_debug, dev_dbg, drm_{,dev}debug
In reply to Jim Cromieddebug_trace() currently issues a single printk:console event. Replace that, adding include/trace/events/dyndbg.h, which defines 2 new events:
- dyndbg:prdbg - from trace_prdbg() - if !dev
- dyndbg:devdbg - from trace_devdbg() - if !!dev
This links the legacy pr_debug API to tracefs, via dyndbg, allowing pr_debug()s etc to add just a little more user-context to the trace-logs, and then at users option, less syslog.
The 2 new trace_*() calls accept their caller's args respectively, keeping the available info w/o alteration; we can't improve on transparency. The args:
1- struct _ddebug *descriptor, giving tracefs all of dyndbg's info. 2- struct device *dev, used by trace_devdbg(), if !!dev
The trace_*() calls need the descriptor arg, the callchain prototypes above them are extended to provide it.
The existing category param in this callchain is partially redundant; when descriptor is available, it has the class_id.
dev_dbg(desc, dev...), if dev is true, issues a trace_devdbg(), otherwise trace_prdbg(). This way we dont consume buffer space storing nulls. Otherwise the events are equivalent.
Also add include/trace/events/drm.h, to create 2 events for use in drm_dbg() and drm_devdbg(), and call them. This recapitulates the changes described above, connecting 3-10K drm.debug callsites to tracefs.
--- drivers/gpu/drm/drm_print.c | 9 +++++ include/trace/events/drm.h | 68 ++++++++++++++++++++++++++++++++ include/trace/events/dyndbg.h | 74 +++++++++++++++++++++++++++++++++++ lib/dynamic_debug.c | 73 +++++++++++++++++----------------- 4 files changed, 188 insertions(+), 36 deletions(-) create mode 100644 include/trace/events/drm.h create mode 100644 include/trace/events/dyndbg.h
drivers/gpu/drm/drm_print.c +9 -0
@@ -34,6 +34,9 @@#include <drm/drm_drv.h> #include <drm/drm_print.h> +#define CREATE_TRACE_POINTS +#include <trace/events/drm.h> +/* * __drm_debug: Enable debug output. * Bitmask of DRM_UT_x. See include/drm/drm_print.h for details.
@@ -283,10 +286,14 @@ void __drm_dev_dbg(struct _ddebug *desc, const struct device *dev,if (desc->flags & _DPRINTK_FLAGS_PRINTK)dev_printk (KERN_DEBUG , dev,"[" DRM_NAME ":%ps] %pV" ,__builtin_return_address (0 ), &vaf); +if (desc->flags & _DPRINTK_FLAGS_TRACE) +trace_drm_devdbg (dev, category, &vaf); }else {if (desc->flags & _DPRINTK_FLAGS_PRINTK)printk (KERN_DEBUG "[" DRM_NAME ":%ps] %pV" ,__builtin_return_address (0 ), &vaf); +if (desc->flags & _DPRINTK_FLAGS_TRACE) +trace_drm_debug (category, &vaf); }va_end (args); }
@@ -307,6 +314,8 @@ void ___drm_dbg(struct _ddebug *desc, enum drm_debug_category category, const chprintk (KERN_DEBUG "[" DRM_NAME ":%ps] %pV" ,__builtin_return_address (0 ), &vaf); +trace_drm_debug (category, &vaf); +va_end (args); }EXPORT_SYMBOL (___drm_dbg);
include/trace/events/drm.h new file +68 -0
68 lines not on this page · raw message
include/trace/events/dyndbg.h new file +74 -0
74 lines not on this page · raw message
lib/dynamic_debug.c +37 -36
185 lines not on this page · raw message
Signature · 1 line
2.35.3
Steven Rostedt
maintainerRe: [PATCH v2 26/27] dyndbg: 4 new trace-events: pr_debug, dev_dbg, drm_{,dev}debug
Sorry for the late review. I finally got some time to look at this.
Quoted 41 lines · On Mon, 16 May 2022 16:56:39 -0600 Jim Cromie <[email protected]> wrote:
include/trace/events/drm.h new file +35
-0@@ -0,0 +1,68 @@ +/* SPDX-License-Identifier: GPL-2.0 */ +#undef TRACE_SYSTEM +#define TRACE_SYSTEM drm + +#if !defined(_TRACE_DRM_H) || defined(TRACE_HEADER_MULTI_READ ) +#define _TRACE_DRM_H + +#include <linux/tracepoint.h> + +/* drm_debug() was called, pass its args */ +TRACE_EVENT (drm_debug, + TP_PROTO(int drm_debug_category, struct va_format *vaf), + +TP_ARGS (drm_debug_category, vaf), + +TP_STRUCT__entry ( + __field(int, drm_debug_category) +__dynamic_array (char, msg,256 ) + ), + +TP_fast_assign ( + int len; + + __entry->drm_debug_category = drm_debug_category; + vsnprintf(__get_str(msg), 256, vaf->fmt, *vaf->va); + + len = strlen(__get_str(msg)); + if (len > 0 && (__get_str(msg)[len - 1] == '\n')) + len -= 1; + __get_str(msg)[len] = 0; + ), + +TP_printk ("%s" ,__get_str (msg)) +); +
include/trace/events/drm.h line 45
Quoted 10 lines
include/trace/events/drm.h new file +10
-0+/* drm_devdbg() was called, pass its args, preserving order */ +TRACE_EVENT(drm_devdbg, + TP_PROTO(const struct device *dev, int drm_debug_category, struct va_format *vaf), + + TP_ARGS(dev, drm_debug_category, vaf), + + TP_STRUCT__entry( + __field(const struct device*, dev) + __field(int, drm_debug_category) + __dynamic_array(char, msg, 256)
You do not want to hardcode the 256 here. That will cause 256 bytes to be reserved on the buffer, and you will not get that back. Might as well make it a static array, as you also add 4 bytes to for the offset and size.
I think you want (haven't tested it)
__dynamic_array(char, msg, get_msg_size(vaf))
Where you have:
static unsigned int get_msg_size(struct va_format *vaf)
{
va_list aq;
unsigned int ret;
va_copy(aq, vaf->va);
ret = vsnprintf(NULL, 0, vaf->fmt, aq);
va_end(aq);
return min(ret + 1, 256);
}What is in the last parameter of __dynamic_array() is used to calculate the size needed to store the dynamic array.
Hmm, looking at other users of __dynamic_array(), this appears to be a constant problem. I need to document this better.
-- Steve
Quoted 21 lines
include/trace/events/drm.h new file +21
-0+ ), + +TP_fast_assign ( + int len; + + __entry->drm_debug_category = drm_debug_category; + __entry->dev = dev; +vsnprintf (__get_str (msg),256 , vaf->fmt, *vaf->va); + + len =strlen (__get_str (msg)); +if (len >0 && (__get_str (msg)[len -1 ] =='\n' )) + len -=1 ; +__get_str (msg)[len] =0 ; + ), + +TP_printk ("cat:%d, %s %s" , __entry->drm_debug_category, +dev_name (__entry->dev),__get_str (msg)) +); + +#endif /* _TRACE_DRM_H */ +
Jim Cromie
maintainerPATCH v2 27/27 dyndbg/drm: POC add tracebits sysfs-knob
In reply to Jim Cromieclone DRM.debug interface to DRM.tracebits: ie map bits to drm-debug-categories, except this interface enables messages to tracefs, not to syslog.
This reuses dyndbg's register-classes API to add the new sysfs-knob:
drm_drv.h:
[A] 2nd use of DYNAMIC_DEBUG_CLASSES(drm_trace_classes), which declares and initializes a known-classes map with the same literal classnames as in the 1st use. This "shares" the classnames for both sysfs-knobs, which is necessary because they're manipulating a shared dyndbg callsite, toggling "p" and "T" flags respectively.
This incurs a tiny waste of constant strings, but its worth it for the simpler declarative macro.
drm_print.c:
1- declare and export a 2nd bit-vector: __drm_trace, like __drm_debug
2- declare and init a struct ddebug_classes_bitmap_param with:
__drm_trace [1], drm_trace_classes [A].
3- module_param_cb([2]) - does the sysfs part
drm_drv.c:
register and unregister [A], and missed unregister on drm_debug_classes.
--- drivers/gpu/drm/drm_drv.c | 3 +++ drivers/gpu/drm/drm_print.c | 10 ++++++++++ include/drm/drm_drv.h | 14 +++++++++++++- 3 files changed, 26 insertions(+), 1 deletion(-)
drivers/gpu/drm/drm_drv.c +3 -0
@@ -1039,6 +1039,8 @@ static void drm_core_exit(void)drm_sysfs_destroy ();idr_destroy (&drm_minors_idr);drm_connector_ida_destroy (); +dynamic_debug_unregister_classes (&drm_debug_classes); +dynamic_debug_unregister_classes (&drm_trace_classes); }static int __init drm_core_init (void )
@@ -1046,6 +1048,7 @@ static int __init drm_core_init(void)int ret;dynamic_debug_register_classes (&drm_debug_classes); +dynamic_debug_register_classes (&drm_trace_classes);drm_connector_ida_init ();idr_init (&drm_minors_idr);
drivers/gpu/drm/drm_print.c +10 -0
@@ -44,6 +44,9 @@unsigned long __drm_debug;EXPORT_SYMBOL (__drm_debug); +unsigned long __drm_trace; +EXPORT_SYMBOL (__drm_trace); +MODULE_PARM_DESC (debug,"Enable debug output, where each bit enables a debug category.\n" "\t\tBit 0 (0x01) will enable CORE messages (drm core code)\n" "\t\tBit 1 (0x02) will enable DRIVER messages (drm controller code)\n"
@@ -63,6 +66,13 @@ static struct ddebug_classes_bitmap_param drm_debug_bitmap = { .map = &drm_debug_classes, };module_param_cb (debug, ¶m_ops_dyndbg_classes, &drm_debug_bitmap,0600 ); + +static struct ddebug_classes_bitmap_param drm_trace_bitmap = { + .bits = &__drm_trace, + .flags ="T" , + .map = &drm_trace_classes, +}; +module_param_cb (tracecats, ¶m_ops_dyndbg_classes, &drm_trace_bitmap,0600 );#endif void __drm_puts_coredump (struct drm_printer *p,const char *str)
include/drm/drm_drv.h +13 -1
@@ -45,7 +45,19 @@ struct drm_printer;struct sg_table ;/* these must comport with enum drm_debug_category values */ -DYNAMIC_DEBUG_CLASSES(drm_debug_classes, "*", 0, +DYNAMIC_DEBUG_CLASSES (drm_debug_classes,0 , +"DRM_UT_CORE" , +"DRM_UT_DRIVER" , +"DRM_UT_KMS" , +"DRM_UT_PRIME" , +"DRM_UT_ATOMIC" , +"DRM_UT_VBL" , +"DRM_UT_STATE" , +"DRM_UT_LEASE" , +"DRM_UT_DP" , +"DRM_UT_DRMRES" ); + +DYNAMIC_DEBUG_CLASSES(drm_trace_classes, 0, "DRM_UT_CORE", "DRM_UT_DRIVER", "DRM_UT_KMS",
Signature · 1 line
2.35.3
Patchwork
CI[Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for DRM.debug on DYNAMIC_DEBUG, add trace events
In reply to Jim Cromie== Series Details ==
== Series Details ==
Series: DRM.debug on DYNAMIC_DEBUG, add trace events
URL : https://patchwork.freedesktop.org/series/104052/
State : warning
== Summary ==
Error: dim checkpatch failed9b925049d3f8 dyndbg: fix static_branch manipulation7a33c56c8d24 dyndbg: show both old and new in change-info 3838cafa7f32 dyndbg: fix module.dyndbg handlingd0c698a826fb dyndbg: drop EXPORTed dynamic_debug_exec_queries 323eeca8bd78 dyndbg: add exclusive class_id to pr_debug callsites -:85: CHECK:MACRO_ARG_REUSE: Macro argument reuse 'id' - possible side-effects? #85: FILE: include/linux/dynamic_debug.h:139:
+#define __dynamic_func_call_cls(id, cls, fmt, func, ...) do { \
+ DEFINE_DYNAMIC_DEBUG_METADATA_CLS(id, cls, fmt); \
+ if (DYNAMIC_DEBUG_BRANCH(id)) \
+ func(&id, ##__VA_ARGS__); \
} while (0)
-:95: CHECK:MACRO_ARG_REUSE: Macro argument reuse 'id' - possible side-effects? #95: FILE: include/linux/dynamic_debug.h:145:
+#define __dynamic_func_call_no_desc_cls(id, cls, fmt, func, ...) do { \
+ DEFINE_DYNAMIC_DEBUG_METADATA_CLS(id, cls, fmt); \
+ if (DYNAMIC_DEBUG_BRANCH(id)) \
+ func(__VA_ARGS__); \
} while (0)
total: 0 errors, 0 warnings, 2 checks, 101 lines checked b00e307b0e6c dyndbg: add dynamic_debug_(un)register_classes 1dbc3121df14 dyndbg: validate class FOO on module 0444535e4efd dyndbg: add drm.debug style bitmap support -:135: CHECK:BRACES: Blank lines aren't necessary after an open brace '{' #135: FILE: lib/dynamic_debug.c:646:
+ for (i = 0; i < dcp->map->length; i++) {
+
total: 0 errors, 0 warnings, 1 checks, 122 lines checked 100ca6d47784 Doc/dyndbg: document new class class_name query support 8a28855c36d5 dyndbg: let query-modname override defaulting modname da5aa3351514 dyndbg: support symbolic class-names in bitmap 7ef98167d65f dyndbg: change zero-or-one classes-map to maps list b9a15e133de2 dyndbg: add __pr_debug_cls(class, fmt, ...)
-:26: CHECK:MACRO_ARG_REUSE: Macro argument reuse 'fmt' - possible side-effects? #26: FILE: include/linux/dynamic_debug.h:219:
+#define dynamic_pr_debug_cls(cls, fmt, ...) \
+ _dynamic_func_call_cls(cls, fmt, __dynamic_pr_debug, \
+ pr_fmt(fmt), ##__VA_ARGS__)
total: 0 errors, 0 warnings, 1 checks, 19 lines checked488ac7361b58 dyndbg: add test_dynamic_debug module
Traceback (most recent call last):
File "scripts/spdxcheck.py", line 10, in <module>
import git
ModuleNotFoundError: No module named 'git'
-:98: WARNING:FILE_PATH_CHANGES: added, moved or deleted file(s), does MAINTAINERS need updating? #98:
new file mode 100644
-:160: WARNING:EXPORT_SYMBOL: EXPORT_SYMBOL(foo); should immediately follow its function/variable #160: FILE: lib/test_dynamic_debug.c:58:
+EXPORT_SYMBOL(bits_1p);
-:161: WARNING:EXPORT_SYMBOL: EXPORT_SYMBOL(foo); should immediately follow its function/variable #161: FILE: lib/test_dynamic_debug.c:59:
+EXPORT_SYMBOL(bits_1t);
-:177: CHECK:LINE_SPACING: Please don't use multiple blank lines #177: FILE: lib/test_dynamic_debug.c:75:
+
+
-:178: CHECK:CAMELCASE: Avoid CamelCase: <Foo>
#178: FILE: lib/test_dynamic_debug.c:76:
+enum cat2 { Foo = 8, Bar, Buzz };
-:178: CHECK:CAMELCASE: Avoid CamelCase: <Bar>
#178: FILE: lib/test_dynamic_debug.c:76:
+enum cat2 { Foo = 8, Bar, Buzz };
-:178: CHECK:CAMELCASE: Avoid CamelCase: <Buzz>
#178: FILE: lib/test_dynamic_debug.c:76:
+enum cat2 { Foo = 8, Bar, Buzz };
-:183: WARNING:EXPORT_SYMBOL: EXPORT_SYMBOL(foo); should immediately follow its function/variable #183: FILE: lib/test_dynamic_debug.c:81:
+EXPORT_SYMBOL(bits_2p);
-:184: WARNING:EXPORT_SYMBOL: EXPORT_SYMBOL(foo); should immediately follow its function/variable #184: FILE: lib/test_dynamic_debug.c:82:
+EXPORT_SYMBOL(bits_2t);
-:200: CHECK:LINE_SPACING: Please don't use multiple blank lines #200: FILE: lib/test_dynamic_debug.c:98:
+
+
-:206: WARNING:EXPORT_SYMBOL: EXPORT_SYMBOL(foo); should immediately follow its function/variable #206: FILE: lib/test_dynamic_debug.c:104:
+EXPORT_SYMBOL(bits_3p);
-:207: WARNING:EXPORT_SYMBOL: EXPORT_SYMBOL(foo); should immediately follow its function/variable #207: FILE: lib/test_dynamic_debug.c:105:
+EXPORT_SYMBOL(bits_3t);
total: 0 errors, 7 warnings, 5 checks, 203 lines checked1fca523c7a63 drm: POC drm on dyndbg - map class-names to drm_debug_category's -:97: CHECK:LINE_SPACING: Please use a blank line after function/struct/union/enum declarations #97: FILE: drivers/gpu/drm/i915/i915_module.c:51:
+}
+static void i915_ddebug_classes_unregister(void)
total: 0 errors, 0 warnings, 1 checks, 96 lines checked 2f8b28f3616e drm/print: POC drm on dyndbg - use bitmap 062c73ac0661 drm_print: condense enum drm_debug_category 7699f77d2bfc drm_print: interpose drm_*dbg with forwarding macros -:80: CHECK:PARENTHESIS_ALIGNMENT: Alignment should match open parenthesis #80: FILE: include/drm/drm_print.h:343:
+void __drm_dev_dbg(const struct device *dev, enum drm_debug_category category,
const char *format, ...);
total: 0 errors, 0 warnings, 1 checks, 59 lines checked cf749a29838e drm_print: wrap drm_*_dbg in dyndbg descriptor factory macro -:83: CHECK:MACRO_ARG_REUSE: Macro argument reuse 'fmt' - possible side-effects? #83: FILE: include/drm/drm_print.h:395:
+#define drm_dev_dbg(dev, cat, fmt, ...) \
+ _dynamic_func_call_no_desc(fmt, __drm_dev_dbg, \
+ dev, cat, fmt, ##__VA_ARGS__)
-:97: CHECK:MACRO_ARG_REUSE: Macro argument reuse 'fmt' - possible side-effects? #97: FILE: include/drm/drm_print.h:508:
+#define __drm_dbg(cat, fmt, ...) \
+ _dynamic_func_call_no_desc(fmt, ___drm_dbg, \
+ cat, fmt, ##__VA_ARGS__)
total: 0 errors, 0 warnings, 2 checks, 61 lines checked06823fbcf6b5 drm_print: refine drm_debug_enabled for jump-label135cac4ddf6d drm_print: prefer bare printk KERN_DEBUG on generic fn
-:49: WARNING:PREFER_PR_LEVEL: Prefer [subsystem eg: netdev]_dbg([subsystem]dev, ... then dev_dbg(dev, ... then pr_debug(... to printk(KERN_DEBUG ... #49: FILE: drivers/gpu/drm/drm_print.c:174:
+ printk(KERN_DEBUG "%s %pV", p->prefix, vaf);
total: 0 errors, 1 warnings, 0 checks, 17 lines checked 0f9de5bc809f drm_print: add _ddebug desc to drm_*dbg prototypes -:56: WARNING:PREFER_DEV_LEVEL: Prefer dev_dbg(... to dev_printk(KERN_DEBUG, ... #56: FILE: drivers/gpu/drm/drm_print.c:284:
+ dev_printk(KERN_DEBUG, dev, "[" DRM_NAME ":%ps] %pV",
-:60: WARNING:PREFER_PR_LEVEL: Prefer [subsystem eg: netdev]_dbg([subsystem]dev, ... then dev_dbg(dev, ... then pr_debug(... to printk(KERN_DEBUG ... #60: FILE: drivers/gpu/drm/drm_print.c:288:
+ printk(KERN_DEBUG "[" DRM_NAME ":%ps] %pV",
total: 0 errors, 2 warnings, 0 checks, 91 lines checked2962dd40ded0 dyndbg: add _DPRINTK_FLAGS_ENABLEDa94e9b4c4296 dyndbg: add _DPRINTK_FLAGS_TRACE4cfbc43dc308 dyndbg: add write-events-to-tracefs code
-:28: WARNING:COMMIT_LOG_LONG_LINE: Possible unwrapped commit description (prefer a maximum 75 chars per line) #28:
https://lore.kernel.org/lkml/[email protected]/
-:168: CHECK:BRACES: Blank lines aren't necessary after an open brace '{' #168: FILE: lib/dynamic_debug.c:849:
+{
+
-:259: CHECK:PARENTHESIS_ALIGNMENT: Alignment should match open parenthesis #259: FILE: lib/dynamic_debug.c:942:
+ ddebug_dev_printk(flags, dev->dev.parent,
+ "%s%s %s %s%s: %pV",
-:269: CHECK:PARENTHESIS_ALIGNMENT: Alignment should match open parenthesis #269: FILE: lib/dynamic_debug.c:950:
+ ddebug_printk(flags, KERN_DEBUG "%s%s: %pV",
+ netdev_name(dev), netdev_reg_state(dev), &vaf);
-:273: CHECK:PARENTHESIS_ALIGNMENT: Alignment should match open parenthesis #273: FILE: lib/dynamic_debug.c:953:
+ ddebug_printk(flags, KERN_DEBUG "(NULL net_device): %pV",
+ &vaf);
total: 0 errors, 1 warnings, 4 checks, 254 lines checkedd7e672d096dc dyndbg: 4 new trace-events: pr_debug, dev_dbg, drm_{, dev}debug Traceback (most recent call last):
File "scripts/spdxcheck.py", line 10, in <module>
import git
ModuleNotFoundError: No module named 'git'
Traceback (most recent call last):
File "scripts/spdxcheck.py", line 10, in <module>
import git
ModuleNotFoundError: No module named 'git'
-:81: WARNING:FILE_PATH_CHANGES: added, moved or deleted file(s), does MAINTAINERS need updating? #81:
new file mode 100644
-:101: CHECK:OPEN_ENDED_LINE: Lines should not end with a '(' #101: FILE: include/trace/events/drm.h:16:
+ TP_STRUCT__entry(
-:106: CHECK:OPEN_ENDED_LINE: Lines should not end with a '(' #106: FILE: include/trace/events/drm.h:21:
+ TP_fast_assign(
-:107: WARNING:TABSTOP: Statements should start on a tabstop #107: FILE: include/trace/events/drm.h:22:
+ int len;
-:113: WARNING:TABSTOP: Statements should start on a tabstop #113: FILE: include/trace/events/drm.h:28:
+ if (len > 0 && (__get_str(msg)[len - 1] == '\n'))
-:113: WARNING:SUSPECT_CODE_INDENT: suspect code indent for conditional statements (20, 28) #113: FILE: include/trace/events/drm.h:28:
+ if (len > 0 && (__get_str(msg)[len - 1] == '\n'))
+ len -= 1;
-:127: CHECK:OPEN_ENDED_LINE: Lines should not end with a '(' #127: FILE: include/trace/events/drm.h:42:
+ TP_STRUCT__entry(
-:133: CHECK:OPEN_ENDED_LINE: Lines should not end with a '(' #133: FILE: include/trace/events/drm.h:48:
+ TP_fast_assign(
-:134: WARNING:TABSTOP: Statements should start on a tabstop #134: FILE: include/trace/events/drm.h:49:
+ int len;
-:141: WARNING:TABSTOP: Statements should start on a tabstop #141: FILE: include/trace/events/drm.h:56:
+ if (len > 0 && (__get_str(msg)[len - 1] == '\n'))
-:141: WARNING:SUSPECT_CODE_INDENT: suspect code indent for conditional statements (20, 28) #141: FILE: include/trace/events/drm.h:56:
+ if (len > 0 && (__get_str(msg)[len - 1] == '\n'))
+ len -= 1;
-:175: CHECK:OPEN_ENDED_LINE: Lines should not end with a '(' #175: FILE: include/trace/events/dyndbg.h:16:
+ TP_STRUCT__entry(
-:180: CHECK:OPEN_ENDED_LINE: Lines should not end with a '(' #180: FILE: include/trace/events/dyndbg.h:21:
+ TP_fast_assign(
-:187: WARNING:TABSTOP: Statements should start on a tabstop #187: FILE: include/trace/events/dyndbg.h:28:
+ if (len > 0 && (text[len - 1] == '\n'))
-:187: WARNING:SUSPECT_CODE_INDENT: suspect code indent for conditional statements (20, 28) #187: FILE: include/trace/events/dyndbg.h:28:
+ if (len > 0 && (text[len - 1] == '\n'))
+ len -= 1;
-:205: CHECK:OPEN_ENDED_LINE: Lines should not end with a '(' #205: FILE: include/trace/events/dyndbg.h:46:
+ TP_STRUCT__entry(
-:211: CHECK:OPEN_ENDED_LINE: Lines should not end with a '(' #211: FILE: include/trace/events/dyndbg.h:52:
+ TP_fast_assign(
-:213: CHECK:SPACING: No space is necessary after a cast #213: FILE: include/trace/events/dyndbg.h:54:
+ __entry->dev = (struct device *) dev;
-:219: WARNING:TABSTOP: Statements should start on a tabstop #219: FILE: include/trace/events/dyndbg.h:60:
+ if (len > 0 && (text[len - 1] == '\n'))
-:219: WARNING:SUSPECT_CODE_INDENT: suspect code indent for conditional statements (20, 28) #219: FILE: include/trace/events/dyndbg.h:60:
+ if (len > 0 && (text[len - 1] == '\n'))
+ len -= 1;
-:350: CHECK:PARENTHESIS_ALIGNMENT: Alignment should match open parenthesis #350: FILE: lib/dynamic_debug.c:912:
+ ddebug_printk(descriptor, KERN_DEBUG "(NULL device *): %pV",
+ &vaf);
total: 0 errors, 11 warnings, 10 checks, 358 lines checked 52b67f942764 dyndbg/drm: POC add tracebits sysfs-knob
Patchwork
CI[Intel-gfx] ✗ Fi.CI.SPARSE: warning for DRM.debug on DYNAMIC_DEBUG, add trace events
In reply to Jim Cromie== Series Details ==
== Series Details ==
Series: DRM.debug on DYNAMIC_DEBUG, add trace events
URL : https://patchwork.freedesktop.org/series/104052/
State : warning
== Summary ==
Error: dim sparse failed
Sparse version: v0.6.2
Fast mode used, each commit won't be checked separately.
Patchwork
CI[Intel-gfx] ✓ Fi.CI.BAT: success for DRM.debug on DYNAMIC_DEBUG, add trace events
In reply to Jim Cromie== Series Details ==
== Series Details ==
Series: DRM.debug on DYNAMIC_DEBUG, add trace events
URL : https://patchwork.freedesktop.org/series/104052/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_11661 -> Patchwork_104052v1
====================================================
Summary
-------
**SUCCESS**
No regressions found.
External URL: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_104052v1/index.html
Participating hosts (42 -> 43)
------------------------------
Additional (2): bat-dg2-8 bat-adlm-1
Missing (1): bat-dg2-9
Known issues
------------
Here are the changes found in Patchwork_104052v1 that come from known issues:
### IGT changes ###
#### Issues hit ####
* igt@i915_selftest@live@gt_pm:
- fi-tgl-1115g4: [PASS][1] -> [DMESG-FAIL][2] ([i915#3987])
[1]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11661/fi-tgl-1115g4/igt@i915_selftest@live@gt_pm.html
[2]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_104052v1/fi-tgl-1115g4/igt@i915_selftest@live@gt_pm.html
* igt@i915_selftest@live@hangcheck:
- fi-bdw-5557u: NOTRUN -> [INCOMPLETE][3] ([i915#3921])
[3]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_104052v1/fi-bdw-5557u/igt@i915_selftest@[email protected]
* igt@kms_chamelium@common-hpd-after-suspend:
- fi-kbl-soraka: NOTRUN -> [SKIP][4] ([fdo#109271] / [fdo#111827])
[4]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_104052v1/fi-kbl-soraka/igt@[email protected]
- bat-dg1-6: NOTRUN -> [SKIP][5] ([fdo#111827])
[5]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_104052v1/bat-dg1-6/igt@[email protected]
- fi-blb-e6850: NOTRUN -> [SKIP][6] ([fdo#109271])
[6]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_104052v1/fi-blb-e6850/igt@[email protected]
* igt@kms_pipe_crc_basic@suspend-read-crc-pipe-a:
- fi-kbl-soraka: NOTRUN -> [SKIP][7] ([fdo#109271])
[7]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_104052v1/fi-kbl-soraka/igt@[email protected]
#### Possible fixes ####
* igt@i915_selftest@live@gt_engines:
- bat-dg1-6: [INCOMPLETE][8] ([i915#4418]) -> [PASS][9]
[8]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11661/bat-dg1-6/igt@i915_selftest@live@gt_engines.html
[9]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_104052v1/bat-dg1-6/igt@i915_selftest@live@gt_engines.html
* igt@i915_selftest@live@gtt:
- fi-bdw-5557u: [INCOMPLETE][10] ([i915#5685]) -> [PASS][11]
[10]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11661/fi-bdw-5557u/igt@i915_selftest@[email protected]
[11]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_104052v1/fi-bdw-5557u/igt@i915_selftest@[email protected]
* igt@i915_selftest@live@requests:
- fi-blb-e6850: [DMESG-FAIL][12] ([i915#4528]) -> [PASS][13]
[12]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11661/fi-blb-e6850/igt@i915_selftest@[email protected]
[13]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_104052v1/fi-blb-e6850/igt@i915_selftest@[email protected]
* igt@kms_busy@basic@flip:
- {bat-adlp-6}: [DMESG-WARN][14] ([i915#3576]) -> [PASS][15] +1 similar issue
[14]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11661/bat-adlp-6/igt@kms_busy@[email protected]
[15]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_104052v1/bat-adlp-6/igt@kms_busy@[email protected]
* igt@kms_busy@basic@modeset:
- bat-adlp-4: [DMESG-WARN][16] ([i915#3576]) -> [PASS][17] +2 similar issues
[16]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11661/bat-adlp-4/igt@kms_busy@[email protected]
[17]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_104052v1/bat-adlp-4/igt@kms_busy@[email protected]
{name}: This element is suppressed. This means it is ignored when computing
the status of the difference (SUCCESS, WARNING, or FAILURE).
[fdo#109271]: https://bugs.freedesktop.org/show_bug.cgi?id=109271
[fdo#109285]: https://bugs.freedesktop.org/show_bug.cgi?id=109285
[fdo#111827]: https://bugs.freedesktop.org/show_bug.cgi?id=111827
[i915#1072]: https://gitlab.freedesktop.org/drm/intel/issues/1072
[i915#1155]: https://gitlab.freedesktop.org/drm/intel/issues/1155
[i915#2582]: https://gitlab.freedesktop.org/drm/intel/issues/2582
[i915#3282]: https://gitlab.freedesktop.org/drm/intel/issues/3282
[i915#3291]: https://gitlab.freedesktop.org/drm/intel/issues/3291
[i915#3547]: https://gitlab.freedesktop.org/drm/intel/issues/3547
[i915#3555]: https://gitlab.freedesktop.org/drm/intel/issues/3555
[i915#3576]: https://gitlab.freedesktop.org/drm/intel/issues/3576
[i915#3595]: https://gitlab.freedesktop.org/drm/intel/issues/3595
[i915#3708]: https://gitlab.freedesktop.org/drm/intel/issues/3708
[i915#3921]: https://gitlab.freedesktop.org/drm/intel/issues/3921
[i915#3987]: https://gitlab.freedesktop.org/drm/intel/issues/3987
[i915#4077]: https://gitlab.freedesktop.org/drm/intel/issues/4077
[i915#4079]: https://gitlab.freedesktop.org/drm/intel/issues/4079
[i915#4083]: https://gitlab.freedesktop.org/drm/intel/issues/4083
[i915#4103]: https://gitlab.freedesktop.org/drm/intel/issues/4103
[i915#4212]: https://gitlab.freedesktop.org/drm/intel/issues/4212
[i915#4213]: https://gitlab.freedesktop.org/drm/intel/issues/4213
[i915#4215]: https://gitlab.freedesktop.org/drm/intel/issues/4215
[i915#4312]: https://gitlab.freedesktop.org/drm/intel/issues/4312
[i915#4418]: https://gitlab.freedesktop.org/drm/intel/issues/4418
[i915#4528]: https://gitlab.freedesktop.org/drm/intel/issues/4528
[i915#4579]: https://gitlab.freedesktop.org/drm/intel/issues/4579
[i915#4613]: https://gitlab.freedesktop.org/drm/intel/issues/4613
[i915#4873]: https://gitlab.freedesktop.org/drm/intel/issues/4873
[i915#5190]: https://gitlab.freedesktop.org/drm/intel/issues/5190
[i915#5274]: https://gitlab.freedesktop.org/drm/intel/issues/5274
[i915#5354]: https://gitlab.freedesktop.org/drm/intel/issues/5354
[i915#5685]: https://gitlab.freedesktop.org/drm/intel/issues/5685
[i915#5763]: https://gitlab.freedesktop.org/drm/intel/issues/5763
[i915#5801]: https://gitlab.freedesktop.org/drm/intel/issues/5801
[i915#5879]: https://gitlab.freedesktop.org/drm/intel/issues/5879
[i915#5885]: https://gitlab.freedesktop.org/drm/intel/issues/5885
Build changes
-------------
* Linux: CI_DRM_11661 -> Patchwork_104052v1
CI-20190529: 20190529
CI_DRM_11661: f0d63dbb9c4ebcb646fd41c0e810d60ff7c7d11e @ git://anongit.freedesktop.org/gfx-ci/linux
IGT_6473: 64723cd44c1cd2f8b8263e3b3681c99f05a1b499 @ https://gitlab.freedesktop.org/drm/igt-gpu-tools.git
Patchwork_104052v1: f0d63dbb9c4ebcb646fd41c0e810d60ff7c7d11e @ git://anongit.freedesktop.org/gfx-ci/linux
### Linux commits
8b6d0399d99f dyndbg/drm: POC add tracebits sysfs-knob 39b62567ffd7 dyndbg: 4 new trace-events: pr_debug, dev_dbg, drm_{, dev}debug d29e003c5bd0 dyndbg: add write-events-to-tracefs code 1ce22bfdc3d3 dyndbg: add _DPRINTK_FLAGS_TRACEbdd1228bf40d dyndbg: add _DPRINTK_FLAGS_ENABLEDc41c1d35cd45 drm_print: add _ddebug desc to drm_*dbg prototypes d07bc397ae96 drm_print: prefer bare printk KERN_DEBUG on generic fn 4e1dfab0aa21 drm_print: refine drm_debug_enabled for jump-label c5c3f788ed01 drm_print: wrap drm_*_dbg in dyndbg descriptor factory macro c81add96aef7 drm_print: interpose drm_*dbg with forwarding macros 77b7c8a163d7 drm_print: condense enum drm_debug_category 451972407ce3 drm/print: POC drm on dyndbg - use bitmap 6a72203b2856 drm: POC drm on dyndbg - map class-names to drm_debug_category's 9f6de83719fb dyndbg: add test_dynamic_debug moduleb60310dbe0f0 dyndbg: add __pr_debug_cls(class, fmt, ...) 8ea9abcec80d dyndbg: change zero-or-one classes-map to maps list 46f0b5eaae3a dyndbg: support symbolic class-names in bitmap 0855101f32ae dyndbg: let query-modname override defaulting modname 0bdf97041b98 Doc/dyndbg: document new class class_name query support a4972715ab78 dyndbg: add drm.debug style bitmap support 4b24bd57ae91 dyndbg: validate class FOO on moduled43324ae48d0 dyndbg: add dynamic_debug_(un)register_classes 8756d8e1dc31 dyndbg: add exclusive class_id to pr_debug callsites 27c4cda19231 dyndbg: drop EXPORTed dynamic_debug_exec_queries b86966e95441 dyndbg: fix module.dyndbg handling6c6e62c28eb6 dyndbg: show both old and new in change-info 88d7a0414164 dyndbg: fix static_branch manipulation
== Logs ==
For more details see: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_104052v1/index.html
Patchwork
CI[Intel-gfx] ✗ Fi.CI.IGT: failure for DRM.debug on DYNAMIC_DEBUG, add trace events
In reply to Jim Cromie== Series Details ==
== Series Details ==
Series: DRM.debug on DYNAMIC_DEBUG, add trace events
URL : https://patchwork.freedesktop.org/series/104052/
State : failure
== Summary ==
CI Bug Log - changes from CI_DRM_11661_full -> Patchwork_104052v1_full
====================================================
Summary
-------
**FAILURE**
Serious unknown changes coming with Patchwork_104052v1_full absolutely need to be verified manually.
If you think the reported changes have nothing to do with the changes introduced in Patchwork_104052v1_full, please notify your bug team to allow them to document this new failure mode, which will reduce false positives in CI.
Participating hosts (13 -> 13)
------------------------------
No changes in participating hosts
Possible new issues
-------------------
Here are the unknown changes that may have been introduced in Patchwork_104052v1_full:
### IGT changes ###
#### Possible regressions ####
* igt@i915_pm_dc@dc9-dpms:
- shard-skl: NOTRUN -> [FAIL][1]
[1]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_104052v1/shard-skl9/igt@[email protected]
* {igt@kms_concurrent@pipe-b@hdmi-a-3} (NEW):
- {shard-dg1}: NOTRUN -> [CRASH][2]
[2]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_104052v1/shard-dg1-18/igt@kms_concurrent@[email protected]
#### Suppressed ####
The following results come from untrusted machines, tests, or statuses. They do not affect the overall result.
* igt@api_intel_allocator@two-level-inception:
- {shard-rkl}: [PASS][3] -> ([DMESG-WARN][4], [PASS][5])
[3]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11661/shard-rkl-1/igt@[email protected]
[4]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_104052v1/shard-rkl-5/igt@[email protected]
[5]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_104052v1/shard-rkl-4/igt@[email protected]
* igt@gem_exec_whisper@basic-fds-priority-all:
- {shard-tglu}: [PASS][6] -> [INCOMPLETE][7]
[6]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11661/shard-tglu-2/igt@[email protected]
[7]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_104052v1/shard-tglu-4/igt@[email protected]
New tests
---------
New tests have been introduced between CI_DRM_11661_full and Patchwork_104052v1_full:
### New IGT tests (6) ###
* igt@kms_concurrent@pipe-b@hdmi-a-3:
- Statuses : 1 crash(s)
- Exec time: [0.03] s
* igt@kms_flip@flip-vs-modeset-vs-hang@d-hdmi-a3:
- Statuses : 1 pass(s)
- Exec time: [30.02] s
* igt@kms_plane_scaling@invalid-num-scalers@pipe-a-hdmi-a-3-invalid-num-scalers:
- Statuses : 1 pass(s)
- Exec time: [0.05] s
* igt@kms_plane_scaling@invalid-num-scalers@pipe-b-hdmi-a-3-invalid-num-scalers:
- Statuses : 1 pass(s)
- Exec time: [0.02] s
* igt@kms_plane_scaling@invalid-num-scalers@pipe-c-hdmi-a-3-invalid-num-scalers:
- Statuses : 1 pass(s)
- Exec time: [0.02] s
* igt@kms_plane_scaling@invalid-num-scalers@pipe-d-hdmi-a-3-invalid-num-scalers:
- Statuses : 1 pass(s)
- Exec time: [0.02] s
Known issues
------------
Here are the changes found in Patchwork_104052v1_full that come from known issues:
### CI changes ###
#### Possible fixes ####
* boot:
- shard-snb: ([PASS][8], [PASS][9], [PASS][10], [PASS][11], [PASS][12], [PASS][13], [PASS][14], [PASS][15], [PASS][16], [PASS][17], [PASS][18], [PASS][19], [PASS][20], [PASS][21], [FAIL][22], [PASS][23], [PASS][24], [PASS][25], [PASS][26], [PASS][27], [PASS][28], [PASS][29], [PASS][30], [PASS][31], [PASS][32]) ([i915#4338]) -> ([PASS][33], [PASS][34], [PASS][35], [PASS][36], [PASS][37], [PASS][38], [PASS][39], [PASS][40], [PASS][41], [PASS][42], [PASS][43], [PASS][44], [PASS][45], [PASS][46], [PASS][47], [PASS][48], [PASS][49], [PASS][50], [PASS][51], [PASS][52], [PASS][53], [PASS][54], [PASS][55], [PASS][56], [PASS][57])
[8]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11661/shard-snb7/boot.html
[9]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11661/shard-snb7/boot.html
[10]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11661/shard-snb7/boot.html
[11]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11661/shard-snb7/boot.html
[12]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11661/shard-snb7/boot.html
[13]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11661/shard-snb6/boot.html
[14]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11661/shard-snb6/boot.html
[15]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11661/shard-snb6/boot.html
[16]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11661/shard-snb6/boot.html
[17]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11661/shard-snb6/boot.html
[18]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11661/shard-snb5/boot.html
[19]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11661/shard-snb5/boot.html
[20]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11661/shard-snb5/boot.html
[21]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11661/shard-snb5/boot.html
[22]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11661/shard-snb5/boot.html
[23]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11661/shard-snb4/boot.html
[24]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11661/shard-snb4/boot.html
[25]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11661/shard-snb4/boot.html
[26]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11661/shard-snb4/boot.html
[27]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11661/shard-snb2/boot.html
[28]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11661/shard-snb2/boot.html
[29]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11661/shard-snb2/boot.html
[30]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11661/shard-snb2/boot.html
[31]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11661/shard-snb2/boot.html
[32]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11661/shard-snb2/boot.html
[33]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_104052v1/shard-snb7/boot.html
[34]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_104052v1/shard-snb7/boot.html
[35]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_104052v1/shard-snb7/boot.html
[36]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_104052v1/shard-snb7/boot.html
[37]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_104052v1/shard-snb7/boot.html
[38]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_104052v1/shard-snb7/boot.html
[39]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_104052v1/shard-snb6/boot.html
[40]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_104052v1/shard-snb6/boot.html
[41]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_104052v1/shard-snb6/boot.html
[42]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_104052v1/shard-snb6/boot.html
[43]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_104052v1/shard-snb6/boot.html
[44]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_104052v1/shard-snb5/boot.html
[45]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_104052v1/shard-snb5/boot.html
[46]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_104052v1/shard-snb5/boot.html
[47]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_104052v1/shard-snb5/boot.html
[48]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_104052v1/shard-snb5/boot.html
[49]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_104052v1/shard-snb4/boot.html
[50]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_104052v1/shard-snb4/boot.html
[51]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_104052v1/shard-snb4/boot.html
[52]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_104052v1/shard-snb4/boot.html
[53]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_104052v1/shard-snb4/boot.html
[54]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_104052v1/shard-snb2/boot.html
[55]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_104052v1/shard-snb2/boot.html
[56]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_104052v1/shard-snb2/boot.html
[57]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_104052v1/shard-snb2/boot.html
### IGT changes ###
#### Issues hit ####
* igt@gem_ctx_persistence@engines-hostile:
- shard-snb: NOTRUN -> [SKIP][58] ([fdo#109271] / [i915#1099])
[58]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_104052v1/shard-snb6/igt@[email protected]
* igt@gem_eio@unwedge-stress:
- shard-iclb: [PASS][59] -> [TIMEOUT][60] ([i915#3070])
[59]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11661/shard-iclb1/igt@[email protected]
[60]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_104052v1/shard-iclb4/igt@[email protected]
* igt@gem_exec_fair@basic-deadline:
- shard-kbl: [PASS][61] -> [FAIL][62] ([i915#2846])
[61]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11661/shard-kbl6/igt@[email protected]
[62]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_104052v1/shard-kbl1/igt@[email protected]
* igt@gem_exec_fair@basic-pace-share@rcs0:
- shard-tglb: [PASS][63] -> [FAIL][64] ([i915#2842])
[63]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11661/shard-tglb3/igt@gem_exec_fair@[email protected]
[64]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_104052v1/shard-tglb7/igt@gem_exec_fair@[email protected]
* igt@gem_exec_fair@basic-pace@rcs0:
- shard-kbl: [PASS][65] -> [FAIL][66] ([i915#2842]) +3 similar issues
[65]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11661/shard-kbl6/igt@gem_exec_fair@[email protected]
[66]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_104052v1/shard-kbl4/igt@gem_exec_fair@[email protected]
* igt@gem_exec_fair@basic-throttle@rcs0:
- shard-glk: [PASS][67] -> [FAIL][68] ([i915#2842])
[67]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11661/shard-glk5/igt@gem_exec_fair@[email protected]
[68]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_104052v1/shard-glk9/igt@gem_exec_fair@[email protected]
* igt@gem_exec_flush@basic-wb-pro-default:
- shard-snb: [PASS][69] -> [SKIP][70] ([fdo#109271]) +2 similar issues
[69]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11661/shard-snb4/igt@[email protected]
[70]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_104052v1/shard-snb6/igt@[email protected]
* igt@gem_exec_schedule@u-semaphore-user:
- shard-skl: [PASS][71] -> [DMESG-WARN][72] ([i915#1982])
[71]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11661/shard-skl3/igt@[email protected]
[72]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_104052v1/shard-skl7/igt@[email protected]
* igt@gem_lmem_swapping@basic:
- shard-skl: NOTRUN -> [SKIP][73] ([fdo#109271] / [i915#4613])
[73]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_104052v1/shard-skl9/igt@[email protected]
* igt@gem_userptr_blits@dmabuf-sync:
- shard-skl: NOTRUN -> [SKIP][74] ([fdo#109271] / [i915#3323])
[74]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_104052v1/shard-skl9/igt@[email protected]
* igt@i915_hangman@engine-engine-hang:
- shard-snb: NOTRUN -> [SKIP][75] ([fdo#109271]) +83 similar issues
[75]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_104052v1/shard-snb6/igt@[email protected]
* igt@kms_big_fb@x-tiled-max-hw-stride-64bpp-rotate-0-async-flip:
- shard-skl: NOTRUN -> [FAIL][76] ([i915#3743])
[76]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_104052v1/shard-skl9/igt@[email protected]
* igt@kms_big_fb@y-tiled-max-hw-stride-32bpp-rotate-0-async-flip:
- shard-tglb: [PASS][77] -> [FAIL][78] ([i915#3743]) +1 similar issue
[77]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11661/shard-tglb7/igt@[email protected]
[78]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_104052v1/shard-tglb7/igt@[email protected]
* igt@kms_ccs@pipe-b-crc-primary-basic-y_tiled_gen12_rc_ccs_cc:
- shard-skl: NOTRUN -> [SKIP][79] ([fdo#109271] / [i915#3886]) +5 similar issues
[79]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_104052v1/shard-skl9/igt@kms_ccs@pipe-b-crc-primary-basic-y_tiled_gen12_rc_ccs_cc.html
* igt@kms_ccs@pipe-d-crc-sprite-planes-basic-y_tiled_gen12_rc_ccs_cc:
- shard-skl: NOTRUN -> [SKIP][80] ([fdo#109271]) +139 similar issues
[80]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_104052v1/shard-skl8/igt@kms_ccs@pipe-d-crc-sprite-planes-basic-y_tiled_gen12_rc_ccs_cc.html
* igt@kms_color_chamelium@pipe-b-ctm-max:
- shard-skl: NOTRUN -> [SKIP][81] ([fdo#109271] / [fdo#111827]) +9 similar issues
[81]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_104052v1/shard-skl9/igt@[email protected]
* igt@kms_color_chamelium@pipe-b-ctm-negative:
- shard-snb: NOTRUN -> [SKIP][82] ([fdo#109271] / [fdo#111827]) +3 similar issues
[82]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_104052v1/shard-snb6/igt@[email protected]
* igt@kms_cursor_crc@pipe-a-cursor-suspend:
- shard-kbl: [PASS][83] -> [DMESG-WARN][84] ([i915#180]) +7 similar issues
[83]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11661/shard-kbl4/igt@[email protected]
[84]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_104052v1/shard-kbl7/igt@[email protected]
* igt@kms_flip@flip-vs-expired-vblank@c-edp1:
- shard-skl: [PASS][85] -> [FAIL][86] ([i915#79]) +1 similar issue
[85]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11661/shard-skl4/igt@kms_flip@[email protected]
[86]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_104052v1/shard-skl3/igt@kms_flip@[email protected]
* igt@kms_flip@flip-vs-suspend@b-edp1:
- shard-tglb: [PASS][87] -> [DMESG-WARN][88] ([i915#2867])
[87]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11661/shard-tglb5/igt@kms_flip@[email protected]
[88]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_104052v1/shard-tglb8/igt@kms_flip@[email protected]
* igt@kms_flip_scaled_crc@flip-32bpp-ytile-to-32bpp-ytileccs-upscaling:
- shard-glk: [PASS][89] -> [FAIL][90] ([i915#4911])
[89]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11661/shard-glk9/igt@kms_flip_scaled_crc@flip-32bpp-ytile-to-32bpp-ytileccs-upscaling.html
[90]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_104052v1/shard-glk3/igt@kms_flip_scaled_crc@flip-32bpp-ytile-to-32bpp-ytileccs-upscaling.html
* igt@kms_pipe_crc_basic@read-crc-pipe-d:
- shard-skl: NOTRUN -> [SKIP][91] ([fdo#109271] / [i915#533]) +1 similar issue
[91]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_104052v1/shard-skl9/igt@[email protected]
* igt@kms_plane@plane-panning-bottom-right-suspend@pipe-b-planes:
- shard-apl: [PASS][92] -> [DMESG-WARN][93] ([i915#180]) +6 similar issues
[92]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11661/shard-apl2/igt@kms_plane@[email protected]
[93]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_104052v1/shard-apl6/igt@kms_plane@[email protected]
* igt@kms_plane_alpha_blend@pipe-b-alpha-opaque-fb:
- shard-skl: NOTRUN -> [FAIL][94] ([fdo#108145] / [i915#265])
[94]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_104052v1/shard-skl9/igt@[email protected]
* igt@kms_plane_alpha_blend@pipe-c-coverage-7efc:
- shard-skl: [PASS][95] -> [FAIL][96] ([fdo#108145] / [i915#265]) +1 similar issue
[95]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11661/shard-skl3/igt@[email protected]
[96]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_104052v1/shard-skl7/igt@[email protected]
* igt@kms_psr@psr2_sprite_blt:
- shard-iclb: [PASS][97] -> [SKIP][98] ([fdo#109441]) +3 similar issues
[97]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11661/shard-iclb2/igt@kms_psr@psr2_sprite_blt.html
[98]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_104052v1/shard-iclb6/igt@kms_psr@psr2_sprite_blt.html
* igt@perf@polling-parameterized:
- shard-skl: [PASS][99] -> [FAIL][100] ([i915#5639])
[99]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11661/shard-skl10/igt@[email protected]
[100]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_104052v1/shard-skl4/igt@[email protected]
* igt@sysfs_clients@fair-0:
- shard-skl: NOTRUN -> [SKIP][101] ([fdo#109271] / [i915#2994]) +1 similar issue
[101]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_104052v1/shard-skl9/igt@[email protected]
#### Possible fixes ####
* igt@gem_ctx_shared@q-smoketest-all:
- {shard-rkl}: [INCOMPLETE][102] ([i915#5080]) -> [PASS][103]
[102]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11661/shard-rkl-5/igt@[email protected]
[103]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_104052v1/shard-rkl-2/igt@[email protected]
* igt@gem_eio@in-flight-contexts-immediate:
- shard-tglb: [TIMEOUT][104] ([i915#3063]) -> [PASS][105]
[104]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11661/shard-tglb8/igt@[email protected]
[105]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_104052v1/shard-tglb5/igt@[email protected]
- {shard-rkl}: [DMESG-WARN][106] -> [PASS][107]
[106]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11661/shard-rkl-5/igt@[email protected]
[107]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_104052v1/shard-rkl-6/igt@[email protected]
* igt@gem_eio@kms:
- shard-tglb: [FAIL][108] ([i915#5784]) -> [PASS][109]
[108]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11661/shard-tglb8/igt@[email protected]
[109]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_104052v1/shard-tglb6/igt@[email protected]
* igt@gem_exec_fair@basic-none-rrul@rcs0:
- shard-glk: [FAIL][110] ([i915#2842]) -> [PASS][111] +2 similar issues
[110]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11661/shard-glk7/igt@gem_exec_fair@[email protected]
[111]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_104052v1/shard-glk5/igt@gem_exec_fair@[email protected]
* igt@gem_exec_fair@basic-none-share@rcs0:
- shard-iclb: [FAIL][112] ([i915#2842]) -> [PASS][113]
[112]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11661/shard-iclb2/igt@gem_exec_fair@[email protected]
[113]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_104052v1/shard-iclb6/igt@gem_exec_fair@[email protected]
* igt@gem_exec_fair@basic-none-solo@rcs0:
- shard-apl: [FAIL][114] ([i915#2842]) -> [PASS][115] +3 similar issues
[114]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11661/shard-apl4/igt@gem_exec_fair@[email protected]
[115]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_104052v1/shard-apl3/igt@gem_exec_fair@[email protected]
* igt@gem_exec_fair@basic-none@vcs1:
- shard-kbl: [FAIL][116] ([i915#2842]) -> [PASS][117]
[116]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11661/shard-kbl7/igt@gem_exec_fair@[email protected]
[117]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_104052v1/shard-kbl7/igt@gem_exec_fair@[email protected]
* igt@gem_exec_fair@basic-throttle@rcs0:
- shard-iclb: [FAIL][118] ([i915#2849]) -> [PASS][119]
[118]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11661/shard-iclb8/igt@gem_exec_fair@[email protected]
[119]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_104052v1/shard-iclb1/igt@gem_exec_fair@[email protected]
* igt@gem_exec_flush@basic-batch-kernel-default-uc:
- shard-snb: [SKIP][120] ([fdo#109271]) -> [PASS][121] +1 similar issue
[120]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11661/shard-snb6/igt@[email protected]
[121]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_104052v1/shard-snb5/igt@[email protected]
* igt@gem_huc_copy@huc-copy:
- shard-tglb: [SKIP][122] ([i915#2190]) -> [PASS][123]
[122]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11661/shard-tglb6/igt@[email protected]
[123]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_104052v1/shard-tglb1/igt@[email protected]
* igt@gen9_exec_parse@allowed-all:
- shard-skl: [DMESG-WARN][124] ([i915#5566] / [i915#716]) -> [PASS][125]
[124]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11661/shard-skl9/igt@[email protected]
[125]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_104052v1/shard-skl8/igt@[email protected]
* igt@i915_pm_dc@dc6-dpms:
- shard-iclb: [FAIL][126] ([i915#454]) -> [PASS][127]
[126]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11661/shard-iclb3/igt@[email protected]
[127]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_104052v1/shard-iclb5/igt@[email protected]
- shard-skl: [FAIL][128] ([i915#454]) -> [PASS][129] +1 similar issue
[128]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11661/shard-skl1/igt@[email protected]
[129]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_104052v1/shard-skl10/igt@[email protected]
* igt@i915_pm_rpm@modeset-lpsp-stress-no-wait:
- {shard-dg1}: [SKIP][130] ([i915#1397]) -> [PASS][131]
[130]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11661/shard-dg1-18/igt@[email protected]
[131]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_104052v1/shard-dg1-19/igt@[email protected]
* igt@kms_async_flips@alternate-sync-async-flip:
- shard-skl: [FAIL][132] ([i915#2521]) -> [PASS][133]
[132]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11661/shard-skl4/igt@[email protected]
[133]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_104052v1/shard-skl4/igt@[email protected]
* igt@kms_ccs@pipe-b-ccs-on-another-bo-y_tiled_gen12_rc_ccs:
- {shard-rkl}: [SKIP][134] ([i915#1845] / [i915#4098]) -> [PASS][135]
[134]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11661/shard-rkl-5/igt@kms_ccs@pipe-b-ccs-on-another-bo-y_tiled_gen12_rc_ccs.html
[135]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_104052v1/shard-rkl-6/igt@kms_ccs@pipe-b-ccs-on-another-bo-y_tiled_gen12_rc_ccs.html
* igt@kms_cursor_crc@pipe-a-cursor-256x85-onscreen:
- {shard-rkl}: [SKIP][136] ([fdo#112022] / [i915#4070]) -> [PASS][137]
[136]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11661/shard-rkl-5/igt@[email protected]
[137]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_104052v1/shard-rkl-6/igt@[email protected]
* igt@kms_cursor_edge_walk@pipe-a-256x256-top-edge:
- {shard-rkl}: [SKIP][138] ([i915#1849] / [i915#4070] / [i915#4098]) -> [PASS][139] +1 similar issue
[138]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11661/shard-rkl-5/igt@[email protected]
[139]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_104052v1/shard-rkl-6/igt@[email protected]
* igt@kms_cursor_legacy@cursor-vs-flip-atomic-transitions-varying-size:
- shard-skl: [DMESG-WARN][140] ([i915#1982]) -> [PASS][141]
[140]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11661/shard-skl9/igt@kms_cursor_legacy@cursor-vs-flip-atomic-transitions-varying-size.html
[141]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_104052v1/shard-skl8/igt@kms_cursor_legacy@cursor-vs-flip-atomic-transitions-varying-size.html
* igt@kms_cursor_legacy@flip-vs-cursor-atomic-transitions:
- shard-iclb: [FAIL][142] ([i915#2346]) -> [PASS][143]
[142]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11661/shard-iclb7/igt@[email protected]
[143]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_104052v1/shard-iclb2/igt@[email protected]
- shard-skl: [FAIL][144] ([i915#2346]) -> [PASS][145]
[144]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11661/shard-skl8/igt@[email protected]
[145]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_104052v1/shard-skl3/igt@[email protected]
* igt@kms_cursor_legacy@pipe-c-single-bo:
- {shard-rkl}: [SKIP][146] ([i915#4070]) -> [PASS][147]
[146]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11661/shard-rkl-1/igt@[email protected]
[147]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_104052v1/shard-rkl-5/igt@[email protected]
* igt@kms_draw_crc@draw-method-xrgb2101010-blt-ytiled:
- {shard-rkl}: [SKIP][148] ([i915#4098] / [i915#4369]) -> [PASS][149]
[148]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11661/shard-rkl-4/igt@[email protected]
[149]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_104052v1/shard-rkl-6/igt@[email protected]
* igt@kms_draw_crc@draw-method-xrgb2101010-render-untiled:
- {shard-rkl}: [SKIP][150] ([fdo#111314] / [i915#4098] / [i915#4369]) -> [PASS][151]
[150]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11661/shard-rkl-5/igt@[email protected]
[151]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_104052v1/shard-rkl-6/igt@[email protected]
* igt@kms_flip@flip-vs-expired-vblank-interruptible@c-hdmi-a1:
- shard-glk: [FAIL][152] ([i915#79]) -> [PASS][153]
[152]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11661/shard-glk6/igt@kms_flip@[email protected]
[153]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_104052v1/shard-glk7/igt@kms_flip@[email protected]
* igt@kms_flip@flip-vs-expired-vblank@a-hdmi-a1:
- shard-glk: [FAIL][154] ([i915#2122]) -> [PASS][155]
[154]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11661/shard-glk3/igt@kms_flip@[email protected]
[155]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_104052v1/shard-glk4/igt@kms_flip@[email protected]
* igt@kms_flip@plain-flip-ts-check@c-edp1:
- shard-skl: [FAIL][156] ([i915#2122]) -> [PASS][157]
[156]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11661/shard-skl7/igt@kms_flip@[email protected]
[157]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_104052v1/shard-skl8/igt@kms_flip@[email protected]
* igt@kms_flip_scaled_crc@flip-32bpp-ytileccs-to-64bpp-ytile-upscaling:
- shard-glk: [FAIL][158] ([i915#4911]) -> [PASS][159] +1 similar issue
[158]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11661/shard-glk8/igt@kms_flip_scaled_crc@flip-32bpp-ytileccs-to-64bpp-ytile-upscaling.html
[159]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_104052v1/shard-glk7/igt@kms_flip_scaled_crc@flip-32bpp-ytileccs-to-64bpp-ytile-upscaling.html
* igt@kms_flip_scaled_crc@flip-64bpp-ytile-to-16bpp-ytile-downscaling:
- shard-iclb: [SKIP][160] ([i915#3701]) -> [PASS][161]
[160]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11661/shard-iclb2/igt@kms_flip_scaled_crc@flip-64bpp-ytile-to-16bpp-ytile-downscaling.html
[161]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_104052v1/shard-iclb6/igt@kms_flip_scaled_crc@flip-64bpp-ytile-to-16bpp-ytile-downscaling.html
* igt@kms_frontbuffer_tracking@fbc-suspend:
- shard-tglb: [DMESG-WARN][162] ([i915#2411] / [i915#2867]) -> [PASS][163]
[162]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11661/shard-tglb7/igt@[email protected]
[163]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_104052v1/shard-tglb2/igt@[email protected]
* {igt@kms_hdr@bpc-switch-suspend@pipe-a-edp-1}:
- shard-skl: [FAIL][164] ([i915#1188]) -> [PASS][165]
[164]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11661/shard-skl10/igt@kms_hdr@[email protected]
[165]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_104052v1/shard-skl6/igt@kms_hdr@[email protected]
* igt@kms_invalid_mode@int-max-clock:
- {shard-rkl}: [SKIP][166] ([i915#4278]) -> [PASS][167]
[166]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11661/shard-rkl-4/igt@[email protected]
[167]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_104052v1/shard-rkl-6/igt@[email protected]
* igt@kms_plane_alpha_blend@pipe-c-constant-alpha-min:
- shard-skl: [FAIL][168] ([fdo#108145] / [i915#265]) -> [PASS][169] +1 similar issue
[168]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11661/shard-skl1/igt@[email protected]
[169]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_104052v1/shard-skl10/igt@[email protected]
* igt@kms_plane_scaling@downscale-with-modifier-factor-0-5@pipe-c-edp-1-downscale-with-modifier:
- shard-iclb: [SKIP][170] ([i915#5176]) -> [PASS][171] +2 similar issues
[170]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11661/shard-iclb2/igt@kms_plane_scaling@downscale-with-modifier-factor-0-5@pipe-c-edp-1-downscale-with-modifier.html
[171]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_104052v1/shard-iclb6/igt@kms_plane_scaling@downscale-with-modifier-factor-0-5@pipe-c-edp-1-downscale-with-modifier.html
* igt@kms_psr2_su@page_flip-xrgb8888:
- shard-iclb: [SKIP][172] ([fdo#109642] / [fdo#111068] / [i915#658]) -> [PASS][173]
[172]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11661/shard-iclb7/igt@kms_psr2_su@page_flip-xrgb8888.html
[173]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_104052v1/shard-iclb2/igt@kms_psr2_su@page_flip-xrgb8888.html
* igt@kms_psr@cursor_mmap_cpu:
- {shard-rkl}: [SKIP][174] ([i915#1072]) -> [PASS][175]
[174]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11661/shard-rkl-4/igt@kms_psr@cursor_mmap_cpu.html
[175]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_104052v1/shard-rkl-6/igt@kms_psr@cursor_mmap_cpu.html
* igt@kms_psr@psr2_no_drrs:
- shard-iclb: [SKIP][176] ([fdo#109441]) -> [PASS][177] +1 similar issue
[176]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11661/shard-iclb3/igt@kms_psr@psr2_no_drrs.html
[177]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_104052v1/shard-iclb2/igt@kms_psr@psr2_no_drrs.html
#### Warnings ####
* igt@gem_exec_balancer@parallel:
- shard-iclb: [SKIP][178] ([i915#4525]) -> [DMESG-WARN][179] ([i915#5614]) +1 similar issue
[178]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11661/shard-iclb6/igt@[email protected]
[179]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_104052v1/shard-iclb1/igt@[email protected]
* igt@gem_exec_fair@basic-none-rrul@rcs0:
- shard-iclb: [FAIL][180] ([i915#2852]) -> [FAIL][181] ([i915#2842])
[180]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11661/shard-iclb7/igt@gem_exec_fair@[email protected]
[181]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_104052v1/shard-iclb7/igt@gem_exec_fair@[email protected]
* igt@i915_pm_rc6_residency@rc6-idle:
- shard-iclb: [WARN][182] ([i915#2684]) -> [FAIL][183] ([i915#2680] / [i915#2684])
[182]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11661/shard-iclb1/igt@[email protected]
[183]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_104052v1/shard-iclb4/igt@[email protected]
* igt@i915_pm_rpm@modeset-non-lpsp-stress:
- shard-tglb: [SKIP][184] ([fdo#111644] / [i915#1397] / [i915#2411]) -> [SKIP][185] ([fdo#111644] / [i915#1397]) +3 similar issues
[184]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11661/shard-tglb7/igt@[email protected]
[185]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_104052v1/shard-tglb8/igt@[email protected]
* igt@i915_pm_rpm@modeset-pc8-residency-stress:
- shard-tglb: [SKIP][186] ([fdo#109506] / [i915#2411]) -> [SKIP][187] ([fdo#109506]) +2 similar issues
[186]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11661/shard-tglb8/igt@[email protected]
[187]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_104052v1/shard-tglb6/igt@[email protected]
* igt@kms_fbcon_fbt@fbc-suspend:
- shard-apl: [FAIL][188] ([i915#4767]) -> [INCOMPLETE][189] ([i915#180])
[188]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11661/shard-apl4/igt@[email protected]
[189]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_104052v1/shard-apl1/igt@[email protected]
* igt@kms_psr2_sf@cursor-plane-update-sf:
- shard-iclb: [SKIP][190] ([fdo#111068] / [i915#658]) -> [SKIP][191] ([i915#2920])
[190]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11661/shard-iclb7/igt@[email protected]
[191]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_104052v1/shard-iclb2/igt@[email protected]
* igt@kms_psr2_su@page_flip-p010:
- shard-iclb: [SKIP][192] ([fdo#109642] / [fdo#111068] / [i915#658]) -> [FAIL][193] ([i915#5939])
[192]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11661/shard-iclb3/igt@kms_psr2_su@page_flip-p010.html
[193]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_104052v1/shard-iclb2/igt@kms_psr2_su@page_flip-p010.html
* igt@runner@aborted:
- shard-kbl: ([FAIL][194], [FAIL][195], [FAIL][196], [FAIL][197], [FAIL][198], [FAIL][199], [FAIL][200], [FAIL][201], [FAIL][202]) ([i915#3002] / [i915#4312] / [i915#5257]) -> ([FAIL][203], [FAIL][204], [FAIL][205], [FAIL][206], [FAIL][207], [FAIL][208], [FAIL][209], [FAIL][210], [FAIL][211], [FAIL][212], [FAIL][213], [FAIL][214], [FAIL][215], [FAIL][216], [FAIL][217]) ([i915#180] / [i915#3002] / [i915#4312] / [i915#5257])
[194]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11661/shard-kbl6/igt@[email protected]
[195]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11661/shard-kbl1/igt@[email protected]
[196]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11661/shard-kbl4/igt@[email protected]
[197]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11661/shard-kbl4/igt@[email protected]
[198]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11661/shard-kbl3/igt@[email protected]
[199]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11661/shard-kbl1/igt@[email protected]
[200]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11661/shard-kbl6/igt@[email protected]
[201]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11661/shard-kbl7/igt@[email protected]
[202]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11661/shard-kbl4/igt@[email protected]
[203]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_104052v1/shard-kbl6/igt@[email protected]
[204]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_104052v1/shard-kbl7/igt@[email protected]
[205]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_104052v1/shard-kbl7/igt@[email protected]
[206]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_104052v1/shard-kbl4/igt@[email protected]
[207]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_104052v1/shard-kbl7/igt@[email protected]
[208]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_104052v1/shard-kbl4/igt@[email protected]
[209]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_104052v1/shard-kbl7/igt@[email protected]
[210]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_104052v1/shard-kbl4/igt@[email protected]
[211]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_104052v1/shard-kbl7/igt@[email protected]
[212]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_104052v1/shard-kbl7/igt@[email protected]
[213]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_104052v1/shard-kbl3/igt@[email protected]
[214]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_104052v1/shard-kbl6/igt@[email protected]
[215]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_104052v1/shard-kbl4/igt@[email protected]
[216]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_104052v1/shard-kbl1/igt@[email protected]
[217]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_104052v1/shard-kbl4/igt@[email protected]
{name}: This element is suppressed. This means it is ignored when computing
the status of the difference (SUCCESS, WARNING, or FAILURE).
[fdo#108145]: https://bugs.freedesktop.org/show_bug.cgi?id=108145
[fdo#109271]: https://bugs.freedesktop.org/show_bug.cgi?id=109271
[fdo#109274]: https://bugs.freedesktop.org/show_bug.cgi?id=109274
[fdo#109279]: https://bugs.freedesktop.org/show_bug.cgi?id=109279
[fdo#109283]: https://bugs.freedesktop.org/show_bug.cgi?id=109283
[fdo#109289]: https://bugs.freedesktop.org/show_bug.cgi?id=109289
[fdo#109291]: https://bugs.freedesktop.org/show_bug.cgi?id=109291
[fdo#109300]: https://bugs.freedesktop.org/show_bug.cgi?id=109300
[fdo#109308]: https://bugs.freedesktop.org/show_bug.cgi?id=109308
[fdo#109441]: https://bugs.freedesktop.org/show_bug.cgi?id=109441
[fdo#109506]: https://bugs.freedesktop.org/show_bug.cgi?id=109506
[fdo#109642]: https://bugs.freedesktop.org/show_bug.cgi?id=109642
[fdo#110189]: https://bugs.freedesktop.org/show_bug.cgi?id=110189
[fdo#110254]: https://bugs.freedesktop.org/show_bug.cgi?id=110254
[fdo#110723]: https://bugs.freedesktop.org/show_bug.cgi?id=110723
[fdo#111068]: https://bugs.freedesktop.org/show_bug.cgi?id=111068
[fdo#111314]: https://bugs.freedesktop.org/show_bug.cgi?id=111314
[fdo#111614]: https://bugs.freedesktop.org/show_bug.cgi?id=111614
[fdo#111644]: https://bugs.freedesktop.org/show_bug.cgi?id=111644
[fdo#111825]: https://bugs.freedesktop.org/show_bug.cgi?id=111825
[fdo#111827]: https://bugs.freedesktop.org/show_bug.cgi?id=111827
[fdo#112022]: https://bugs.freedesktop.org/show_bug.cgi?id=112022
[i915#1063]: https://gitlab.freedesktop.org/drm/intel/issues/1063
[i915#1072]: https://gitlab.freedesktop.org/drm/intel/issues/1072
[i915#1099]: https://gitlab.freedesktop.org/drm/intel/issues/1099
[i915#1149]: https://gitlab.freedesktop.org/drm/intel/issues/1149
[i915#1155]: https://gitlab.freedesktop.org/drm/intel/issues/1155
[i915#1188]: https://gitlab.freedesktop.org/drm/intel/issues/1188
[i915#132]: https://gitlab.freedesktop.org/drm/intel/issues/132
[i915#1397]: https://gitlab.freedesktop.org/drm/intel/issues/1397
[i915#1722]: https://gitlab.freedesktop.org/drm/intel/issues/1722
[i915#1769]: https://gitlab.freedesktop.org/drm/intel/issues/1769
[i915#180]: https://gitlab.freedesktop.org/drm/intel/issues/180
[i915#1825]: https://gitlab.freedesktop.org/drm/intel/issues/1825
[i915#1839]: https://gitlab.freedesktop.org/drm/intel/issues/1839
[i915#1845]: https://gitlab.freedesktop.org/drm/intel/issues/1845
[i915#1849]: https://gitlab.freedesktop.org/drm/intel/issues/1849
[i915#1911]: https://gitlab.freedesktop.org/drm/intel/issues/1911
[i915#1982]: https://gitlab.freedesktop.org/drm/intel/issues/1982
[i915#2122]: https://gitlab.freedesktop.org/drm/intel/issues/2122
[i915#2190]: https://gitlab.freedesktop.org/drm/intel/issues/2190
[i915#2346]: https://gitlab.freedesktop.org/drm/intel/issues/2346
[i915#2410]: https://gitlab.freedesktop.org/drm/intel/issues/2410
[i915#2411]: https://gitlab.freedesktop.org/drm/intel/issues/2411
[i915#2437]: https://gitlab.freedesktop.org/drm/intel/issues/2437
[i915#2521]: https://gitlab.freedesktop.org/drm/intel/issues/2521
[i915#2527]: https://gitlab.freedesktop.org/drm/intel/issues/2527
[i915#2530]: https://gitlab.freedesktop.org/drm/intel/issues/2530
[i915#2587]: https://gitlab.freedesktop.org/drm/intel/issues/2587
[i915#265]: https://gitlab.freedesktop.org/drm/intel/issues/265
[i915#2672]: https://gitlab.freedesktop.org/drm/intel/issues/2672
[i915#2680]: https://gitlab.freedesktop.org/drm/intel/issues/2680
[i915#2681]: https://gitlab.freedesktop.org/drm/intel/issues/2681
[i915#2684]: https://gitlab.freedesktop.org/drm/intel/issues/2684
[i915#280]: https://gitlab.freedesktop.org/drm/intel/issues/280
[i915#2842]: https://gitlab.freedesktop.org/drm/intel/issues/2842
[i915#2846]: https://gitlab.freedesktop.org/drm/intel/issues/2846
[i915#2849]: https://gitlab.freedesktop.org/drm/intel/issues/2849
[i915#2852]: https://gitlab.freedesktop.org/drm/intel/issues/2852
[i915#2867]: https://gitlab.freedesktop.org/drm/intel/issues/2867
[i915#2920]: https://gitlab.freedesktop.org/drm/intel/issues/2920
[i915#2994]: https://gitlab.freedesktop.org/drm/intel/issues/2994
[i915#3002]: https://gitlab.freedesktop.org/drm/intel/issues/3002
[i915#3012]: https://gitlab.freedesktop.org/drm/intel/issues/3012
[i915#3063]: https://gitlab.freedesktop.org/drm/intel/issues/3063
[i915#3070]: https://gitlab.freedesktop.org/drm/intel/issues/3070
[i915#3281]: https://gitlab.freedesktop.org/drm/intel/issues/3281
[i915#3282]: https://gitlab.freedesktop.org/drm/intel/issues/3282
[i915#3291]: https://gitlab.freedesktop.org/drm/intel/issues/3291
[i915#3297]: https://gitlab.freedesktop.org/drm/intel/issues/3297
[i915#3299]: https://gitlab.freedesktop.org/drm/intel/issues/3299
[i915#3318]: https://gitlab.freedesktop.org/drm/intel/issues/3318
[i915#3319]: https://gitlab.freedesktop.org/drm/intel/issues/3319
[i915#3323]: https://gitlab.freedesktop.org/drm/intel/issues/3323
[i915#3359]: https://gitlab.freedesktop.org/drm/intel/issues/3359
[i915#3361]: https://gitlab.freedesktop.org/drm/intel/issues/3361
[i915#3458]: https://gitlab.freedesktop.org/drm/intel/issues/3458
[i915#3539]: https://gitlab.freedesktop.org/drm/intel/issues/3539
[i915#3555]: https://gitlab.freedesktop.org/drm/intel/issues/3555
[i915#3558]: https://gitlab.freedesktop.org/drm/intel/issues/3558
[i915#3637]: https://gitlab.freedesktop.org/drm/intel/issues/3637
[i915#3638]: https://gitlab.freedesktop.org/drm/intel/issues/3638
[i915#3689]: https://gitlab.freedesktop.org/drm/intel/issues/3689
[i915#3701]: https://gitlab.freedesktop.org/drm/intel/issues/3701
[i915#3708]: https://gitlab.freedesktop.org/drm/intel/issues/3708
[i915#3734]: https://gitlab.freedesktop.org/drm/intel/issues/3734
[i915#3743]: https://gitlab.freedesktop.org/drm/intel/issues/3743
[i915#3828]: https://gitlab.freedesktop.org/drm/intel/issues/3828
[i915#3886]: https://gitlab.freedesktop.org/drm/intel/issues/3886
[i915#3936]: https://gitlab.freedesktop.org/drm/intel/issues/3936
[i915#3955]: https://gitlab.freedesktop.org/drm/intel/issues/3955
[i915#404]: https://gitlab.freedesktop.org/drm/intel/issues/404
[i915#4070]: https://gitlab.freedesktop.org/drm/intel/issues/4070
[i915#4077]: https://gitlab.freedesktop.org/drm/intel/issues/4077
[i915#4078]: https://gitlab.freedesktop.org/drm/intel/issues/4078
[i915#4083]: https://gitlab.freedesktop.org/drm/intel/issues/4083
[i915#4098]: https://gitlab.freedesktop.org/drm/intel/issues/4098
[i915#4103]: https://gitlab.freedesktop.org/drm/intel/issues/4103
[i915#4212]: https://gitlab.freedesktop.org/drm/intel/issues/4212
[i915#426]: https://gitlab.freedesktop.org/drm/intel/issues/426
[i915#4270]: https://gitlab.freedesktop.org/drm/intel/issues/4270
[i915#4278]: https://gitlab.freedesktop.org/drm/intel/issues/4278
[i915#4312]: https://gitlab.freedesktop.org/drm/intel/issues/4312
[i915#4338]: https://gitlab.freedesktop.org/drm/intel/issues/4338
[i915#4369]: https://gitlab.freedesktop.org/drm/intel/issues/4369
[i915#4525]: https://gitlab.freedesktop.org/drm/intel/issues/4525
[i915#4538]: https://gitlab.freedesktop.org/drm/intel/issues/4538
[i915#454]: https://gitlab.freedesktop.org/drm/intel/issues/454
[i915#4565]: https://gitlab.freedesktop.org/drm/intel/issues/4565
[i915#4613]: https://gitlab.freedesktop.org/drm/intel/issues/4613
[i915#4767]: https://gitlab.freedesktop.org/drm/intel/issues/4767
[i915#4812]: https://gitlab.freedesktop.org/drm/intel/issues/4812
[i915#4833]: https://gitlab.freedesktop.org/drm/intel/issues/4833
[i915#4842]: https://gitlab.freedesktop.org/drm/intel/issues/4842
[i915#4852]: https://gitlab.freedesktop.org/drm/intel/issues/4852
[i915#4853]: https://gitlab.freedesktop.org/drm/intel/issues/4853
[i915#4860]: https://gitlab.freedesktop.org/drm/intel/issues/4860
[i915#4877]: https://gitlab.freedesktop.org/drm/intel/issues/4877
[i915#4880]: https://gitlab.freedesktop.org/drm/intel/issues/4880
[i915#4881]: https://gitlab.freedesktop.org/drm/intel/issues/4881
[i915#4885]: https://gitlab.freedesktop.org/drm/intel/issues/4885
[i915#4893]: https://gitlab.freedesktop.org/drm/intel/issues/4893
[i915#4911]: https://gitlab.freedesktop.org/drm/intel/issues/4911
[i915#4929]: https://gitlab.freedesktop.org/drm/intel/issues/4929
[i915#4991]: https://gitlab.freedesktop.org/drm/intel/issues/4991
[i915#5030]: https://gitlab.freedesktop.org/drm/intel/issues/5030
[i915#5080]: https://gitlab.freedesktop.org/drm/intel/issues/5080
[i915#5098]: https://gitlab.freedesktop.org/drm/intel/issues/5098
[i915#5176]: https://gitlab.freedesktop.org/drm/intel/issues/5176
[i915#5234]: https://gitlab.freedesktop.org/drm/intel/issues/5234
[i915#5235]: https://gitlab.freedesktop.org/drm/intel/issues/5235
[i915#5257]: https://gitlab.freedesktop.org/drm/intel/issues/5257
[i915#5286]: https://gitlab.freedesktop.org/drm/intel/issues/5286
[i915#5287]: https://gitlab.freedesktop.org/drm/intel/issues/5287
[i915#5288]: https://gitlab.freedesktop.org/drm/intel/issues/5288
[i915#5289]: https://gitlab.freedesktop.org/drm/intel/issues/5289
[i915#533]: https://gitlab.freedesktop.org/drm/intel/issues/533
[i915#5563]: https://gitlab.freedesktop.org/drm/intel/issues/5563
[i915#5566]: https://gitlab.freedesktop.org/drm/intel/issues/5566
[i915#5614]: https://gitlab.freedesktop.org/drm/intel/issues/5614
[i915#5639]: https://gitlab.freedesktop.org/drm/intel/issues/5639
[i915#5691]: https://gitlab.freedesktop.org/drm/intel/issues/5691
[i915#5723]: https://gitlab.freedesktop.org/drm/intel/issues/5723
[i915#5784]: https://gitlab.freedesktop.org/drm/intel/issues/5784
[i915#5939]: https://gitlab.freedesktop.org/drm/intel/issues/5939
[i915#658]: https://gitlab.freedesktop.org/drm/intel/issues/658
[i915#716]: https://gitlab.freedesktop.org/drm/intel/issues/716
[i915#79]: https://gitlab.freedesktop.org/drm/intel/issues/79
Build changes
-------------
* Linux: CI_DRM_11661 -> Patchwork_104052v1
CI-20190529: 20190529
CI_DRM_11661: f0d63dbb9c4ebcb646fd41c0e810d60ff7c7d11e @ git://anongit.freedesktop.org/gfx-ci/linux
IGT_6473: 64723cd44c1cd2f8b8263e3b3681c99f05a1b499 @ https://gitlab.freedesktop.org/drm/igt-gpu-tools.git
Patchwork_104052v1: f0d63dbb9c4ebcb646fd41c0e810d60ff7c7d11e @ git://anongit.freedesktop.org/gfx-ci/linux
piglit_4509: fdc5a4ca11124ab8413c7988896eec4c97336694 @ git://anongit.freedesktop.org/piglit
== Logs ==
For more details see: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_104052v1/index.html
Quoted 9 lines · Jim Cromie
DRM.debug API is 23 macros, issuing 10 exclusive categories of debug messages. By rough count, they are used 5140 times in the kernel. These all call
drm_dbgordrm_devdbg, which calldrm_debug_enabled(), which checks bits in global__drm_debug. Some of these are page-flips and vblanks, and get called often.
DYNAMIC_DEBUG(withCONFIG_JUMP_LABEL) is built to avoid this kind of work, with NOOPd jump/callsites.
Quoted 7 lines
This patchset is RFC because:
- it touches 2.5 subsystems: dyndbg, drm, tracefs (new events)
- dyndbg class support is built for drm, needs it for validation
- new api, used by drm
- big memory impact, with 5100 new pr-debug callsites.
- drm class bikeshedding opportunities
- others, names etc.
Thanks a lot for keeping on pushing this!
Quoted 46 lines
DYNAMIC_DEBUG:Adapt to directly represent 32 exclusive classes / categories. All existing users get _CLASS_DFLT:31, reserving 0-30 for opt-in.
dynamic_debug_register_classes(): Tells dyndbg that caller/client is using .class_id's 0..N, and wants them exposed and manipulatable with
names:DRM_UT_KMSetc.Client invokes
DYNAMIC_DEBUG_CLASSESto define thename->idmap, then registers it during its initialization.Then, when a dyndbg command-query has "class FOO":
echo class
DRM_UT_KMS+p >/proc/dynamic_debug/control
ddebug_change()will 1stddebug_validate_classname()for each module, using its registered class-maps; only modules which knowDRM_UT_KMSwill get those callsite adjustments. This "protects" each module's class-id space, unlike "class 4" query syntax.Add bitmap support for:
echo0x02>/sys/module/drm/parameters/debugAdd symbolic bitmap, because we have the class-names:
echo +DRM_UT_KMS,+DRM_UT_ATOMIC >/sys/module/drm/parameters/debugAdd
test_dynamic_debug, to prove out the API.which is (used 3x to prove class-id ranges):
- DYNAMIC_DEBUG_CLASSES(var, ... [3 class-name-literals each])
-dynamic_debug_register_classes(var)
-dynamic_debug_unregister_classes(var)
also (6x):
+module_param_cb(<node-name>,¶m_ops_dyndbg_classes, /[pt][123]_bitmap/, 0600);Bits 0,1,2 of each of the 6 bitmaps control the 3 named classes in each of 3 groups, toggling their p,T bits respectively.
RFC:
dynamic_debug_register_classes()cannot act early enough to be in effect at module-load. So this will not work as you'd reasonably expect:
Quoted 6 lines
modprobe
test_dynamic_debugdyndbg='+pfm; class FOO +pfmlt'The 1st query:+pfm will be enabled during load, but in the 2nd query, "class FOO" will be unknown at load time. Early class enablement would be nice.
DYNAMIC_DEBUG_CLASSESis a static initializer, which is certainly early enough, but Im missing a trick, suggestions?
So maybe I'm just totally overloading this work here so feel free to ignore or postpone, but: Could we do the dynamic_debug_register_classes() automatically at module load as a new special section? And then throw in a bit of kbuild so that in a given subsystem every driver gets the same class names by default and everything would just work, without having to sprinkle calls to dynamic_debug_register_classes() all over the place? That kbuild magic could then also insert all the boilerplate to make the module options work, or maybe you could push that all into the module loader and it would add these special options on its own (yay for more consistency across subsystems)?
Also I think with that the early class stuff should be possible to fix, since you can make sure that the classes are all there (in the module loader code) before anything else gets done. A bit a special case but oh well.
For the entire class approach, did you spot another subsystem that could benefit from this and maybe make a more solid case that this is something good?
Quoted 45 lines
Wildcarding on classname is possible, maybe useful:
echo +DRM_UT_\* >
/sys/module/drm/parameters/debugIf contemplated in earnest, it should consider the difference between "DRM_*" and "
*_KMS", wrt observing across class hierarchies, as well as decide whether that echo means 1st match, or all matching names.
__pr_debug_cls(cls, fmt,...)is just for testing, drm doesnt need it.DRM adaptation:
Basically, these patches add another layer of macro indirection, which by
CONFIG_DRM_USE_DYNAMIC_DEBUG=y, wraps drm_*dbg() in dyndbg's callsite Factory macro, and adds the new descriptor arg to the funcs.With these patches, drm.debugs appear as controllable *pr-dbg* callsites:
[ 11.804352] dyndbg: register_classes: drm [ 11.920715] dyndbg: 234 debug prints in module drm_kms_helper [ 11.932135] dyndbg: 2 debug prints in module ttm [ 11.936119] dyndbg: 8 debug prints in module video [ 12.537543] dyndbg: 1756 debug prints in module i915 [ 12.555045] dyndbg: register_classes: i915 [ 12.666727] AMD-Vi: AMD IOMMUv2 functionality not available on this .. [ 13.735310] dyndbg: 3859 debug prints in module amdgpuamdgpu's large count includes:
582 direct uses/mentions of pr_debug 43 defns of DC_LOG_*, which use either pr_debug or DRM_DEBUG_* ~1000 uses of DC_LOG_* 1116 uses of dml_print in drivers/gpu/drm/amd 15 drm_dbg_\\w+ drivers/gpu/drm/amd 273 DRM_DEBUG_\\w+ drivers/gpu/drm/amdi915 has:
1072 drm_dbg_\\w+ drivers/gpu/drm/i915/ | wc -l 200 DRM_DEBUG_\\w+ drivers/gpu/drm/i915/ 46 pr_debug drivers/gpu/drm/i915/ 144 gvt_dbg_\\w+ drivers/gpu/drm/i915/gvt, using pr_debugThis impacts the data footprint, so everything new/drm is dependent on DRM_USE_DYNAMIC_DEBUG=y.
Quoted 6 lines
RFC for DRM:
- decoration flags "fmlt" do not work on drm_*dbg().
(drm_*dbg() dont usepr_debug, they *become* one flavor of them) this could (should?) be added, and maybe tailored for drm.
some of the device prefixes are very long, a "d" flag could optionalize them.
I'm lost what the fmlt decoration flags are?
Quoted 2 lines
- api use needs review wrt drm life-cycle.
enumdrm_debug_categoryandDYNAMIC_DEBUG_CLASSEScould be together?
Hm if they're tied to module lifetime we should be good? Not sure what could go wrong here.
Quoted 3 lines
- class-names could stand review, perhaps extension "drm:core:" etc have appeared (maybe just from me) or a "plan" to look at it later
Yeah it's been a bit sprawling. I'm kinda hoping that by firmly establishing dyndbg as the drm debug approach we can cut down for the need for ad-hoc flags a bit.
Quoted 4 lines
- i915 & amdgpu have
pr_debugs(DC_LOG_*, gvt_dbg_*) that have class-ish prefixes that are separate from, but similar to DRM_UT_*, and could stand review and possible unification with reformed or extended drm categories.
Yeah drm is not entirely consistent with how exactly driver debug printing should be done. Another reason why I'm hoping that the kitchen sync with everything approach you're doing here could help unify things.
Quoted 4 lines
- the change to enum
drm_debug_categoryfrom bitmask values to 0..31 means that we foreclose this possiblility:drm_dbg(DRM_UT_CORE|DRM_UT_KMS, "wierd double-cat experiment");
Yeah no, that doesn't make much sense to me :-)
Quoted 2 lines
- nouveau has very few drm.debug calls,
hasNV_DEBUG,VMM_DEBUG,nvkm_printk_, I havent looked deeply.
Yeah see above. There's a pile more drivers (more on the armsoc side of things) which are quite big on the raw debug call approach.
Cheers, Daniel
Quoted 279 lines
DYNDBG/DRM -> TRACEFS
My 1st try was motivated by Sean Paul's patch - DRM.trace:
https://patchwork.freedesktop.org/patch/445549/?series=78133&rev=5Those used
trace_printk, so were not good for upstream.Vincent Whitchurch's code:
https://lore.kernel.org/lkml/[email protected]/added similar features, by sending printk:console events from dyndbg. It met with a good reception from Steve Rostedt, so I re-started with that.
The biggest addition (from UI viewpoint) is 4 new trace-events, 2 each from dyndbg (
pr_debug,dev_dbg) and drm (drm_dbg,drm_dev_dbg); 2 have dev, other 2 avoid storing nulls. Im unsure that 4 distinctions is valuable, but it seemed most obvious to reflect them straight thru to tracefs.RFC: the event/message formats are a bit of a mash-up;
in
/sys/kernel/tracing:
drm/drm_debug/format:print fmt: "%s",__get_str(msg)drm/drm_devdbg/format:print fmt: "cat:%d, %s %s", \ REC->drm_debug_category, dev_name(REC->dev), __get_str(msg)The 1st prints just the mesg itself, 2nd prints category as int; it'd be better if DRM.class-name replaced (not just augmented) the event-name "
drm_devdbg" in the trace, is that possible ?dyndbg/prdbg/format:
print fmt: "%s.%s %s",REC->desc->modname,REC->desc->function,__get_str(msg)dyndbg/devdbg/format:
print fmt: "%s.%s %s",REC->desc->modname,REC->desc->function,__get_str(msg)These add a prefix string similar to dyndbg's decorations, except they don't use dyndbg's "fmlt" decoration flags.
There are also 3 vblank trace-events already,
declared in:drivers/gpu/drm/drm_trace.h
15:TRACE_EVENT(drm_vblank_event,
35:TRACE_EVENT(drm_vblank_event_queued,
52:TRACE_EVENT(drm_vblank_event_delivered,STATUS
kernel-test-robot tested this patchset (on 5.18-rc6). github:[jimc:blead] BUILD SUCCESS
6c59e52ac81dd81ac7da4522a5e15b7ac488d5b5May 15, 2022, 8:39 AM (1 day ago)Ive been testing, mostly on virtme, mostly with this:
#!/bin/bash# test class FOO handling of dynamic-debugalias lmt='modprobe
test_dynamic_debugdyndbg=+pmf' alias rmt='rmmodtest_dynamic_debug'
alias look='greptest_dynamic_debug/proc/dynamic_debug/control'
lookfor(){
grep $1/proc/dynamic_debug/control
}
vx(){
echo $* >/sys/module/dynamic_debug/parameters/verbose
}# amdgpu has ~2200 pr-debugs (before drm-debug-on-dyndbg), # use them to prove modprobe <mod> dyndbg=+p works
test_param_dyndbg(){modprobe amdgpu dyndbg=+pfm
let count=$(grep =pmf/proc/dynamic_debug/control| grep amdgpu | wc -l)if [ $count -gt 200 ] ; then
echo amdgpu has $count pr-dbgs
return 0
else
echo failed $count
return -1
fi
}
out=$(test_param_dyndbg)
echo out:$out $?
[ $? -eq 0 ] || exit $?
qry_cmd(){
echo "QCMD: $* >control" >&2
echo $* >/proc/dynamic_debug/control
}# enable dyndbg tracing dynable() { grep -P \\d $SKT/events/dyndbg/{.,*}/enable echo 1 > $SKT/events/dyndbg/enable grep -P \\d $SKT/events/dyndbg/{.,*}/enable }# enable drm tracing drmable() { grep -P \\d $SKT/events/drm/{.,*}/enable echo 1 > $SKT/events/drm/enable grep -P \\d $SKT/events/drm/{.,*}/enable }function
doit(){
cat/sys/module/test_dynamic_debug/parameters/do_prints
}# test class FOO behavior of test_dynamic_debug module ttest_module__() { flg=$1 dmesg -C modprobe test_dynamic_debug dyndbg=+pfm doitfor cls in FOO BAR BUZZ; do
qry_cmdmoduletest_dynamic_debugclass $cls $flg doit
done
doitfor cls in Foo Bar Buzz; do
qry_cmdmoduletest_dynamic_debugclass $cls $flg doit
done
doitfor cls in bing bong boom; do
qry_cmdmoduletest_dynamic_debugclass $cls $flg doit
done
doitdmesg | grep class
}
ttest_module(){ttest_module__ +p ttest_module__ -p #ttest_module__ +T #ttest_module__ -T }#dynable
#drmable
ttest_module
greptest_dyn/proc/dynamic_debug/control# use/test bitmapsset_tddm_() { val=$1; knob=$2; echo "TDDM: $val >$knob" >&2 echo $val > /sys/module/test_dynamic_debug/parameters/$knob cat /sys/module/test_dynamic_debug/parameters/$knob }CLS_1="FOO -FOO +FOO -FOO BAR -BAR +BAR -BAR BUZZ -BUZZ +BUZZ -BUZZ" CLS_2=" Foo Bar Buzz -Foo -Bar -Buzz +Foo +Bar +Buzz -Foo -Bar -Buzz" CLS_3=" bing bong boom -bing -bong -boom +bing +bong +boom -bing -bong -boom"
tddm_sysnode_classes__() { targ=$1 shift cls=$* for bitsym in $cls; do set_tddm_ $bitsym $targ done }# work all 3 sysfs bitmapsfor sysnode in
c1_syslog_bitsc2_syslog_bitsc3_syslog_bits; do
for val in 0 1 2 4 8 0;
do
tddm_sysnode_classes__$sysnode $val
done
done
tddm_sysnode_classes__c1_syslog_bits$CLS_1tddm_sysnode_classes__c2_syslog_bits$CLS_2tddm_sysnode_classes__c3_syslog_bits$CLS_3echo "show unknown: c3-names on c1-knob" >&2
tddm_sysnode_classes__c1_trace_bits$CLS_3echo "flags look inverted" >&2
tddm_sysnode_classes__c1_syslog_bits$CLS_1CLS_1_=FOO,-FOO,+FOO,-FOO,BAR,-BAR,+BAR,-BAR,BUZZ,-BUZZ,+BUZZ,-BUZZ CLS_2_=Foo,Bar,Buzz,-Foo,-Bar,-Buzz,+Foo,+Bar,+Buzz,-Foo,-Bar,-Buzz
# leading err doesnt wreck the rest CLS_3_=,bing,bong,boom,-bing,-bong,-boom,+bing,+bong,+boom,-bing,-bong,-boom
tddm_sysnode_classes__c1_syslog_bits$CLS_1_tddm_sysnode_classes__c2_syslog_bits$CLS_2_tddm_sysnode_classes__c3_syslog_bits$CLS_3_Cc Sean Paul <[email protected]>Cc Daniel Vetter <[email protected]>Cc David Airlie <[email protected]>Cc Jani Nikula <[email protected]>Cc Joonas Lahtinen <[email protected]>Cc Pekka Paalanen <[email protected]>Cc Rob Clark <[email protected]>Cc Steven Rostedt <[email protected]>Cc Thomas Zimmermann <[email protected]>Cc Ville Syrjälä <[email protected]>Cc Chris Wilson <[email protected]>Cc Steven Rostedt <[email protected]>Jim Cromie (27):
dyndbg: fixstatic_branchmanipulation
dyndbg: show both old and new in change-info
dyndbg: fix module.dyndbg handling
dyndbg: drop EXPORTeddynamic_debug_exec_queries
dyndbg: add exclusiveclass_idtopr_debugcallsites
dyndbg: add dynamic_debug_(un)register_classes
dyndbg: validate class FOO on module
dyndbg: add drm.debug style bitmap support Doc/dyndbg: document new classclass_namequery support
dyndbg: let query-modname override defaulting modname
dyndbg: support symbolic class-names in bitmap
dyndbg: change zero-or-one classes-map to maps list
dyndbg: add__pr_debug_cls(class, fmt, ...)
dyndbg: addtest_dynamic_debugmodule
drm: POC drm on dyndbg - map class-names to drm_debug_category's drm/print: POC drm on dyndbg - use bitmap
drm_print: condense enumdrm_debug_category
drm_print: interpose drm_*dbg with forwarding macros
drm_print: wrap drm_*_dbg in dyndbg descriptor factory macro
drm_print: refinedrm_debug_enabledfor jump-label
drm_print: prefer bare printkKERN_DEBUGon generic fn
drm_print: add_ddebugdesc to drm_*dbg prototypes
dyndbg: add_DPRINTK_FLAGS_ENABLED
dyndbg: add_DPRINTK_FLAGS_TRACE
dyndbg: add write-events-to-tracefs code
dyndbg: 4 new trace-events:pr_debug,dev_dbg, drm_{,dev}debug dyndbg/drm: POC add tracebits sysfs-knob.../admin-guide/dynamic-debug-howto.rst | 12 + MAINTAINERS | 1 + drivers/gpu/drm/Kconfig | 12 + drivers/gpu/drm/Makefile | 2 + drivers/gpu/drm/amd/amdgpu/amdgpu_drv.c | 3 + drivers/gpu/drm/drm_drv.c | 5 + drivers/gpu/drm/drm_print.c | 69 ++- drivers/gpu/drm/i915/i915_module.c | 11 + drivers/gpu/drm/nouveau/nouveau_drm.c | 4 + include/drm/drm_drv.h | 26 + include/drm/drm_print.h | 84 ++- include/linux/dynamic_debug.h | 136 ++++- include/trace/events/drm.h | 68 +++ include/trace/events/dyndbg.h | 74 +++ lib/Kconfig.debug | 11 + lib/Makefile | 1 + lib/dynamic_debug.c | 487 +++++++++++++++--- lib/test_dynamic_debug.c | 172 +++++++ 18 files changed, 1049 insertions(+), 129 deletions(-) create mode 100644 include/trace/events/drm.h create mode 100644 include/trace/events/dyndbg.h create mode 100644 lib/test_dynamic_debug.cSignature · 1 line
2.35.1
Signature · 3 lines
Daniel Vetter Software Engineer, Intel Corporation http://blog.ffwll.ch
[email protected]
maintainerQuoted 40 lines · Daniel Vetter
Quoted 9 lines · Jim Cromie
DRM.debug API is 23 macros, issuing 10 exclusive categories of debug messages. By rough count, they are used 5140 times in the kernel. These all call
drm_dbgordrm_devdbg, which calldrm_debug_enabled(), which checks bits in global__drm_debug. Some of these are page-flips and vblanks, and get called often.
DYNAMIC_DEBUG(withCONFIG_JUMP_LABEL) is built to avoid this kind of work, with NOOPd jump/callsites.Quoted 7 lines
This patchset is RFC because:
- it touches 2.5 subsystems: dyndbg, drm, tracefs (new events)
- dyndbg class support is built for drm, needs it for validation
- new api, used by drm
- big memory impact, with 5100 new pr-debug callsites.
- drm class bikeshedding opportunities
- others, names etc.Thanks a lot for keeping on pushing this!
Quoted 12 lines
DYNAMIC_DEBUG:RFC:
dynamic_debug_register_classes()cannot act early enough to be in effect at module-load. So this will not work as you'd reasonably expect:Quoted 6 lines
modprobe
test_dynamic_debugdyndbg='+pfm; class FOO +pfmlt'The 1st query:+pfm will be enabled during load, but in the 2nd query, "class FOO" will be unknown at load time. Early class enablement would be nice.
DYNAMIC_DEBUG_CLASSESis a static initializer, which is certainly early enough, but Im missing a trick, suggestions?
Quoted 7 lines
So maybe I'm just totally overloading this work here so feel free to ignore or postpone, but: Could we do the
dynamic_debug_register_classes()automatically at module load as a new special section? And then throw in a bit of kbuild so that in a given subsystem every driver gets the same class names by default and everything would just work, without having to sprinkle calls todynamic_debug_register_classes()all over the place?
This is now done; Ive added __dyndbg_classes section. load_module() now grabs it from the .ko
and ddebug_add_module() attaches it to the module's ddebug_table record. for builtins, dynamic_debug_init feeds the builtin class-maps to ddebug_add_module
bash-5.1# modprobe test_dynamic_debug dyndbg="class FOO +p"
[ 88.374722] dyndbg: class[0]: nm:test_dynamic_debug base:20 len:7 ty:1 [ 88.375158] dyndbg: 0: EMERG [ 88.375345] dyndbg: 1: DANGER [ 88.375540] dyndbg: 2: ERROR [ 88.375726] dyndbg: 3: WARNING [ 88.375930] dyndbg: 4: NOTICE [ 88.376130] dyndbg: 5: INFO [ 88.376310] dyndbg: 6: DEBUG [ 88.376499] dyndbg: class[1]: nm:test_dynamic_debug base:12 len:3 ty:1 [ 88.376903] dyndbg: 0: ONE [ 88.377079] dyndbg: 1: TWO [ 88.377253] dyndbg: 2: THREE [ 88.377441] dyndbg: class[2]: nm:test_dynamic_debug base:8 len:3 ty:0 [ 88.377837] dyndbg: 0: bing [ 88.378022] dyndbg: 1: bong [ 88.378203] dyndbg: 2: boom [ 88.378387] dyndbg: class[3]: nm:test_dynamic_debug base:4 len:3 ty:0 [ 88.378800] dyndbg: 0: Foo [ 88.378986] dyndbg: 1: Bar [ 88.379167] dyndbg: 2: Buzz [ 88.379348] dyndbg: class[4]: nm:test_dynamic_debug base:0 len:3 ty:0 [ 88.379757] dyndbg: 0: FOO [ 88.379938] dyndbg: 1: BAR [ 88.380136] dyndbg: 2: BUZZ [ 88.380410] dyndbg: module:test_dynamic_debug attached 5 classes [ 88.380881] dyndbg: 24 debug prints in module test_dynamic_debug [ 88.381315] dyndbg: module: test_dynamic_debug dyndbg="class FOO +p" [ 88.381714] dyndbg: query 0: "class FOO +p" mod:test_dynamic_debug [ 88.382109] dyndbg: split into words: "class" "FOO" "+p" [ 88.382445] dyndbg: op='+' [ 88.382616] dyndbg: flags=0x1 [ 88.382802] dyndbg: *flagsp=0x1 *maskp=0xffffffff [ 88.383101] dyndbg: parsed: func="" file="" module="test_dynamic_debug" format="" lineno=0-0 class=FOO [ 88.383740] dyndbg: applied: func="" file="" module="test_dynamic_debug" format="" lineno=0-0 class=FOO [ 88.384324] dyndbg: processed 1 queries, with 2 matches, 0 errs
bash-5.1#
so its working at module-load time.
Quoted 4 lines
For the entire class approach, did you spot another subsystem that could benefit from this and maybe make a more solid case that this is something good?
I had been working on the premise that ~4k drm*dbg callsites was a good case.
verbosity-levels - with x<y logic instead of x==y is what's currently missing.
the next revision adds something, which "kinda works". But I think I'll rip it out, and do this simpler approach instead:
implement a verbose/levels param & callback, which takes
echo 3 > /sys/module/foo/parameters/debug_verbosity
and effectively does
echo <<EOQRY > /proc/dynamic_debug/control
module foo class V1 +p
module foo class V2 +p
module foo class V3 +p
module foo class V4 -p
module foo class V5 -p
module foo class V6 -p
module foo class V7 -p
module foo class V8 -p
EOQRY
since only real +/-p changes incur kernel-patching costs, the remaining overheads are minimal.
Quoted 6 lines
RFC for DRM:
- decoration flags "fmlt" do not work on drm_*dbg(). (drm_*dbg() dont use
pr_debug, they *become* one flavor of them) this could (should?) be added, and maybe tailored for drm. some of the device prefixes are very long, a "d" flag could optionalize
them.
I'm lost what the fmlt decoration flags are?
The flags are::
p enables the pr_debug() callsite. f Include the function name in the printed message l Include line number in the printed message m Include module name in the printed message t Include thread ID in messages not generated from interrupt context _ No flags are set. (Or'd with others on input)
the fmlt flags add a "decoration" prefix to enabled/printed log messages
Quoted 7 lines
- api use needs review wrt drm life-cycle.
Quoted 1 line
enum
drm_debug_categoryandDYNAMIC_DEBUG_CLASSEScould be together?Hm if they're tied to module lifetime we should be good? Not sure what could go wrong here.
with the new __section, "life-cycle" doesnt really pertain. the new issue is how the class-maps are shared across the subsystem; the current class-maps list for each module will probably break; a list item cannot be on N different lists of different modules. Altering the list-items to ref the class-map (not contain it) should solve the problem.
Quoted 9 lines
Quoted 3 lines
- class-names could stand review, perhaps extension "drm:core:" etc have appeared (maybe just from me) or a "plan" to look at it later
Yeah it's been a bit sprawling. I'm kinda hoping that by firmly establishing dyndbg as the drm debug approach we can cut down for the need for ad-hoc flags a bit.
yeah thats why I kept the DRM_UT_* names.
OTOH - the symbolic names patch exposes the choices, which locks the names as API ??
Quoted 9 lines
Quoted 4 lines
- i915 & amdgpu have
pr_debugs(DC_LOG_*, gvt_dbg_*) that have class-ish prefixes that are separate from, but similar to DRM_UT_*, and could stand review and possible unification with reformed or extended drm categories.Yeah drm is not entirely consistent with how exactly driver debug printing should be done. Another reason why I'm hoping that the kitchen sync with everything approach you're doing here could help unify things.
the decoration flags can help here; they loosely/precisely describe the elements of most/all the current debug format-prefix variations. So case by case, the ad-hoc variations should map onto these flags,
The flags allow selectively dropping the prefix info from some of the log entries,
after you've seen the module name and function a dozen times, it's helpful to reduce screen clutter.
It might make sense to add a new flag for device,
so that dev_dbg() flavors can shorten-or-skip the longer device strings, maybe some drm specific flavors.
Quoted 9 lines
Quoted 5 lines
- the change to enum
drm_debug_categoryfrom bitmask values to 0..31 means that we foreclose this possiblility:drm_dbg(DRM_UT_CORE|DRM_UT_KMS, "wierd double-cat experiment");Yeah no, that doesn't make much sense to me :-)
no chuckles for the schrodinger's cat joke ?
(maybe "yeah no" is the artful superpositional reply, I just caught :)
Quoted 4 lines
Quoted 2 lines
- nouveau has very few drm.debug calls,
hasNV_DEBUG,VMM_DEBUG,nvkm_printk_, I havent looked deeply.
nouveau has like levels, man ..test_dynamic_debug implements its priority-style names as a POC
patch 18 converts nvkm_debug/trace to use dev_dbg instead of dev_info it probably could adapt to use drm_devdbg
Quoted 4 lines
Yeah see above. There's a pile more drivers (more on the armsoc side of things) which are quite big on the raw debug call approach.
LOW, MID, HI has been proposed at least once wrt dyndbg. that probably fits well with current disjoint classes. level/verbose classes should be practical too, as described above.
NB: The symbolic names should also work
echo +MID > /sys/module/foobar/parameters/debug_verbosity
though theres some ambiguity with
echo -V3 > /sys/module/foobar/parameters/debug_verbosity
that should turn off V4,5,6,
but what about V1,2 ?
it could leave them alone (whatever their previous settings are)
anyway, lkp-robot and igt-trybot should be grinding on the latest patchset soon,
I'll send it after I fix whatever breaks.
Quoted 2 lines
Cheers, Daniel
thanks,
Jim
Quoted 94 lines · On Mon, Jun 06, 2022 at 08:59:36AM -0600, [email protected] wrote:
Quoted 40 lines · Daniel Vetter
Quoted 9 lines · Jim Cromie
DRM.debug API is 23 macros, issuing 10 exclusive categories of debug messages. By rough count, they are used 5140 times in the kernel. These all call
drm_dbgordrm_devdbg, which calldrm_debug_enabled(), which checks bits in global__drm_debug. Some of these are page-flips and vblanks, and get called often.
DYNAMIC_DEBUG(withCONFIG_JUMP_LABEL) is built to avoid this kind of work, with NOOPd jump/callsites.Quoted 7 lines
This patchset is RFC because:
- it touches 2.5 subsystems: dyndbg, drm, tracefs (new events)
- dyndbg class support is built for drm, needs it for validation
- new api, used by drm
- big memory impact, with 5100 new pr-debug callsites.
- drm class bikeshedding opportunities
- others, names etc.Thanks a lot for keeping on pushing this!
Quoted 12 lines
DYNAMIC_DEBUG:RFC:
dynamic_debug_register_classes()cannot act early enough to be in effect at module-load. So this will not work as you'd reasonably expect:Quoted 6 lines
modprobe
test_dynamic_debugdyndbg='+pfm; class FOO +pfmlt'The 1st query:+pfm will be enabled during load, but in the 2nd query, "class FOO" will be unknown at load time. Early class enablement would be nice.
DYNAMIC_DEBUG_CLASSESis a static initializer, which is certainly early enough, but Im missing a trick, suggestions?Quoted 7 lines
So maybe I'm just totally overloading this work here so feel free to ignore or postpone, but: Could we do the
dynamic_debug_register_classes()automatically at module load as a new special section? And then throw in a bit of kbuild so that in a given subsystem every driver gets the same class names by default and everything would just work, without having to sprinkle calls todynamic_debug_register_classes()all over the place?This is now done; Ive added
__dyndbg_classessection.load_module()now grabs it from the .ko
andddebug_add_module()attaches it to the module'sddebug_tablerecord. for builtins,dynamic_debug_initfeeds the builtin class-maps toddebug_add_modulebash-5.1# modprobe
test_dynamic_debugdyndbg="class FOO +p"[ 88.374722] dyndbg: class[0]: nm:test_dynamic_debug base:20 len:7 ty:1 [ 88.375158] dyndbg: 0: EMERG [ 88.375345] dyndbg: 1: DANGER [ 88.375540] dyndbg: 2: ERROR [ 88.375726] dyndbg: 3: WARNING [ 88.375930] dyndbg: 4: NOTICE [ 88.376130] dyndbg: 5: INFO [ 88.376310] dyndbg: 6: DEBUG [ 88.376499] dyndbg: class[1]: nm:test_dynamic_debug base:12 len:3 ty:1 [ 88.376903] dyndbg: 0: ONE [ 88.377079] dyndbg: 1: TWO [ 88.377253] dyndbg: 2: THREE [ 88.377441] dyndbg: class[2]: nm:test_dynamic_debug base:8 len:3 ty:0 [ 88.377837] dyndbg: 0: bing [ 88.378022] dyndbg: 1: bong [ 88.378203] dyndbg: 2: boom [ 88.378387] dyndbg: class[3]: nm:test_dynamic_debug base:4 len:3 ty:0 [ 88.378800] dyndbg: 0: Foo [ 88.378986] dyndbg: 1: Bar [ 88.379167] dyndbg: 2: Buzz [ 88.379348] dyndbg: class[4]: nm:test_dynamic_debug base:0 len:3 ty:0 [ 88.379757] dyndbg: 0: FOO [ 88.379938] dyndbg: 1: BAR [ 88.380136] dyndbg: 2: BUZZ [ 88.380410] dyndbg: module:test_dynamic_debug attached 5 classes [ 88.380881] dyndbg: 24 debug prints in module test_dynamic_debug [ 88.381315] dyndbg: module: test_dynamic_debug dyndbg="class FOO +p" [ 88.381714] dyndbg: query 0: "class FOO +p" mod:test_dynamic_debug [ 88.382109] dyndbg: split into words: "class" "FOO" "+p" [ 88.382445] dyndbg: op='+' [ 88.382616] dyndbg: flags=0x1 [ 88.382802] dyndbg: *flagsp=0x1 *maskp=0xffffffff [ 88.383101] dyndbg: parsed: func="" file="" module="test_dynamic_debug" format="" lineno=0-0 class=FOO [ 88.383740] dyndbg: applied: func="" file="" module="test_dynamic_debug" format="" lineno=0-0 class=FOO [ 88.384324] dyndbg: processed 1 queries, with 2 matches, 0 errs
Quoted 3 lines
bash-5.1#
so its working at module-load time.
Awesome!
Quoted 7 lines
Quoted 4 lines
For the entire class approach, did you spot another subsystem that could benefit from this and maybe make a more solid case that this is something good?
I had been working on the premise that ~4k drm*dbg callsites was a good case.
Oh I'm happy with just drm, but occasionally we've done stuff in drm that the wider kernel community found a bit silly. So bit more acks/validation from outside the dri-devel echo chamber would be great, whatever form it is.
Quoted 48 lines
verbosity-levels - with x<y logic instead of x==y is what's currently missing.
the next revision adds something, which "kinda works". But I think I'll rip it out, and do this simpler approach instead:
implement a verbose/levels param & callback, which takes
echo 3 >
/sys/module/foo/parameters/debug_verbosityand effectively does
echo <<EOQRY >
/proc/dynamic_debug/control
module foo class V1 +p
module foo class V2 +p
module foo class V3 +p
module foo class V4 -p
module foo class V5 -p
module foo class V6 -p
module foo class V7 -p
module foo class V8 -p
EOQRYsince only real +/-p changes incur kernel-patching costs, the remaining overheads are minimal.
Quoted 6 lines
RFC for DRM:
- decoration flags "fmlt" do not work on drm_*dbg(). (drm_*dbg() dont use
pr_debug, they *become* one flavor of them) this could (should?) be added, and maybe tailored for drm. some of the device prefixes are very long, a "d" flag could optionalizethem.
I'm lost what the fmlt decoration flags are?
The flags are::
p enables the pr_debug() callsite. f Include the function name in the printed message l Include line number in the printed message m Include module name in the printed message t Include thread ID in messages not generated from interrupt context _ No flags are set. (Or'd with others on input)
Quoted 1 line
the fmlt flags add a "decoration" prefix to enabled/printed log messages
Oh I was just confused and thought fmlt was some special format thing, and not just the list of letters that wond work due to the implementation.
If you havent, maybe just spell the above list out (like you do here) in the docs?
Quoted 21 lines
Quoted 7 lines
- api use needs review wrt drm life-cycle.
Quoted 1 line
enum
drm_debug_categoryandDYNAMIC_DEBUG_CLASSEScould be together?Hm if they're tied to module lifetime we should be good? Not sure what could go wrong here.
with the new
__section, "life-cycle" doesnt really pertain. the new issue is how the class-maps are shared across the subsystem; the current class-maps list for each module will probably break; a list item cannot be on N different lists of different modules. Altering the list-items to ref the class-map (not contain it) should solve the problem.Quoted 4 lines
Quoted 3 lines
- class-names could stand review, perhaps extension "drm:core:" etc have appeared (maybe just from me) or a "plan" to look at it later
Quoted 7 lines
Quoted 5 lines
Yeah it's been a bit sprawling. I'm kinda hoping that by firmly establishing dyndbg as the drm debug approach we can cut down for the need for ad-hoc flags a bit.
yeah thats why I kept the DRM_UT_* names.
OTOH - the symbolic names patch exposes the choices, which locks the names as API ??
Yeah that part is fine. It's more because the flags was the only thing we ever had, any debug need was solved with them. With dyndbg we should have a lot more and a lot more precise options for handling this.
So I'm not worried about the flags and their names per-se, more that we had some pressure to add more flags for specific files and libraries. Dyndbg should give us a much more powerful tool for these problems.
Quoted 67 lines
Quoted 9 lines
Quoted 4 lines
- i915 & amdgpu have
pr_debugs(DC_LOG_*, gvt_dbg_*) that have class-ish prefixes that are separate from, but similar to DRM_UT_*, and could stand review and possible unification with reformed or extended drm categories.Yeah drm is not entirely consistent with how exactly driver debug printing should be done. Another reason why I'm hoping that the kitchen sync with everything approach you're doing here could help unify things.
the decoration flags can help here; they loosely/precisely describe the elements of most/all the current debug format-prefix variations. So case by case, the ad-hoc variations should map onto these flags,
The flags allow selectively dropping the prefix info from some of the log entries,
after you've seen the module name and function a dozen times, it's helpful to reduce screen clutter.It might make sense to add a new flag for device,
so thatdev_dbg()flavors can shorten-or-skip the longer device strings, maybe some drm specific flavors.Quoted 9 lines
Quoted 5 lines
- the change to enum
drm_debug_categoryfrom bitmask values to 0..31 means that we foreclose this possiblility:drm_dbg(DRM_UT_CORE|DRM_UT_KMS, "wierd double-cat experiment");Yeah no, that doesn't make much sense to me :-)
no chuckles for the schrodinger's cat joke ?
(maybe "yeah no" is the artful superpositional reply, I just caught :)
Quoted 4 lines
Quoted 2 lines
- nouveau has very few drm.debug calls,
hasNV_DEBUG,VMM_DEBUG,nvkm_printk_, I havent looked deeply.nouveau has like levels, man ..
test_dynamic_debugimplements its priority-style names as a POCpatch 18 converts nvkm_debug/trace to use
dev_dbginstead ofdev_infoit probably could adapt to usedrm_devdbgQuoted 4 lines
Yeah see above. There's a pile more drivers (more on the armsoc side of things) which are quite big on the raw debug call approach.
LOW, MID, HI has been proposed at least once wrt dyndbg. that probably fits well with current disjoint classes. level/verbose classes should be practical too, as described above.
NB: The symbolic names should also work
echo +MID >
/sys/module/foobar/parameters/debug_verbositythough theres some ambiguity with
echo -V3 >
/sys/module/foobar/parameters/debug_verbosity
Quoted 7 lines
that should turn off V4,5,6,
but what about V1,2 ?
it could leave them alone (whatever their previous settings are)anyway, lkp-robot and igt-trybot should be grinding on the latest patchset soon,
I'll send it after I fix whatever breaks.
Awesome, like I said I'm a bit drowned in everything, but I'm really happy you're pushing this!
-Daniel
Quoted 8 lines
Quoted 5 lines
Cheers, Daniel
thanks,
Jim
Signature · 3 lines
Daniel Vetter Software Engineer, Intel Corporation http://blog.ffwll.ch