* [PATCH v3 1/1] drm/xe/guc: Fix GuC log/ct output via debugfs
@ 2025-01-07 20:22 Julia Filipchuk
2025-01-07 20:57 ` ✓ CI.Patch_applied: success for series starting with [v3,1/1] " Patchwork
` (8 more replies)
0 siblings, 9 replies; 22+ messages in thread
From: Julia Filipchuk @ 2025-01-07 20:22 UTC (permalink / raw)
To: intel-xe; +Cc: Julia Filipchuk
Change to disable asci85 GuC logging only when output to devcoredump
(was temporarily disabled for all code paths).
v2: Ignore only for devcoredump case (not dmesg output).
v3: Rebase to resolve parent tag mismatch.
Signed-off-by: Julia Filipchuk <julia.filipchuk@intel.com>
---
drivers/gpu/drm/xe/xe_devcoredump.c | 8 +++++---
include/drm/drm_print.h | 2 ++
2 files changed, 7 insertions(+), 3 deletions(-)
diff --git a/drivers/gpu/drm/xe/xe_devcoredump.c b/drivers/gpu/drm/xe/xe_devcoredump.c
index 6980304c8903..8e5d1f9866a7 100644
--- a/drivers/gpu/drm/xe/xe_devcoredump.c
+++ b/drivers/gpu/drm/xe/xe_devcoredump.c
@@ -424,10 +424,12 @@ void xe_print_blob_ascii85(struct drm_printer *p, const char *prefix,
* Splitting blobs across multiple lines is not compatible with the mesa
* debug decoder tool. Note that even dropping the explicit '\n' below
* doesn't help because the GuC log is so big some underlying implementation
- * still splits the lines at 512K characters. So just bail completely for
- * the moment.
+ * still splits the lines at 512K characters.
+ *
+ * Only disable from devcoredump output.
*/
- return;
+ if (p->coredump)
+ return;
#define DMESG_MAX_LINE_LEN 800
#define MIN_SPACE (ASCII85_BUFSZ + 2) /* 85 + "\n\0" */
diff --git a/include/drm/drm_print.h b/include/drm/drm_print.h
index f77fe1531cf8..f5ea7f38ba09 100644
--- a/include/drm/drm_print.h
+++ b/include/drm/drm_print.h
@@ -182,6 +182,7 @@ struct drm_printer {
unsigned int counter;
} line;
enum drm_debug_category category;
+ bool coredump;
};
void __drm_printfn_coredump(struct drm_printer *p, struct va_format *vaf);
@@ -335,6 +336,7 @@ drm_coredump_printer(struct drm_print_iterator *iter)
.printfn = __drm_printfn_coredump,
.puts = __drm_puts_coredump,
.arg = iter,
+ .coredump = true,
};
/* Set the internal offset of the iterator to zero */
--
2.47.1
^ permalink raw reply related [flat|nested] 22+ messages in thread* ✓ CI.Patch_applied: success for series starting with [v3,1/1] drm/xe/guc: Fix GuC log/ct output via debugfs 2025-01-07 20:22 [PATCH v3 1/1] drm/xe/guc: Fix GuC log/ct output via debugfs Julia Filipchuk @ 2025-01-07 20:57 ` Patchwork 2025-01-07 20:58 ` ✓ CI.checkpatch: " Patchwork ` (7 subsequent siblings) 8 siblings, 0 replies; 22+ messages in thread From: Patchwork @ 2025-01-07 20:57 UTC (permalink / raw) To: Julia Filipchuk; +Cc: intel-xe == Series Details == Series: series starting with [v3,1/1] drm/xe/guc: Fix GuC log/ct output via debugfs URL : https://patchwork.freedesktop.org/series/143203/ State : success == Summary == === Applying kernel patches on branch 'drm-tip' with base: === Base commit: dbd476153d41 drm-tip: 2025y-01m-07d-19h-16m-14s UTC integration manifest === git am output follows === Applying: drm/xe/guc: Fix GuC log/ct output via debugfs ^ permalink raw reply [flat|nested] 22+ messages in thread
* ✓ CI.checkpatch: success for series starting with [v3,1/1] drm/xe/guc: Fix GuC log/ct output via debugfs 2025-01-07 20:22 [PATCH v3 1/1] drm/xe/guc: Fix GuC log/ct output via debugfs Julia Filipchuk 2025-01-07 20:57 ` ✓ CI.Patch_applied: success for series starting with [v3,1/1] " Patchwork @ 2025-01-07 20:58 ` Patchwork 2025-01-07 20:59 ` ✓ CI.KUnit: " Patchwork ` (6 subsequent siblings) 8 siblings, 0 replies; 22+ messages in thread From: Patchwork @ 2025-01-07 20:58 UTC (permalink / raw) To: Julia Filipchuk; +Cc: intel-xe == Series Details == Series: series starting with [v3,1/1] drm/xe/guc: Fix GuC log/ct output via debugfs URL : https://patchwork.freedesktop.org/series/143203/ State : success == Summary == + KERNEL=/kernel + git clone https://gitlab.freedesktop.org/drm/maintainer-tools mt Cloning into 'mt'... warning: redirecting to https://gitlab.freedesktop.org/drm/maintainer-tools.git/ + git -C mt rev-list -n1 origin/master 30ab6715fc09baee6cc14cb3c89ad8858688d474 + cd /kernel + git config --global --add safe.directory /kernel + git log -n1 commit fcb2a296a2af5aa8166d2f6003653de81ec500b7 Author: Julia Filipchuk <julia.filipchuk@intel.com> Date: Tue Jan 7 12:22:52 2025 -0800 drm/xe/guc: Fix GuC log/ct output via debugfs Change to disable asci85 GuC logging only when output to devcoredump (was temporarily disabled for all code paths). v2: Ignore only for devcoredump case (not dmesg output). v3: Rebase to resolve parent tag mismatch. Signed-off-by: Julia Filipchuk <julia.filipchuk@intel.com> + /mt/dim checkpatch dbd476153d41352ad6022088be16301051b9bce7 drm-intel fcb2a296a2af drm/xe/guc: Fix GuC log/ct output via debugfs ^ permalink raw reply [flat|nested] 22+ messages in thread
* ✓ CI.KUnit: success for series starting with [v3,1/1] drm/xe/guc: Fix GuC log/ct output via debugfs 2025-01-07 20:22 [PATCH v3 1/1] drm/xe/guc: Fix GuC log/ct output via debugfs Julia Filipchuk 2025-01-07 20:57 ` ✓ CI.Patch_applied: success for series starting with [v3,1/1] " Patchwork 2025-01-07 20:58 ` ✓ CI.checkpatch: " Patchwork @ 2025-01-07 20:59 ` Patchwork 2025-01-07 21:10 ` [PATCH v3 1/1] " Lucas De Marchi ` (5 subsequent siblings) 8 siblings, 0 replies; 22+ messages in thread From: Patchwork @ 2025-01-07 20:59 UTC (permalink / raw) To: Julia Filipchuk; +Cc: intel-xe == Series Details == Series: series starting with [v3,1/1] drm/xe/guc: Fix GuC log/ct output via debugfs URL : https://patchwork.freedesktop.org/series/143203/ State : success == Summary == + trap cleanup EXIT + /kernel/tools/testing/kunit/kunit.py run --kunitconfig /kernel/drivers/gpu/drm/xe/.kunitconfig [20:58:01] Configuring KUnit Kernel ... Generating .config ... Populating config with: $ make ARCH=um O=.kunit olddefconfig [20:58:09] Building KUnit Kernel ... Populating config with: $ make ARCH=um O=.kunit olddefconfig Building with: $ make all compile_commands.json ARCH=um O=.kunit --jobs=48 ../lib/iomap.c:156:5: warning: no previous prototype for ‘ioread64_lo_hi’ [-Wmissing-prototypes] 156 | u64 ioread64_lo_hi(const void __iomem *addr) | ^~~~~~~~~~~~~~ ../lib/iomap.c:163:5: warning: no previous prototype for ‘ioread64_hi_lo’ [-Wmissing-prototypes] 163 | u64 ioread64_hi_lo(const void __iomem *addr) | ^~~~~~~~~~~~~~ ../lib/iomap.c:170:5: warning: no previous prototype for ‘ioread64be_lo_hi’ [-Wmissing-prototypes] 170 | u64 ioread64be_lo_hi(const void __iomem *addr) | ^~~~~~~~~~~~~~~~ ../lib/iomap.c:178:5: warning: no previous prototype for ‘ioread64be_hi_lo’ [-Wmissing-prototypes] 178 | u64 ioread64be_hi_lo(const void __iomem *addr) | ^~~~~~~~~~~~~~~~ ../lib/iomap.c:264:6: warning: no previous prototype for ‘iowrite64_lo_hi’ [-Wmissing-prototypes] 264 | void iowrite64_lo_hi(u64 val, void __iomem *addr) | ^~~~~~~~~~~~~~~ ../lib/iomap.c:272:6: warning: no previous prototype for ‘iowrite64_hi_lo’ [-Wmissing-prototypes] 272 | void iowrite64_hi_lo(u64 val, void __iomem *addr) | ^~~~~~~~~~~~~~~ ../lib/iomap.c:280:6: warning: no previous prototype for ‘iowrite64be_lo_hi’ [-Wmissing-prototypes] 280 | void iowrite64be_lo_hi(u64 val, void __iomem *addr) | ^~~~~~~~~~~~~~~~~ ../lib/iomap.c:288:6: warning: no previous prototype for ‘iowrite64be_hi_lo’ [-Wmissing-prototypes] 288 | void iowrite64be_hi_lo(u64 val, void __iomem *addr) | ^~~~~~~~~~~~~~~~~ [20:59:05] Starting KUnit Kernel (1/1)... [20:59:05] ============================================================ Running tests with: $ .kunit/linux kunit.enable=1 mem=1G console=tty kunit_shutdown=halt [20:59:05] =================== guc_dbm (7 subtests) =================== [20:59:05] [PASSED] test_empty [20:59:05] [PASSED] test_default [20:59:05] ======================== test_size ======================== [20:59:05] [PASSED] 4 [20:59:05] [PASSED] 8 [20:59:05] [PASSED] 32 [20:59:05] [PASSED] 256 [20:59:05] ==================== [PASSED] test_size ==================== [20:59:05] ======================= test_reuse ======================== [20:59:05] [PASSED] 4 [20:59:05] [PASSED] 8 [20:59:05] [PASSED] 32 [20:59:05] [PASSED] 256 [20:59:05] =================== [PASSED] test_reuse ==================== [20:59:05] =================== test_range_overlap ==================== [20:59:05] [PASSED] 4 [20:59:05] [PASSED] 8 [20:59:05] [PASSED] 32 [20:59:05] [PASSED] 256 [20:59:05] =============== [PASSED] test_range_overlap ================ [20:59:05] =================== test_range_compact ==================== [20:59:05] [PASSED] 4 [20:59:05] [PASSED] 8 [20:59:05] [PASSED] 32 [20:59:05] [PASSED] 256 [20:59:05] =============== [PASSED] test_range_compact ================ [20:59:05] ==================== test_range_spare ===================== [20:59:05] [PASSED] 4 [20:59:05] [PASSED] 8 [20:59:05] [PASSED] 32 [20:59:05] [PASSED] 256 [20:59:05] ================ [PASSED] test_range_spare ================= [20:59:05] ===================== [PASSED] guc_dbm ===================== [20:59:05] =================== guc_idm (6 subtests) =================== [20:59:05] [PASSED] bad_init [20:59:05] [PASSED] no_init [20:59:05] [PASSED] init_fini [20:59:05] [PASSED] check_used [20:59:05] [PASSED] check_quota [20:59:05] [PASSED] check_all [20:59:05] ===================== [PASSED] guc_idm ===================== [20:59:05] ================== no_relay (3 subtests) =================== [20:59:05] [PASSED] xe_drops_guc2pf_if_not_ready [20:59:05] [PASSED] xe_drops_guc2vf_if_not_ready [20:59:05] [PASSED] xe_rejects_send_if_not_ready [20:59:05] ==================== [PASSED] no_relay ===================== [20:59:05] ================== pf_relay (14 subtests) ================== [20:59:05] [PASSED] pf_rejects_guc2pf_too_short [20:59:05] [PASSED] pf_rejects_guc2pf_too_long [20:59:05] [PASSED] pf_rejects_guc2pf_no_payload [20:59:05] [PASSED] pf_fails_no_payload [20:59:05] [PASSED] pf_fails_bad_origin [20:59:05] [PASSED] pf_fails_bad_type [20:59:05] [PASSED] pf_txn_reports_error [20:59:05] [PASSED] pf_txn_sends_pf2guc [20:59:05] [PASSED] pf_sends_pf2guc [20:59:05] [SKIPPED] pf_loopback_nop [20:59:05] [SKIPPED] pf_loopback_echo [20:59:05] [SKIPPED] pf_loopback_fail [20:59:05] [SKIPPED] pf_loopback_busy [20:59:05] [SKIPPED] pf_loopback_retry [20:59:05] ==================== [PASSED] pf_relay ===================== [20:59:05] ================== vf_relay (3 subtests) =================== [20:59:05] [PASSED] vf_rejects_guc2vf_too_short [20:59:05] [PASSED] vf_rejects_guc2vf_too_long [20:59:05] [PASSED] vf_rejects_guc2vf_no_payload [20:59:05] ==================== [PASSED] vf_relay ===================== [20:59:05] ================= pf_service (11 subtests) ================= [20:59:05] [PASSED] pf_negotiate_any [20:59:05] [PASSED] pf_negotiate_base_match [20:59:05] [PASSED] pf_negotiate_base_newer [20:59:05] [PASSED] pf_negotiate_base_next [20:59:05] [SKIPPED] pf_negotiate_base_older [20:59:05] [PASSED] pf_negotiate_base_prev [20:59:05] [PASSED] pf_negotiate_latest_match [20:59:05] [PASSED] pf_negotiate_latest_newer [20:59:05] [PASSED] pf_negotiate_latest_next [20:59:05] [SKIPPED] pf_negotiate_latest_older [20:59:05] [SKIPPED] pf_negotiate_latest_prev [20:59:05] =================== [PASSED] pf_service ==================== [20:59:05] ===================== lmtt (1 subtest) ===================== [20:59:05] ======================== test_ops ========================= [20:59:05] [PASSED] 2-level [20:59:05] [PASSED] multi-level [20:59:05] ==================== [PASSED] test_ops ===================== [20:59:05] ====================== [PASSED] lmtt ======================= [20:59:05] =================== xe_mocs (2 subtests) =================== [20:59:05] ================ xe_live_mocs_kernel_kunit ================ [20:59:05] =========== [SKIPPED] xe_live_mocs_kernel_kunit ============ [20:59:05] ================ xe_live_mocs_reset_kunit ================= [20:59:05] ============ [SKIPPED] xe_live_mocs_reset_kunit ============ [20:59:05] ==================== [SKIPPED] xe_mocs ===================== [20:59:05] ================= xe_migrate (2 subtests) ================== [20:59:05] ================= xe_migrate_sanity_kunit ================= [20:59:05] ============ [SKIPPED] xe_migrate_sanity_kunit ============= [20:59:05] ================== xe_validate_ccs_kunit ================== [20:59:05] ============= [SKIPPED] xe_validate_ccs_kunit ============== [20:59:05] =================== [SKIPPED] xe_migrate =================== [20:59:05] ================== xe_dma_buf (1 subtest) ================== [20:59:05] ==================== xe_dma_buf_kunit ===================== [20:59:05] ================ [SKIPPED] xe_dma_buf_kunit ================ [20:59:05] =================== [SKIPPED] xe_dma_buf =================== [20:59:05] ================= xe_bo_shrink (1 subtest) ================= [20:59:05] =================== xe_bo_shrink_kunit ==================== [20:59:05] =============== [SKIPPED] xe_bo_shrink_kunit =============== [20:59:05] ================== [SKIPPED] xe_bo_shrink ================== [20:59:05] ==================== xe_bo (2 subtests) ==================== [20:59:05] ================== xe_ccs_migrate_kunit =================== [20:59:05] ============== [SKIPPED] xe_ccs_migrate_kunit ============== [20:59:05] ==================== xe_bo_evict_kunit ==================== [20:59:05] =============== [SKIPPED] xe_bo_evict_kunit ================ [20:59:05] ===================== [SKIPPED] xe_bo ====================== [20:59:05] ==================== args (11 subtests) ==================== [20:59:05] [PASSED] count_args_test [20:59:05] [PASSED] call_args_example [20:59:05] [PASSED] call_args_test [20:59:05] [PASSED] drop_first_arg_example [20:59:05] [PASSED] drop_first_arg_test [20:59:05] [PASSED] first_arg_example [20:59:05] [PASSED] first_arg_test stty: 'standard input': Inappropriate ioctl for device [20:59:05] [PASSED] last_arg_example [20:59:05] [PASSED] last_arg_test [20:59:05] [PASSED] pick_arg_example [20:59:05] [PASSED] sep_comma_example [20:59:05] ====================== [PASSED] args ======================= [20:59:05] =================== xe_pci (2 subtests) ==================== [20:59:05] [PASSED] xe_gmdid_graphics_ip [20:59:05] [PASSED] xe_gmdid_media_ip [20:59:05] ===================== [PASSED] xe_pci ====================== [20:59:05] =================== xe_rtp (2 subtests) ==================== [20:59:05] =============== xe_rtp_process_to_sr_tests ================ [20:59:05] [PASSED] coalesce-same-reg [20:59:05] [PASSED] no-match-no-add [20:59:05] [PASSED] match-or [20:59:05] [PASSED] match-or-xfail [20:59:05] [PASSED] no-match-no-add-multiple-rules [20:59:05] [PASSED] two-regs-two-entries [20:59:05] [PASSED] clr-one-set-other [20:59:05] [PASSED] set-field [20:59:05] [PASSED] conflict-duplicate [20:59:05] [PASSED] conflict-not-disjoint [20:59:05] [PASSED] conflict-reg-type [20:59:05] =========== [PASSED] xe_rtp_process_to_sr_tests ============ [20:59:05] ================== xe_rtp_process_tests =================== [20:59:05] [PASSED] active1 [20:59:05] [PASSED] active2 [20:59:05] [PASSED] active-inactive [20:59:05] [PASSED] inactive-active [20:59:05] [PASSED] inactive-1st_or_active-inactive [20:59:05] [PASSED] inactive-2nd_or_active-inactive [20:59:05] [PASSED] inactive-last_or_active-inactive [20:59:05] [PASSED] inactive-no_or_active-inactive [20:59:05] ============== [PASSED] xe_rtp_process_tests =============== [20:59:05] ===================== [PASSED] xe_rtp ====================== [20:59:05] ==================== xe_wa (1 subtest) ===================== [20:59:05] ======================== xe_wa_gt ========================= [20:59:05] [PASSED] TIGERLAKE (B0) [20:59:05] [PASSED] DG1 (A0) [20:59:05] [PASSED] DG1 (B0) [20:59:05] [PASSED] ALDERLAKE_S (A0) [20:59:05] [PASSED] ALDERLAKE_S (B0) [20:59:05] [PASSED] ALDERLAKE_S (C0) [20:59:05] [PASSED] ALDERLAKE_S (D0) [20:59:05] [PASSED] ALDERLAKE_P (A0) [20:59:05] [PASSED] ALDERLAKE_P (B0) [20:59:05] [PASSED] ALDERLAKE_P (C0) [20:59:05] [PASSED] ALDERLAKE_S_RPLS (D0) [20:59:05] [PASSED] ALDERLAKE_P_RPLU (E0) [20:59:05] [PASSED] DG2_G10 (C0) [20:59:05] [PASSED] DG2_G11 (B1) [20:59:05] [PASSED] DG2_G12 (A1) [20:59:05] [PASSED] METEORLAKE (g:A0, m:A0) [20:59:05] [PASSED] METEORLAKE (g:A0, m:A0) [20:59:05] [PASSED] METEORLAKE (g:A0, m:A0) [20:59:05] [PASSED] LUNARLAKE (g:A0, m:A0) [20:59:05] [PASSED] LUNARLAKE (g:B0, m:A0) [20:59:05] [PASSED] BATTLEMAGE (g:A0, m:A1) [20:59:05] ==================== [PASSED] xe_wa_gt ===================== [20:59:05] ====================== [PASSED] xe_wa ====================== [20:59:05] ============================================================ [20:59:05] Testing complete. Ran 122 tests: passed: 106, skipped: 16 [20:59:05] Elapsed time: 64.179s total, 7.579s configuring, 56.277s building, 0.298s running + /kernel/tools/testing/kunit/kunit.py run --kunitconfig /kernel/drivers/gpu/drm/tests/.kunitconfig [20:59:05] Configuring KUnit Kernel ... Regenerating .config ... Populating config with: $ make ARCH=um O=.kunit olddefconfig [20:59:08] Building KUnit Kernel ... Populating config with: $ make ARCH=um O=.kunit olddefconfig Building with: $ make all compile_commands.json ARCH=um O=.kunit --jobs=48 ../lib/iomap.c:156:5: warning: no previous prototype for ‘ioread64_lo_hi’ [-Wmissing-prototypes] 156 | u64 ioread64_lo_hi(const void __iomem *addr) | ^~~~~~~~~~~~~~ ../lib/iomap.c:163:5: warning: no previous prototype for ‘ioread64_hi_lo’ [-Wmissing-prototypes] 163 | u64 ioread64_hi_lo(const void __iomem *addr) | ^~~~~~~~~~~~~~ ../lib/iomap.c:170:5: warning: no previous prototype for ‘ioread64be_lo_hi’ [-Wmissing-prototypes] 170 | u64 ioread64be_lo_hi(const void __iomem *addr) | ^~~~~~~~~~~~~~~~ ../lib/iomap.c:178:5: warning: no previous prototype for ‘ioread64be_hi_lo’ [-Wmissing-prototypes] 178 | u64 ioread64be_hi_lo(const void __iomem *addr) | ^~~~~~~~~~~~~~~~ ../lib/iomap.c:264:6: warning: no previous prototype for ‘iowrite64_lo_hi’ [-Wmissing-prototypes] 264 | void iowrite64_lo_hi(u64 val, void __iomem *addr) | ^~~~~~~~~~~~~~~ ../lib/iomap.c:272:6: warning: no previous prototype for ‘iowrite64_hi_lo’ [-Wmissing-prototypes] 272 | void iowrite64_hi_lo(u64 val, void __iomem *addr) | ^~~~~~~~~~~~~~~ ../lib/iomap.c:280:6: warning: no previous prototype for ‘iowrite64be_lo_hi’ [-Wmissing-prototypes] 280 | void iowrite64be_lo_hi(u64 val, void __iomem *addr) | ^~~~~~~~~~~~~~~~~ ../lib/iomap.c:288:6: warning: no previous prototype for ‘iowrite64be_hi_lo’ [-Wmissing-prototypes] 288 | void iowrite64be_hi_lo(u64 val, void __iomem *addr) | ^~~~~~~~~~~~~~~~~ [20:59:31] Starting KUnit Kernel (1/1)... [20:59:31] ============================================================ Running tests with: $ .kunit/linux kunit.enable=1 mem=1G console=tty kunit_shutdown=halt [20:59:31] ================== drm_buddy (7 subtests) ================== [20:59:31] [PASSED] drm_test_buddy_alloc_limit [20:59:31] [PASSED] drm_test_buddy_alloc_optimistic [20:59:31] [PASSED] drm_test_buddy_alloc_pessimistic [20:59:31] [PASSED] drm_test_buddy_alloc_pathological [20:59:31] [PASSED] drm_test_buddy_alloc_contiguous [20:59:31] [PASSED] drm_test_buddy_alloc_clear [20:59:31] [PASSED] drm_test_buddy_alloc_range_bias [20:59:31] ==================== [PASSED] drm_buddy ==================== [20:59:31] ============= drm_cmdline_parser (40 subtests) ============= [20:59:31] [PASSED] drm_test_cmdline_force_d_only [20:59:31] [PASSED] drm_test_cmdline_force_D_only_dvi [20:59:31] [PASSED] drm_test_cmdline_force_D_only_hdmi [20:59:31] [PASSED] drm_test_cmdline_force_D_only_not_digital [20:59:31] [PASSED] drm_test_cmdline_force_e_only [20:59:31] [PASSED] drm_test_cmdline_res [20:59:31] [PASSED] drm_test_cmdline_res_vesa [20:59:31] [PASSED] drm_test_cmdline_res_vesa_rblank [20:59:31] [PASSED] drm_test_cmdline_res_rblank [20:59:31] [PASSED] drm_test_cmdline_res_bpp [20:59:31] [PASSED] drm_test_cmdline_res_refresh [20:59:31] [PASSED] drm_test_cmdline_res_bpp_refresh [20:59:31] [PASSED] drm_test_cmdline_res_bpp_refresh_interlaced [20:59:31] [PASSED] drm_test_cmdline_res_bpp_refresh_margins [20:59:31] [PASSED] drm_test_cmdline_res_bpp_refresh_force_off [20:59:31] [PASSED] drm_test_cmdline_res_bpp_refresh_force_on [20:59:31] [PASSED] drm_test_cmdline_res_bpp_refresh_force_on_analog [20:59:31] [PASSED] drm_test_cmdline_res_bpp_refresh_force_on_digital [20:59:31] [PASSED] drm_test_cmdline_res_bpp_refresh_interlaced_margins_force_on [20:59:31] [PASSED] drm_test_cmdline_res_margins_force_on [20:59:31] [PASSED] drm_test_cmdline_res_vesa_margins [20:59:31] [PASSED] drm_test_cmdline_name [20:59:31] [PASSED] drm_test_cmdline_name_bpp [20:59:31] [PASSED] drm_test_cmdline_name_option [20:59:31] [PASSED] drm_test_cmdline_name_bpp_option [20:59:31] [PASSED] drm_test_cmdline_rotate_0 [20:59:31] [PASSED] drm_test_cmdline_rotate_90 [20:59:31] [PASSED] drm_test_cmdline_rotate_180 [20:59:31] [PASSED] drm_test_cmdline_rotate_270 [20:59:31] [PASSED] drm_test_cmdline_hmirror [20:59:31] [PASSED] drm_test_cmdline_vmirror [20:59:31] [PASSED] drm_test_cmdline_margin_options [20:59:31] [PASSED] drm_test_cmdline_multiple_options [20:59:31] [PASSED] drm_test_cmdline_bpp_extra_and_option [20:59:31] [PASSED] drm_test_cmdline_extra_and_option [20:59:31] [PASSED] drm_test_cmdline_freestanding_options [20:59:31] [PASSED] drm_test_cmdline_freestanding_force_e_and_options [20:59:31] [PASSED] drm_test_cmdline_panel_orientation [20:59:31] ================ drm_test_cmdline_invalid ================= [20:59:31] [PASSED] margin_only [20:59:31] [PASSED] interlace_only [20:59:31] [PASSED] res_missing_x [20:59:31] [PASSED] res_missing_y [20:59:31] [PASSED] res_bad_y [20:59:31] [PASSED] res_missing_y_bpp [20:59:31] [PASSED] res_bad_bpp [20:59:31] [PASSED] res_bad_refresh [20:59:31] [PASSED] res_bpp_refresh_force_on_off [20:59:31] [PASSED] res_invalid_mode [20:59:31] [PASSED] res_bpp_wrong_place_mode [20:59:31] [PASSED] name_bpp_refresh [20:59:31] [PASSED] name_refresh [20:59:31] [PASSED] name_refresh_wrong_mode [20:59:31] [PASSED] name_refresh_invalid_mode [20:59:31] [PASSED] rotate_multiple [20:59:31] [PASSED] rotate_invalid_val [20:59:31] [PASSED] rotate_truncated [20:59:31] [PASSED] invalid_option [20:59:31] [PASSED] invalid_tv_option [20:59:31] [PASSED] truncated_tv_option [20:59:31] ============ [PASSED] drm_test_cmdline_invalid ============= [20:59:31] =============== drm_test_cmdline_tv_options =============== [20:59:31] [PASSED] NTSC [20:59:31] [PASSED] NTSC_443 [20:59:31] [PASSED] NTSC_J [20:59:31] [PASSED] PAL [20:59:31] [PASSED] PAL_M [20:59:31] [PASSED] PAL_N [20:59:31] [PASSED] SECAM [20:59:31] [PASSED] MONO_525 [20:59:31] [PASSED] MONO_625 [20:59:31] =========== [PASSED] drm_test_cmdline_tv_options =========== [20:59:31] =============== [PASSED] drm_cmdline_parser ================ [20:59:31] ========== drmm_connector_hdmi_init (19 subtests) ========== [20:59:31] [PASSED] drm_test_connector_hdmi_init_valid [20:59:31] [PASSED] drm_test_connector_hdmi_init_bpc_8 [20:59:31] [PASSED] drm_test_connector_hdmi_init_bpc_10 [20:59:31] [PASSED] drm_test_connector_hdmi_init_bpc_12 [20:59:31] [PASSED] drm_test_connector_hdmi_init_bpc_invalid [20:59:31] [PASSED] drm_test_connector_hdmi_init_bpc_null [20:59:31] [PASSED] drm_test_connector_hdmi_init_formats_empty [20:59:31] [PASSED] drm_test_connector_hdmi_init_formats_no_rgb [20:59:31] [PASSED] drm_test_connector_hdmi_init_null_ddc [20:59:31] [PASSED] drm_test_connector_hdmi_init_null_product [20:59:31] [PASSED] drm_test_connector_hdmi_init_null_vendor [20:59:31] [PASSED] drm_test_connector_hdmi_init_product_length_exact [20:59:31] [PASSED] drm_test_connector_hdmi_init_product_length_too_long [20:59:31] [PASSED] drm_test_connector_hdmi_init_product_valid [20:59:31] [PASSED] drm_test_connector_hdmi_init_vendor_length_exact [20:59:31] [PASSED] drm_test_connector_hdmi_init_vendor_length_too_long [20:59:31] [PASSED] drm_test_connector_hdmi_init_vendor_valid [20:59:31] ========= drm_test_connector_hdmi_init_type_valid ========= [20:59:31] [PASSED] HDMI-A [20:59:31] [PASSED] HDMI-B [20:59:31] ===== [PASSED] drm_test_connector_hdmi_init_type_valid ===== [20:59:31] ======== drm_test_connector_hdmi_init_type_invalid ======== [20:59:31] [PASSED] Unknown [20:59:31] [PASSED] VGA [20:59:31] [PASSED] DVI-I [20:59:31] [PASSED] DVI-D [20:59:31] [PASSED] DVI-A [20:59:31] [PASSED] Composite [20:59:31] [PASSED] SVIDEO [20:59:31] [PASSED] LVDS [20:59:31] [PASSED] Component [20:59:31] [PASSED] DIN [20:59:31] [PASSED] DP [20:59:31] [PASSED] TV [20:59:31] [PASSED] eDP [20:59:31] [PASSED] Virtual [20:59:31] [PASSED] DSI [20:59:31] [PASSED] DPI [20:59:31] [PASSED] Writeback [20:59:31] [PASSED] SPI [20:59:31] [PASSED] USB [20:59:31] ==== [PASSED] drm_test_connector_hdmi_init_type_invalid ==== [20:59:31] ============ [PASSED] drmm_connector_hdmi_init ============= [20:59:31] ============= drmm_connector_init (3 subtests) ============= [20:59:31] [PASSED] drm_test_drmm_connector_init [20:59:31] [PASSED] drm_test_drmm_connector_init_null_ddc [20:59:31] ========= drm_test_drmm_connector_init_type_valid ========= [20:59:31] [PASSED] Unknown [20:59:31] [PASSED] VGA [20:59:31] [PASSED] DVI-I [20:59:31] [PASSED] DVI-D [20:59:31] [PASSED] DVI-A [20:59:31] [PASSED] Composite [20:59:31] [PASSED] SVIDEO [20:59:31] [PASSED] LVDS [20:59:31] [PASSED] Component [20:59:31] [PASSED] DIN [20:59:31] [PASSED] DP [20:59:31] [PASSED] HDMI-A [20:59:31] [PASSED] HDMI-B [20:59:31] [PASSED] TV [20:59:31] [PASSED] eDP [20:59:31] [PASSED] Virtual [20:59:31] [PASSED] DSI [20:59:31] [PASSED] DPI [20:59:31] [PASSED] Writeback [20:59:31] [PASSED] SPI [20:59:31] [PASSED] USB [20:59:31] ===== [PASSED] drm_test_drmm_connector_init_type_valid ===== [20:59:31] =============== [PASSED] drmm_connector_init =============== [20:59:31] ========= drm_connector_dynamic_init (6 subtests) ========== [20:59:31] [PASSED] drm_test_drm_connector_dynamic_init [20:59:31] [PASSED] drm_test_drm_connector_dynamic_init_null_ddc [20:59:31] [PASSED] drm_test_drm_connector_dynamic_init_not_added [20:59:31] [PASSED] drm_test_drm_connector_dynamic_init_properties [20:59:31] ===== drm_test_drm_connector_dynamic_init_type_valid ====== [20:59:31] [PASSED] Unknown [20:59:31] [PASSED] VGA [20:59:31] [PASSED] DVI-I [20:59:31] [PASSED] DVI-D [20:59:31] [PASSED] DVI-A [20:59:31] [PASSED] Composite [20:59:31] [PASSED] SVIDEO [20:59:31] [PASSED] LVDS [20:59:31] [PASSED] Component [20:59:31] [PASSED] DIN [20:59:31] [PASSED] DP [20:59:31] [PASSED] HDMI-A [20:59:31] [PASSED] HDMI-B [20:59:31] [PASSED] TV [20:59:31] [PASSED] eDP [20:59:31] [PASSED] Virtual [20:59:31] [PASSED] DSI [20:59:31] [PASSED] DPI [20:59:31] [PASSED] Writeback [20:59:31] [PASSED] SPI [20:59:31] [PASSED] USB [20:59:31] = [PASSED] drm_test_drm_connector_dynamic_init_type_valid == [20:59:31] ======== drm_test_drm_connector_dynamic_init_name ========= [20:59:31] [PASSED] Unknown [20:59:31] [PASSED] VGA [20:59:31] [PASSED] DVI-I [20:59:31] [PASSED] DVI-D [20:59:31] [PASSED] DVI-A [20:59:31] [PASSED] Composite [20:59:31] [PASSED] SVIDEO [20:59:31] [PASSED] LVDS [20:59:31] [PASSED] Component [20:59:31] [PASSED] DIN [20:59:31] [PASSED] DP [20:59:31] [PASSED] HDMI-A [20:59:31] [PASSED] HDMI-B [20:59:31] [PASSED] TV [20:59:31] [PASSED] eDP [20:59:31] [PASSED] Virtual [20:59:31] [PASSED] DSI [20:59:31] [PASSED] DPI [20:59:31] [PASSED] Writeback [20:59:31] [PASSED] SPI [20:59:31] [PASSED] USB [20:59:31] ==== [PASSED] drm_test_drm_connector_dynamic_init_name ===== [20:59:31] =========== [PASSED] drm_connector_dynamic_init ============ [20:59:31] ==== drm_connector_dynamic_register_early (4 subtests) ===== [20:59:31] [PASSED] drm_test_drm_connector_dynamic_register_early_on_list [20:59:31] [PASSED] drm_test_drm_connector_dynamic_register_early_defer [20:59:31] [PASSED] drm_test_drm_connector_dynamic_register_early_no_init [20:59:31] [PASSED] drm_test_drm_connector_dynamic_register_early_no_mode_object [20:59:31] ====== [PASSED] drm_connector_dynamic_register_early ======= [20:59:31] ======= drm_connector_dynamic_register (7 subtests) ======== [20:59:31] [PASSED] drm_test_drm_connector_dynamic_register_on_list [20:59:31] [PASSED] drm_test_drm_connector_dynamic_register_no_defer [20:59:31] [PASSED] drm_test_drm_connector_dynamic_register_no_init [20:59:31] [PASSED] drm_test_drm_connector_dynamic_register_mode_object [20:59:31] [PASSED] drm_test_drm_connector_dynamic_register_sysfs [20:59:31] [PASSED] drm_test_drm_connector_dynamic_register_sysfs_name [20:59:31] [PASSED] drm_test_drm_connector_dynamic_register_debugfs [20:59:31] ========= [PASSED] drm_connector_dynamic_register ========== [20:59:31] = drm_connector_attach_broadcast_rgb_property (2 subtests) = [20:59:31] [PASSED] drm_test_drm_connector_attach_broadcast_rgb_property [20:59:31] [PASSED] drm_test_drm_connector_attach_broadcast_rgb_property_hdmi_connector [20:59:31] === [PASSED] drm_connector_attach_broadcast_rgb_property === [20:59:31] ========== drm_get_tv_mode_from_name (2 subtests) ========== [20:59:31] ========== drm_test_get_tv_mode_from_name_valid =========== [20:59:31] [PASSED] NTSC [20:59:31] [PASSED] NTSC-443 [20:59:31] [PASSED] NTSC-J [20:59:31] [PASSED] PAL [20:59:31] [PASSED] PAL-M [20:59:31] [PASSED] PAL-N [20:59:31] [PASSED] SECAM [20:59:31] [PASSED] Mono [20:59:31] ====== [PASSED] drm_test_get_tv_mode_from_name_valid ======= [20:59:31] [PASSED] drm_test_get_tv_mode_from_name_truncated [20:59:31] ============ [PASSED] drm_get_tv_mode_from_name ============ [20:59:31] = drm_test_connector_hdmi_compute_mode_clock (12 subtests) = [20:59:31] [PASSED] drm_test_drm_hdmi_compute_mode_clock_rgb [20:59:31] [PASSED] drm_test_drm_hdmi_compute_mode_clock_rgb_10bpc [20:59:31] [PASSED] drm_test_drm_hdmi_compute_mode_clock_rgb_10bpc_vic_1 [20:59:31] [PASSED] drm_test_drm_hdmi_compute_mode_clock_rgb_12bpc [20:59:31] [PASSED] drm_test_drm_hdmi_compute_mode_clock_rgb_12bpc_vic_1 [20:59:31] [PASSED] drm_test_drm_hdmi_compute_mode_clock_rgb_double [20:59:31] = drm_test_connector_hdmi_compute_mode_clock_yuv420_valid = [20:59:31] [PASSED] VIC 96 [20:59:31] [PASSED] VIC 97 [20:59:31] [PASSED] VIC 101 [20:59:31] [PASSED] VIC 102 [20:59:31] [PASSED] VIC 106 [20:59:31] [PASSED] VIC 107 [20:59:31] === [PASSED] drm_test_connector_hdmi_compute_mode_clock_yuv420_valid === [20:59:31] [PASSED] drm_test_connector_hdmi_compute_mode_clock_yuv420_10_bpc [20:59:31] [PASSED] drm_test_connector_hdmi_compute_mode_clock_yuv420_12_bpc [20:59:31] [PASSED] drm_test_connector_hdmi_compute_mode_clock_yuv422_8_bpc [20:59:31] [PASSED] drm_test_connector_hdmi_compute_mode_clock_yuv422_10_bpc [20:59:31] [PASSED] drm_test_connector_hdmi_compute_mode_clock_yuv422_12_bpc [20:59:31] === [PASSED] drm_test_connector_hdmi_compute_mode_clock ==== [20:59:31] == drm_hdmi_connector_get_broadcast_rgb_name (2 subtests) == [20:59:31] === drm_test_drm_hdmi_connector_get_broadcast_rgb_name ==== [20:59:31] [PASSED] Automatic [20:59:31] [PASSED] Full [20:59:31] [PASSED] Limited 16:235 [20:59:31] === [PASSED] drm_test_drm_hdmi_connector_get_broadcast_rgb_name === [20:59:31] [PASSED] drm_test_drm_hdmi_connector_get_broadcast_rgb_name_invalid [20:59:31] ==== [PASSED] drm_hdmi_connector_get_broadcast_rgb_name ==== [20:59:31] == drm_hdmi_connector_get_output_format_name (2 subtests) == [20:59:31] === drm_test_drm_hdmi_connector_get_output_format_name ==== [20:59:31] [PASSED] RGB [20:59:31] [PASSED] YUV 4:2:0 [20:59:31] [PASSED] YUV 4:2:2 [20:59:31] [PASSED] YUV 4:4:4 [20:59:31] === [PASSED] drm_test_drm_hdmi_connector_get_output_format_name === [20:59:31] [PASSED] drm_test_drm_hdmi_connector_get_output_format_name_invalid [20:59:31] ==== [PASSED] drm_hdmi_connector_get_output_format_name ==== [20:59:31] ============= drm_damage_helper (21 subtests) ============== [20:59:31] [PASSED] drm_test_damage_iter_no_damage [20:59:31] [PASSED] drm_test_damage_iter_no_damage_fractional_src [20:59:31] [PASSED] drm_test_damage_iter_no_damage_src_moved [20:59:31] [PASSED] drm_test_damage_iter_no_damage_fractional_src_moved [20:59:31] [PASSED] drm_test_damage_iter_no_damage_not_visible [20:59:31] [PASSED] drm_test_damage_iter_no_damage_no_crtc [20:59:31] [PASSED] drm_test_damage_iter_no_damage_no_fb [20:59:31] [PASSED] drm_test_damage_iter_simple_damage [20:59:31] [PASSED] drm_test_damage_iter_single_damage [20:59:31] [PASSED] drm_test_damage_iter_single_damage_intersect_src [20:59:31] [PASSED] drm_test_damage_iter_single_damage_outside_src [20:59:31] [PASSED] drm_test_damage_iter_single_damage_fractional_src [20:59:31] [PASSED] drm_test_damage_iter_single_damage_intersect_fractional_src [20:59:31] [PASSED] drm_test_damage_iter_single_damage_outside_fractional_src [20:59:31] [PASSED] drm_test_damage_iter_single_damage_src_moved [20:59:31] [PASSED] drm_test_damage_iter_single_damage_fractional_src_moved [20:59:31] [PASSED] drm_test_damage_iter_damage [20:59:31] [PASSED] drm_test_damage_iter_damage_one_intersect [20:59:31] [PASSED] drm_test_damage_iter_damage_one_outside [20:59:31] [PASSED] drm_test_damage_iter_damage_src_moved [20:59:31] [PASSED] drm_test_damage_iter_damage_not_visible [20:59:31] ================ [PASSED] drm_damage_helper ================ [20:59:31] ============== drm_dp_mst_helper (3 subtests) ============== [20:59:31] ============== drm_test_dp_mst_calc_pbn_mode ============== [20:59:31] [PASSED] Clock 154000 BPP 30 DSC disabled [20:59:31] [PASSED] Clock 234000 BPP 30 DSC disabled [20:59:31] [PASSED] Clock 297000 BPP 24 DSC disabled [20:59:31] [PASSED] Clock 332880 BPP 24 DSC enabled [20:59:31] [PASSED] Clock 324540 BPP 24 DSC enabled [20:59:31] ========== [PASSED] drm_test_dp_mst_calc_pbn_mode ========== [20:59:31] ============== drm_test_dp_mst_calc_pbn_div =============== [20:59:31] [PASSED] Link rate 2000000 lane count 4 [20:59:31] [PASSED] Link rate 2000000 lane count 2 [20:59:31] [PASSED] Link rate 2000000 lane count 1 [20:59:31] [PASSED] Link rate 1350000 lane count 4 [20:59:31] [PASSED] Link rate 1350000 lane count 2 [20:59:31] [PASSED] Link rate 1350000 lane count 1 [20:59:31] [PASSED] Link rate 1000000 lane count 4 [20:59:31] [PASSED] Link rate 1000000 lane count 2 [20:59:31] [PASSED] Link rate 1000000 lane count 1 [20:59:31] [PASSED] Link rate 810000 lane count 4 [20:59:31] [PASSED] Link rate 810000 lane count 2 [20:59:31] [PASSED] Link rate 810000 lane count 1 [20:59:31] [PASSED] Link rate 540000 lane count 4 [20:59:31] [PASSED] Link rate 540000 lane count 2 [20:59:31] [PASSED] Link rate 540000 lane count 1 [20:59:31] [PASSED] Link rate 270000 lane count 4 [20:59:31] [PASSED] Link rate 270000 lane count 2 [20:59:31] [PASSED] Link rate 270000 lane count 1 [20:59:31] [PASSED] Link rate 162000 lane count 4 [20:59:31] [PASSED] Link rate 162000 lane count 2 [20:59:31] [PASSED] Link rate 162000 lane count 1 [20:59:31] ========== [PASSED] drm_test_dp_mst_calc_pbn_div =========== [20:59:31] ========= drm_test_dp_mst_sideband_msg_req_decode ========= [20:59:31] [PASSED] DP_ENUM_PATH_RESOURCES with port number [20:59:31] [PASSED] DP_POWER_UP_PHY with port number [20:59:31] [PASSED] DP_POWER_DOWN_PHY with port number [20:59:31] [PASSED] DP_ALLOCATE_PAYLOAD with SDP stream sinks [20:59:31] [PASSED] DP_ALLOCATE_PAYLOAD with port number [20:59:31] [PASSED] DP_ALLOCATE_PAYLOAD with VCPI [20:59:31] [PASSED] DP_ALLOCATE_PAYLOAD with PBN [20:59:31] [PASSED] DP_QUERY_PAYLOAD with port number [20:59:31] [PASSED] DP_QUERY_PAYLOAD with VCPI [20:59:31] [PASSED] DP_REMOTE_DPCD_READ with port number [20:59:31] [PASSED] DP_REMOTE_DPCD_READ with DPCD address [20:59:31] [PASSED] DP_REMOTE_DPCD_READ with max number of bytes [20:59:31] [PASSED] DP_REMOTE_DPCD_WRITE with port number [20:59:31] [PASSED] DP_REMOTE_DPCD_WRITE with DPCD address [20:59:31] [PASSED] DP_REMOTE_DPCD_WRITE with data array [20:59:31] [PASSED] DP_REMOTE_I2C_READ with port number [20:59:31] [PASSED] DP_REMOTE_I2C_READ with I2C device ID [20:59:31] [PASSED] DP_REMOTE_I2C_READ with transactions array [20:59:31] [PASSED] DP_REMOTE_I2C_WRITE with port number [20:59:31] [PASSED] DP_REMOTE_I2C_WRITE with I2C device ID [20:59:31] [PASSED] DP_REMOTE_I2C_WRITE with data array [20:59:31] [PASSED] DP_QUERY_STREAM_ENC_STATUS with stream ID [20:59:31] [PASSED] DP_QUERY_STREAM_ENC_STATUS with client ID [20:59:31] [PASSED] DP_QUERY_STREAM_ENC_STATUS with stream event [20:59:31] [PASSED] DP_QUERY_STREAM_ENC_STATUS with valid stream event [20:59:31] [PASSED] DP_QUERY_STREAM_ENC_STATUS with stream behavior [20:59:31] [PASSED] DP_QUERY_STREAM_ENC_STATUS with a valid stream behavior [20:59:31] ===== [PASSED] drm_test_dp_mst_sideband_msg_req_decode ===== [20:59:31] ================ [PASSED] drm_dp_mst_helper ================ [20:59:31] ================== drm_exec (7 subtests) =================== [20:59:31] [PASSED] sanitycheck [20:59:31] [PASSED] test_lock [20:59:31] [PASSED] test_lock_unlock [20:59:31] [PASSED] test_duplicates [20:59:31] [PASSED] test_prepare [20:59:31] [PASSED] test_prepare_array [20:59:31] [PASSED] test_multiple_loops [20:59:31] ==================== [PASSED] drm_exec ===================== [20:59:31] =========== drm_format_helper_test (17 subtests) =========== [20:59:31] ============== drm_test_fb_xrgb8888_to_gray8 ============== [20:59:31] [PASSED] single_pixel_source_buffer [20:59:31] [PASSED] single_pixel_clip_rectangle [20:59:31] [PASSED] well_known_colors [20:59:31] [PASSED] destination_pitch [20:59:31] ========== [PASSED] drm_test_fb_xrgb8888_to_gray8 ========== [20:59:31] ============= drm_test_fb_xrgb8888_to_rgb332 ============== [20:59:31] [PASSED] single_pixel_source_buffer [20:59:31] [PASSED] single_pixel_clip_rectangle [20:59:31] [PASSED] well_known_colors [20:59:31] [PASSED] destination_pitch [20:59:31] ========= [PASSED] drm_test_fb_xrgb8888_to_rgb332 ========== [20:59:31] ============= drm_test_fb_xrgb8888_to_rgb565 ============== [20:59:31] [PASSED] single_pixel_source_buffer [20:59:31] [PASSED] single_pixel_clip_rectangle [20:59:31] [PASSED] well_known_colors [20:59:31] [PASSED] destination_pitch [20:59:31] ========= [PASSED] drm_test_fb_xrgb8888_to_rgb565 ========== [20:59:31] ============ drm_test_fb_xrgb8888_to_xrgb1555 ============= [20:59:31] [PASSED] single_pixel_source_buffer [20:59:31] [PASSED] single_pixel_clip_rectangle [20:59:31] [PASSED] well_known_colors [20:59:31] [PASSED] destination_pitch [20:59:31] ======== [PASSED] drm_test_fb_xrgb8888_to_xrgb1555 ========= [20:59:31] ============ drm_test_fb_xrgb8888_to_argb1555 ============= [20:59:31] [PASSED] single_pixel_source_buffer [20:59:31] [PASSED] single_pixel_clip_rectangle [20:59:31] [PASSED] well_known_colors [20:59:31] [PASSED] destination_pitch [20:59:31] ======== [PASSED] drm_test_fb_xrgb8888_to_argb1555 ========= [20:59:31] ============ drm_test_fb_xrgb8888_to_rgba5551 ============= [20:59:31] [PASSED] single_pixel_source_buffer [20:59:31] [PASSED] single_pixel_clip_rectangle [20:59:31] [PASSED] well_known_colors [20:59:31] [PASSED] destination_pitch [20:59:31] ======== [PASSED] drm_test_fb_xrgb8888_to_rgba5551 ========= [20:59:31] ============= drm_test_fb_xrgb8888_to_rgb888 ============== [20:59:31] [PASSED] single_pixel_source_buffer [20:59:31] [PASSED] single_pixel_clip_rectangle [20:59:31] [PASSED] well_known_colors [20:59:31] [PASSED] destination_pitch [20:59:31] ========= [PASSED] drm_test_fb_xrgb8888_to_rgb888 ========== [20:59:31] ============ drm_test_fb_xrgb8888_to_argb8888 ============= [20:59:31] [PASSED] single_pixel_source_buffer [20:59:31] [PASSED] single_pixel_clip_rectangle [20:59:31] [PASSED] well_known_colors [20:59:31] [PASSED] destination_pitch [20:59:31] ======== [PASSED] drm_test_fb_xrgb8888_to_argb8888 ========= [20:59:31] =========== drm_test_fb_xrgb8888_to_xrgb2101010 =========== [20:59:31] [PASSED] single_pixel_source_buffer [20:59:31] [PASSED] single_pixel_clip_rectangle [20:59:31] [PASSED] well_known_colors [20:59:31] [PASSED] destination_pitch [20:59:31] ======= [PASSED] drm_test_fb_xrgb8888_to_xrgb2101010 ======= [20:59:31] =========== drm_test_fb_xrgb8888_to_argb2101010 =========== [20:59:31] [PASSED] single_pixel_source_buffer [20:59:31] [PASSED] single_pixel_clip_rectangle [20:59:31] [PASSED] well_known_colors [20:59:31] [PASSED] destination_pitch [20:59:31] ======= [PASSED] drm_test_fb_xrgb8888_to_argb2101010 ======= [20:59:31] ============== drm_test_fb_xrgb8888_to_mono =============== [20:59:31] [PASSED] single_pixel_source_buffer [20:59:31] [PASSED] single_pixel_clip_rectangle [20:59:31] [PASSED] well_known_colors [20:59:31] [PASSED] destination_pitch [20:59:31] ========== [PASSED] drm_test_fb_xrgb8888_to_mono =========== [20:59:31] ==================== drm_test_fb_swab ===================== [20:59:31] [PASSED] single_pixel_source_buffer [20:59:31] [PASSED] single_pixel_clip_rectangle [20:59:31] [PASSED] well_known_colors [20:59:31] [PASSED] destination_pitch [20:59:31] ================ [PASSED] drm_test_fb_swab ================= [20:59:31] ============ drm_test_fb_xrgb8888_to_xbgr8888 ============= [20:59:31] [PASSED] single_pixel_source_buffer [20:59:31] [PASSED] single_pixel_clip_rectangle [20:59:31] [PASSED] well_known_colors [20:59:31] [PASSED] destination_pitch [20:59:31] ======== [PASSED] drm_test_fb_xrgb8888_to_xbgr8888 ========= [20:59:31] ============ drm_test_fb_xrgb8888_to_abgr8888 ============= [20:59:31] [PASSED] single_pixel_source_buffer [20:59:31] [PASSED] single_pixel_clip_rectangle [20:59:31] [PASSED] well_known_colors [20:59:31] [PASSED] destination_pitch [20:59:31] ======== [PASSED] drm_test_fb_xrgb8888_to_abgr8888 ========= [20:59:31] ================= drm_test_fb_clip_offset ================= [20:59:31] [PASSED] pass through [20:59:31] [PASSED] horizontal offset [20:59:31] [PASSED] vertical offset [20:59:31] [PASSED] horizontal and vertical offset [20:59:31] [PASSED] horizontal offset (custom pitch) [20:59:31] [PASSED] vertical offset (custom pitch) [20:59:31] [PASSED] horizontal and vertical offset (custom pitch) [20:59:31] ============= [PASSED] drm_test_fb_clip_offset ============= [20:59:31] ============== drm_test_fb_build_fourcc_list ============== [20:59:31] [PASSED] no native formats [20:59:31] [PASSED] XRGB8888 as native format [20:59:31] [PASSED] remove duplicates [20:59:31] [PASSED] convert alpha formats [20:59:31] [PASSED] random formats [20:59:31] ========== [PASSED] drm_test_fb_build_fourcc_list ========== [20:59:31] =================== drm_test_fb_memcpy ==================== [20:59:31] [PASSED] single_pixel_source_buffer: XR24 little-endian (0x34325258) [20:59:31] [PASSED] single_pixel_source_buffer: XRA8 little-endian (0x38415258) [20:59:31] [PASSED] single_pixel_source_buffer: YU24 little-endian (0x34325559) [20:59:31] [PASSED] single_pixel_clip_rectangle: XB24 little-endian (0x34324258) [20:59:31] [PASSED] single_pixel_clip_rectangle: XRA8 little-endian (0x38415258) [20:59:31] [PASSED] single_pixel_clip_rectangle: YU24 little-endian (0x34325559) [20:59:31] [PASSED] well_known_colors: XB24 little-endian (0x34324258) [20:59:31] [PASSED] well_known_colors: XRA8 little-endian (0x38415258) [20:59:31] [PASSED] well_known_colors: YU24 little-endian (0x34325559) [20:59:31] [PASSED] destination_pitch: XB24 little-endian (0x34324258) [20:59:31] [PASSED] destination_pitch: XRA8 little-endian (0x38415258) [20:59:31] [PASSED] destination_pitch: YU24 little-endian (0x34325559) [20:59:31] =============== [PASSED] drm_test_fb_memcpy ================ [20:59:31] ============= [PASSED] drm_format_helper_test ============== [20:59:31] ================= drm_format (18 subtests) ================= [20:59:31] [PASSED] drm_test_format_block_width_invalid [20:59:31] [PASSED] drm_test_format_block_width_one_plane [20:59:31] [PASSED] drm_test_format_block_width_two_plane [20:59:31] [PASSED] drm_test_format_block_width_three_plane [20:59:31] [PASSED] drm_test_format_block_width_tiled [20:59:31] [PASSED] drm_test_format_block_height_invalid [20:59:31] [PASSED] drm_test_format_block_height_one_plane [20:59:31] [PASSED] drm_test_format_block_height_two_plane [20:59:31] [PASSED] drm_test_format_block_height_three_plane [20:59:31] [PASSED] drm_test_format_block_height_tiled [20:59:31] [PASSED] drm_test_format_min_pitch_invalid [20:59:31] [PASSED] drm_test_format_min_pitch_one_plane_8bpp [20:59:31] [PASSED] drm_test_format_min_pitch_one_plane_16bpp [20:59:31] [PASSED] drm_test_format_min_pitch_one_plane_24bpp [20:59:31] [PASSED] drm_test_format_min_pitch_one_plane_32bpp [20:59:31] [PASSED] drm_test_format_min_pitch_two_plane [20:59:31] [PASSED] drm_test_format_min_pitch_three_plane_8bpp [20:59:31] [PASSED] drm_test_format_min_pitch_tiled [20:59:31] =================== [PASSED] drm_format ==================== [20:59:31] ============== drm_framebuffer (10 subtests) =============== [20:59:31] ========== drm_test_framebuffer_check_src_coords ========== [20:59:31] [PASSED] Success: source fits into fb [20:59:31] [PASSED] Fail: overflowing fb with x-axis coordinate [20:59:31] [PASSED] Fail: overflowing fb with y-axis coordinate [20:59:31] [PASSED] Fail: overflowing fb with source width [20:59:31] [PASSED] Fail: overflowing fb with source height [20:59:31] ====== [PASSED] drm_test_framebuffer_check_src_coords ====== [20:59:31] [PASSED] drm_test_framebuffer_cleanup [20:59:31] =============== drm_test_framebuffer_create =============== [20:59:31] [PASSED] ABGR8888 normal sizes [20:59:31] [PASSED] ABGR8888 max sizes [20:59:31] [PASSED] ABGR8888 pitch greater than min required [20:59:31] [PASSED] ABGR8888 pitch less than min required [20:59:31] [PASSED] ABGR8888 Invalid width [20:59:31] [PASSED] ABGR8888 Invalid buffer handle [20:59:31] [PASSED] No pixel format [20:59:31] [PASSED] ABGR8888 Width 0 [20:59:31] [PASSED] ABGR8888 Height 0 [20:59:31] [PASSED] ABGR8888 Out of bound height * pitch combination [20:59:31] [PASSED] ABGR8888 Large buffer offset [20:59:31] [PASSED] ABGR8888 Buffer offset for inexistent plane [20:59:31] [PASSED] ABGR8888 Invalid flag [20:59:31] [PASSED] ABGR8888 Set DRM_MODE_FB_MODIFIERS without modifiers [20:59:31] [PASSED] ABGR8888 Valid buffer modifier [20:59:31] [PASSED] ABGR8888 Invalid buffer modifier(DRM_FORMAT_MOD_SAMSUNG_64_32_TILE) [20:59:31] [PASSED] ABGR8888 Extra pitches without DRM_MODE_FB_MODIFIERS [20:59:31] [PASSED] ABGR8888 Extra pitches with DRM_MODE_FB_MODIFIERS [20:59:31] [PASSED] NV12 Normal sizes [20:59:31] [PASSED] NV12 Max sizes [20:59:31] [PASSED] NV12 Invalid pitch [20:59:31] [PASSED] NV12 Invalid modifier/missing DRM_MODE_FB_MODIFIERS flag [20:59:31] [PASSED] NV12 different modifier per-plane [20:59:31] [PASSED] NV12 with DRM_FORMAT_MOD_SAMSUNG_64_32_TILE [20:59:31] [PASSED] NV12 Valid modifiers without DRM_MODE_FB_MODIFIERS [20:59:31] [PASSED] NV12 Modifier for inexistent plane [20:59:31] [PASSED] NV12 Handle for inexistent plane [20:59:31] [PASSED] NV12 Handle for inexistent plane without DRM_MODE_FB_MODIFIERS [20:59:31] [PASSED] YVU420 DRM_MODE_FB_MODIFIERS set without modifier [20:59:31] [PASSED] YVU420 Normal sizes [20:59:31] [PASSED] YVU420 Max sizes [20:59:31] [PASSED] YVU420 Invalid pitch [20:59:31] [PASSED] YVU420 Different pitches [20:59:31] [PASSED] YVU420 Different buffer offsets/pitches [20:59:31] [PASSED] YVU420 Modifier set just for plane 0, without DRM_MODE_FB_MODIFIERS [20:59:31] [PASSED] YVU420 Modifier set just for planes 0, 1, without DRM_MODE_FB_MODIFIERS [20:59:31] [PASSED] YVU420 Modifier set just for plane 0, 1, with DRM_MODE_FB_MODIFIERS [20:59:31] [PASSED] YVU420 Valid modifier [20:59:31] [PASSED] YVU420 Different modifiers per plane [20:59:31] [PASSED] YVU420 Modifier for inexistent plane [20:59:31] [PASSED] YUV420_10BIT Invalid modifier(DRM_FORMAT_MOD_LINEAR) [20:59:31] [PASSED] X0L2 Normal sizes [20:59:31] [PASSED] X0L2 Max sizes [20:59:31] [PASSED] X0L2 Invalid pitch [20:59:31] [PASSED] X0L2 Pitch greater than minimum required [20:59:31] [PASSED] X0L2 Handle for inexistent plane [20:59:31] [PASSED] X0L2 Offset for inexistent plane, without DRM_MODE_FB_MODIFIERS set [20:59:31] [PASSED] X0L2 Modifier without DRM_MODE_FB_MODIFIERS set [20:59:31] [PASSED] X0L2 Valid modifier [20:59:31] [PASSED] X0L2 Modifier for inexistent plane [20:59:31] =========== [PASSED] drm_test_framebuffer_create =========== [20:59:31] [PASSED] drm_test_framebuffer_free [20:59:31] [PASSED] drm_test_framebuffer_init [20:59:31] [PASSED] drm_test_framebuffer_init_bad_format [20:59:31] [PASSED] drm_test_framebuffer_init_dev_mismatch [20:59:31] [PASSED] drm_test_framebuffer_lookup [20:59:31] [PASSED] drm_test_framebuffer_lookup_inexistent [20:59:31] [PASSED] drm_test_framebuffer_modifiers_not_supported [20:59:31] ================= [PASSED] drm_framebuffer ================= [20:59:31] ================ drm_gem_shmem (8 subtests) ================ [20:59:31] [PASSED] drm_gem_shmem_test_obj_create [20:59:31] [PASSED] drm_gem_shmem_test_obj_create_private [20:59:31] [PASSED] drm_gem_shmem_test_pin_pages [20:59:31] [PASSED] drm_gem_shmem_test_vmap [20:59:31] [PASSED] drm_gem_shmem_test_get_pages_sgt [20:59:31] [PASSED] drm_gem_shmem_test_get_sg_table [20:59:31] [PASSED] drm_gem_shmem_test_madvise [20:59:31] [PASSED] drm_gem_shmem_test_purge [20:59:31] ================== [PASSED] drm_gem_shmem ================== [20:59:31] === drm_atomic_helper_connector_hdmi_check (22 subtests) === [20:59:31] [PASSED] drm_test_check_broadcast_rgb_auto_cea_mode [20:59:31] [PASSED] drm_test_check_broadcast_rgb_auto_cea_mode_vic_1 stty: 'standard input': Inappropriate ioctl for device [20:59:31] [PASSED] drm_test_check_broadcast_rgb_full_cea_mode [20:59:31] [PASSED] drm_test_check_broadcast_rgb_full_cea_mode_vic_1 [20:59:31] [PASSED] drm_test_check_broadcast_rgb_limited_cea_mode [20:59:31] [PASSED] drm_test_check_broadcast_rgb_limited_cea_mode_vic_1 [20:59:31] [PASSED] drm_test_check_broadcast_rgb_crtc_mode_changed [20:59:31] [PASSED] drm_test_check_broadcast_rgb_crtc_mode_not_changed [20:59:31] [PASSED] drm_test_check_hdmi_funcs_reject_rate [20:59:31] [PASSED] drm_test_check_max_tmds_rate_bpc_fallback [20:59:31] [PASSED] drm_test_check_max_tmds_rate_format_fallback [20:59:31] [PASSED] drm_test_check_output_bpc_crtc_mode_changed [20:59:31] [PASSED] drm_test_check_output_bpc_crtc_mode_not_changed [20:59:31] [PASSED] drm_test_check_output_bpc_dvi [20:59:31] [PASSED] drm_test_check_output_bpc_format_vic_1 [20:59:31] [PASSED] drm_test_check_output_bpc_format_display_8bpc_only [20:59:31] [PASSED] drm_test_check_output_bpc_format_display_rgb_only [20:59:31] [PASSED] drm_test_check_output_bpc_format_driver_8bpc_only [20:59:31] [PASSED] drm_test_check_output_bpc_format_driver_rgb_only [20:59:31] [PASSED] drm_test_check_tmds_char_rate_rgb_8bpc [20:59:31] [PASSED] drm_test_check_tmds_char_rate_rgb_10bpc [20:59:31] [PASSED] drm_test_check_tmds_char_rate_rgb_12bpc [20:59:31] ===== [PASSED] drm_atomic_helper_connector_hdmi_check ====== [20:59:31] === drm_atomic_helper_connector_hdmi_reset (6 subtests) ==== [20:59:31] [PASSED] drm_test_check_broadcast_rgb_value [20:59:31] [PASSED] drm_test_check_bpc_8_value [20:59:31] [PASSED] drm_test_check_bpc_10_value [20:59:31] [PASSED] drm_test_check_bpc_12_value [20:59:31] [PASSED] drm_test_check_format_value [20:59:31] [PASSED] drm_test_check_tmds_char_value [20:59:31] ===== [PASSED] drm_atomic_helper_connector_hdmi_reset ====== [20:59:31] = drm_atomic_helper_connector_hdmi_mode_valid (4 subtests) = [20:59:31] [PASSED] drm_test_check_mode_valid [20:59:31] [PASSED] drm_test_check_mode_valid_reject [20:59:31] [PASSED] drm_test_check_mode_valid_reject_rate [20:59:31] [PASSED] drm_test_check_mode_valid_reject_max_clock [20:59:31] === [PASSED] drm_atomic_helper_connector_hdmi_mode_valid === [20:59:31] ================= drm_managed (2 subtests) ================= [20:59:31] [PASSED] drm_test_managed_release_action [20:59:31] [PASSED] drm_test_managed_run_action [20:59:31] =================== [PASSED] drm_managed =================== [20:59:31] =================== drm_mm (6 subtests) ==================== [20:59:31] [PASSED] drm_test_mm_init [20:59:31] [PASSED] drm_test_mm_debug [20:59:31] [PASSED] drm_test_mm_align32 [20:59:31] [PASSED] drm_test_mm_align64 [20:59:31] [PASSED] drm_test_mm_lowest [20:59:31] [PASSED] drm_test_mm_highest [20:59:31] ===================== [PASSED] drm_mm ====================== [20:59:31] ============= drm_modes_analog_tv (5 subtests) ============= [20:59:31] [PASSED] drm_test_modes_analog_tv_mono_576i [20:59:31] [PASSED] drm_test_modes_analog_tv_ntsc_480i [20:59:31] [PASSED] drm_test_modes_analog_tv_ntsc_480i_inlined [20:59:31] [PASSED] drm_test_modes_analog_tv_pal_576i [20:59:31] [PASSED] drm_test_modes_analog_tv_pal_576i_inlined [20:59:31] =============== [PASSED] drm_modes_analog_tv =============== [20:59:31] ============== drm_plane_helper (2 subtests) =============== [20:59:31] =============== drm_test_check_plane_state ================ [20:59:31] [PASSED] clipping_simple [20:59:31] [PASSED] clipping_rotate_reflect [20:59:31] [PASSED] positioning_simple [20:59:31] [PASSED] upscaling [20:59:31] [PASSED] downscaling [20:59:31] [PASSED] rounding1 [20:59:31] [PASSED] rounding2 [20:59:31] [PASSED] rounding3 [20:59:31] [PASSED] rounding4 [20:59:31] =========== [PASSED] drm_test_check_plane_state ============ [20:59:31] =========== drm_test_check_invalid_plane_state ============ [20:59:31] [PASSED] positioning_invalid [20:59:31] [PASSED] upscaling_invalid [20:59:31] [PASSED] downscaling_invalid [20:59:31] ======= [PASSED] drm_test_check_invalid_plane_state ======== [20:59:31] ================ [PASSED] drm_plane_helper ================= [20:59:31] ====== drm_connector_helper_tv_get_modes (1 subtest) ======= [20:59:31] ====== drm_test_connector_helper_tv_get_modes_check ======= [20:59:31] [PASSED] None [20:59:31] [PASSED] PAL [20:59:31] [PASSED] NTSC [20:59:31] [PASSED] Both, NTSC Default [20:59:31] [PASSED] Both, PAL Default [20:59:31] [PASSED] Both, NTSC Default, with PAL on command-line [20:59:31] [PASSED] Both, PAL Default, with NTSC on command-line [20:59:31] == [PASSED] drm_test_connector_helper_tv_get_modes_check === [20:59:31] ======== [PASSED] drm_connector_helper_tv_get_modes ======== [20:59:31] ================== drm_rect (9 subtests) =================== [20:59:31] [PASSED] drm_test_rect_clip_scaled_div_by_zero [20:59:31] [PASSED] drm_test_rect_clip_scaled_not_clipped [20:59:31] [PASSED] drm_test_rect_clip_scaled_clipped [20:59:31] [PASSED] drm_test_rect_clip_scaled_signed_vs_unsigned [20:59:31] ================= drm_test_rect_intersect ================= [20:59:31] [PASSED] top-left x bottom-right: 2x2+1+1 x 2x2+0+0 [20:59:31] [PASSED] top-right x bottom-left: 2x2+0+0 x 2x2+1-1 [20:59:31] [PASSED] bottom-left x top-right: 2x2+1-1 x 2x2+0+0 [20:59:31] [PASSED] bottom-right x top-left: 2x2+0+0 x 2x2+1+1 [20:59:31] [PASSED] right x left: 2x1+0+0 x 3x1+1+0 [20:59:31] [PASSED] left x right: 3x1+1+0 x 2x1+0+0 [20:59:31] [PASSED] up x bottom: 1x2+0+0 x 1x3+0-1 [20:59:31] [PASSED] bottom x up: 1x3+0-1 x 1x2+0+0 [20:59:31] [PASSED] touching corner: 1x1+0+0 x 2x2+1+1 [20:59:31] [PASSED] touching side: 1x1+0+0 x 1x1+1+0 [20:59:31] [PASSED] equal rects: 2x2+0+0 x 2x2+0+0 [20:59:31] [PASSED] inside another: 2x2+0+0 x 1x1+1+1 [20:59:31] [PASSED] far away: 1x1+0+0 x 1x1+3+6 [20:59:31] [PASSED] points intersecting: 0x0+5+10 x 0x0+5+10 [20:59:31] [PASSED] points not intersecting: 0x0+0+0 x 0x0+5+10 [20:59:31] ============= [PASSED] drm_test_rect_intersect ============= [20:59:31] ================ drm_test_rect_calc_hscale ================ [20:59:31] [PASSED] normal use [20:59:31] [PASSED] out of max range [20:59:31] [PASSED] out of min range [20:59:31] [PASSED] zero dst [20:59:31] [PASSED] negative src [20:59:31] [PASSED] negative dst [20:59:31] ============ [PASSED] drm_test_rect_calc_hscale ============ [20:59:31] ================ drm_test_rect_calc_vscale ================ [20:59:31] [PASSED] normal use [20:59:31] [PASSED] out of max range [20:59:31] [PASSED] out of min range [20:59:31] [PASSED] zero dst [20:59:31] [PASSED] negative src [20:59:31] [PASSED] negative dst [20:59:31] ============ [PASSED] drm_test_rect_calc_vscale ============ [20:59:31] ================== drm_test_rect_rotate =================== [20:59:31] [PASSED] reflect-x [20:59:31] [PASSED] reflect-y [20:59:31] [PASSED] rotate-0 [20:59:31] [PASSED] rotate-90 [20:59:31] [PASSED] rotate-180 [20:59:31] [PASSED] rotate-270 [20:59:31] ============== [PASSED] drm_test_rect_rotate =============== [20:59:31] ================ drm_test_rect_rotate_inv ================= [20:59:31] [PASSED] reflect-x [20:59:31] [PASSED] reflect-y [20:59:31] [PASSED] rotate-0 [20:59:31] [PASSED] rotate-90 [20:59:31] [PASSED] rotate-180 [20:59:31] [PASSED] rotate-270 [20:59:31] ============ [PASSED] drm_test_rect_rotate_inv ============= [20:59:31] ==================== [PASSED] drm_rect ===================== [20:59:31] ============================================================ [20:59:31] Testing complete. Ran 587 tests: passed: 587 [20:59:31] Elapsed time: 25.671s total, 2.119s configuring, 23.386s building, 0.118s running + /kernel/tools/testing/kunit/kunit.py run --kunitconfig /kernel/drivers/gpu/drm/ttm/tests/.kunitconfig [20:59:31] Configuring KUnit Kernel ... Regenerating .config ... Populating config with: $ make ARCH=um O=.kunit olddefconfig [20:59:33] Building KUnit Kernel ... Populating config with: $ make ARCH=um O=.kunit olddefconfig Building with: $ make all compile_commands.json ARCH=um O=.kunit --jobs=48 [20:59:41] Starting KUnit Kernel (1/1)... [20:59:41] ============================================================ Running tests with: $ .kunit/linux kunit.enable=1 mem=1G console=tty kunit_shutdown=halt [20:59:41] ================= ttm_device (5 subtests) ================== [20:59:41] [PASSED] ttm_device_init_basic [20:59:41] [PASSED] ttm_device_init_multiple [20:59:41] [PASSED] ttm_device_fini_basic [20:59:41] [PASSED] ttm_device_init_no_vma_man [20:59:41] ================== ttm_device_init_pools ================== [20:59:41] [PASSED] No DMA allocations, no DMA32 required [20:59:41] [PASSED] DMA allocations, DMA32 required [20:59:41] [PASSED] No DMA allocations, DMA32 required [20:59:41] [PASSED] DMA allocations, no DMA32 required [20:59:41] ============== [PASSED] ttm_device_init_pools ============== [20:59:41] =================== [PASSED] ttm_device ==================== [20:59:41] ================== ttm_pool (8 subtests) =================== [20:59:41] ================== ttm_pool_alloc_basic =================== [20:59:41] [PASSED] One page [20:59:41] [PASSED] More than one page [20:59:41] [PASSED] Above the allocation limit [20:59:41] [PASSED] One page, with coherent DMA mappings enabled [20:59:41] [PASSED] Above the allocation limit, with coherent DMA mappings enabled [20:59:41] ============== [PASSED] ttm_pool_alloc_basic =============== [20:59:41] ============== ttm_pool_alloc_basic_dma_addr ============== [20:59:41] [PASSED] One page [20:59:41] [PASSED] More than one page [20:59:41] [PASSED] Above the allocation limit [20:59:41] [PASSED] One page, with coherent DMA mappings enabled [20:59:41] [PASSED] Above the allocation limit, with coherent DMA mappings enabled [20:59:41] ========== [PASSED] ttm_pool_alloc_basic_dma_addr ========== [20:59:41] [PASSED] ttm_pool_alloc_order_caching_match [20:59:41] [PASSED] ttm_pool_alloc_caching_mismatch [20:59:41] [PASSED] ttm_pool_alloc_order_mismatch [20:59:41] [PASSED] ttm_pool_free_dma_alloc [20:59:41] [PASSED] ttm_pool_free_no_dma_alloc [20:59:41] [PASSED] ttm_pool_fini_basic [20:59:41] ==================== [PASSED] ttm_pool ===================== [20:59:41] ================ ttm_resource (8 subtests) ================= [20:59:41] ================= ttm_resource_init_basic ================= [20:59:41] [PASSED] Init resource in TTM_PL_SYSTEM [20:59:41] [PASSED] Init resource in TTM_PL_VRAM [20:59:41] [PASSED] Init resource in a private placement [20:59:41] [PASSED] Init resource in TTM_PL_SYSTEM, set placement flags [20:59:41] ============= [PASSED] ttm_resource_init_basic ============= [20:59:41] [PASSED] ttm_resource_init_pinned [20:59:41] [PASSED] ttm_resource_fini_basic [20:59:41] [PASSED] ttm_resource_manager_init_basic [20:59:41] [PASSED] ttm_resource_manager_usage_basic [20:59:41] [PASSED] ttm_resource_manager_set_used_basic [20:59:41] [PASSED] ttm_sys_man_alloc_basic [20:59:41] [PASSED] ttm_sys_man_free_basic [20:59:41] ================== [PASSED] ttm_resource =================== [20:59:41] =================== ttm_tt (15 subtests) =================== [20:59:41] ==================== ttm_tt_init_basic ==================== [20:59:41] [PASSED] Page-aligned size [20:59:41] [PASSED] Extra pages requested [20:59:41] ================ [PASSED] ttm_tt_init_basic ================ [20:59:41] [PASSED] ttm_tt_init_misaligned [20:59:41] [PASSED] ttm_tt_fini_basic [20:59:41] [PASSED] ttm_tt_fini_sg [20:59:41] [PASSED] ttm_tt_fini_shmem [20:59:41] [PASSED] ttm_tt_create_basic [20:59:41] [PASSED] ttm_tt_create_invalid_bo_type [20:59:41] [PASSED] ttm_tt_create_ttm_exists [20:59:41] [PASSED] ttm_tt_create_failed [20:59:41] [PASSED] ttm_tt_destroy_basic [20:59:41] [PASSED] ttm_tt_populate_null_ttm [20:59:41] [PASSED] ttm_tt_populate_populated_ttm [20:59:41] [PASSED] ttm_tt_unpopulate_basic [20:59:41] [PASSED] ttm_tt_unpopulate_empty_ttm [20:59:41] [PASSED] ttm_tt_swapin_basic [20:59:41] ===================== [PASSED] ttm_tt ====================== [20:59:41] =================== ttm_bo (14 subtests) =================== [20:59:41] =========== ttm_bo_reserve_optimistic_no_ticket =========== [20:59:41] [PASSED] Cannot be interrupted and sleeps [20:59:41] [PASSED] Cannot be interrupted, locks straight away [20:59:41] [PASSED] Can be interrupted, sleeps [20:59:41] ======= [PASSED] ttm_bo_reserve_optimistic_no_ticket ======= [20:59:41] [PASSED] ttm_bo_reserve_locked_no_sleep [20:59:41] [PASSED] ttm_bo_reserve_no_wait_ticket [20:59:41] [PASSED] ttm_bo_reserve_double_resv [20:59:41] [PASSED] ttm_bo_reserve_interrupted [20:59:41] [PASSED] ttm_bo_reserve_deadlock [20:59:41] [PASSED] ttm_bo_unreserve_basic [20:59:41] [PASSED] ttm_bo_unreserve_pinned [20:59:41] [PASSED] ttm_bo_unreserve_bulk [20:59:41] [PASSED] ttm_bo_put_basic [20:59:41] [PASSED] ttm_bo_put_shared_resv [20:59:41] [PASSED] ttm_bo_pin_basic [20:59:41] [PASSED] ttm_bo_pin_unpin_resource [20:59:41] [PASSED] ttm_bo_multiple_pin_one_unpin [20:59:41] ===================== [PASSED] ttm_bo ====================== [20:59:41] ============== ttm_bo_validate (22 subtests) =============== [20:59:41] ============== ttm_bo_init_reserved_sys_man =============== [20:59:41] [PASSED] Buffer object for userspace [20:59:41] [PASSED] Kernel buffer object [20:59:41] [PASSED] Shared buffer object [20:59:41] ========== [PASSED] ttm_bo_init_reserved_sys_man =========== [20:59:41] ============== ttm_bo_init_reserved_mock_man ============== [20:59:41] [PASSED] Buffer object for userspace [20:59:41] [PASSED] Kernel buffer object [20:59:41] [PASSED] Shared buffer object [20:59:41] ========== [PASSED] ttm_bo_init_reserved_mock_man ========== [20:59:41] [PASSED] ttm_bo_init_reserved_resv [20:59:41] ================== ttm_bo_validate_basic ================== [20:59:41] [PASSED] Buffer object for userspace [20:59:41] [PASSED] Kernel buffer object [20:59:41] [PASSED] Shared buffer object [20:59:41] ============== [PASSED] ttm_bo_validate_basic ============== [20:59:41] [PASSED] ttm_bo_validate_invalid_placement [20:59:41] ============= ttm_bo_validate_same_placement ============== [20:59:41] [PASSED] System manager [20:59:41] [PASSED] VRAM manager [20:59:41] ========= [PASSED] ttm_bo_validate_same_placement ========== [20:59:41] [PASSED] ttm_bo_validate_failed_alloc [20:59:41] [PASSED] ttm_bo_validate_pinned [20:59:41] [PASSED] ttm_bo_validate_busy_placement [20:59:41] ================ ttm_bo_validate_multihop ================= [20:59:41] [PASSED] Buffer object for userspace [20:59:41] [PASSED] Kernel buffer object [20:59:41] [PASSED] Shared buffer object [20:59:41] ============ [PASSED] ttm_bo_validate_multihop ============= [20:59:41] ========== ttm_bo_validate_no_placement_signaled ========== [20:59:41] [PASSED] Buffer object in system domain, no page vector [20:59:41] [PASSED] Buffer object in system domain with an existing page vector [20:59:41] ====== [PASSED] ttm_bo_validate_no_placement_signaled ====== [20:59:41] ======== ttm_bo_validate_no_placement_not_signaled ======== [20:59:41] [PASSED] Buffer object for userspace [20:59:41] [PASSED] Kernel buffer object [20:59:41] [PASSED] Shared buffer object [20:59:41] ==== [PASSED] ttm_bo_validate_no_placement_not_signaled ==== [20:59:41] [PASSED] ttm_bo_validate_move_fence_signaled [20:59:41] ========= ttm_bo_validate_move_fence_not_signaled ========= [20:59:41] [PASSED] Waits for GPU [20:59:41] [PASSED] Tries to lock straight away [20:59:41] ===== [PASSED] ttm_bo_validate_move_fence_not_signaled ===== [20:59:41] [PASSED] ttm_bo_validate_swapout [20:59:41] [PASSED] ttm_bo_validate_happy_evict [20:59:41] [PASSED] ttm_bo_validate_all_pinned_evict [20:59:41] [PASSED] ttm_bo_validate_allowed_only_evict [20:59:41] [PASSED] ttm_bo_validate_deleted_evict [20:59:41] [PASSED] ttm_bo_validate_busy_domain_evict [20:59:41] [PASSED] ttm_bo_validate_evict_gutting [20:59:41] [PASSED] ttm_bo_validate_recrusive_evict stty: 'standard input': Inappropriate ioctl for device [20:59:41] ================= [PASSED] ttm_bo_validate ================= [20:59:41] ============================================================ [20:59:41] Testing complete. Ran 102 tests: passed: 102 [20:59:41] Elapsed time: 10.088s total, 1.639s configuring, 7.781s building, 0.581s running + cleanup ++ stat -c %u:%g /kernel + chown -R 1003:1003 /kernel ^ permalink raw reply [flat|nested] 22+ messages in thread
* Re: [PATCH v3 1/1] drm/xe/guc: Fix GuC log/ct output via debugfs 2025-01-07 20:22 [PATCH v3 1/1] drm/xe/guc: Fix GuC log/ct output via debugfs Julia Filipchuk ` (2 preceding siblings ...) 2025-01-07 20:59 ` ✓ CI.KUnit: " Patchwork @ 2025-01-07 21:10 ` Lucas De Marchi 2025-01-08 20:14 ` John Harrison 2025-01-07 21:25 ` ✓ CI.Build: success for series starting with [v3,1/1] " Patchwork ` (4 subsequent siblings) 8 siblings, 1 reply; 22+ messages in thread From: Lucas De Marchi @ 2025-01-07 21:10 UTC (permalink / raw) To: Julia Filipchuk; +Cc: intel-xe On Tue, Jan 07, 2025 at 12:22:52PM -0800, Julia Filipchuk wrote: >Change to disable asci85 GuC logging only when output to devcoredump >(was temporarily disabled for all code paths). > >v2: Ignore only for devcoredump case (not dmesg output). >v3: Rebase to resolve parent tag mismatch. > >Signed-off-by: Julia Filipchuk <julia.filipchuk@intel.com> >--- > drivers/gpu/drm/xe/xe_devcoredump.c | 8 +++++--- > include/drm/drm_print.h | 2 ++ > 2 files changed, 7 insertions(+), 3 deletions(-) > >diff --git a/drivers/gpu/drm/xe/xe_devcoredump.c b/drivers/gpu/drm/xe/xe_devcoredump.c >index 6980304c8903..8e5d1f9866a7 100644 >--- a/drivers/gpu/drm/xe/xe_devcoredump.c >+++ b/drivers/gpu/drm/xe/xe_devcoredump.c >@@ -424,10 +424,12 @@ void xe_print_blob_ascii85(struct drm_printer *p, const char *prefix, > * Splitting blobs across multiple lines is not compatible with the mesa > * debug decoder tool. Note that even dropping the explicit '\n' below > * doesn't help because the GuC log is so big some underlying implementation >- * still splits the lines at 512K characters. So just bail completely for >- * the moment. >+ * still splits the lines at 512K characters. did we investigate where this is done and how we can overcome it? I understand having to split it into multiple calls, but not something adding a \n. particularly for the functions dealing with seq_file and devcoredump. >+ * >+ * Only disable from devcoredump output. > */ >- return; >+ if (p->coredump) but we do want the guc log to be inside the devcoredump, so rather than adding more workarounds, can we fix it ? Lucas De Marchi ^ permalink raw reply [flat|nested] 22+ messages in thread
* Re: [PATCH v3 1/1] drm/xe/guc: Fix GuC log/ct output via debugfs 2025-01-07 21:10 ` [PATCH v3 1/1] " Lucas De Marchi @ 2025-01-08 20:14 ` John Harrison 2025-01-08 22:11 ` Lucas De Marchi 0 siblings, 1 reply; 22+ messages in thread From: John Harrison @ 2025-01-08 20:14 UTC (permalink / raw) To: Lucas De Marchi, Julia Filipchuk; +Cc: intel-xe On 1/7/2025 13:10, Lucas De Marchi wrote: > On Tue, Jan 07, 2025 at 12:22:52PM -0800, Julia Filipchuk wrote: >> Change to disable asci85 GuC logging only when output to devcoredump >> (was temporarily disabled for all code paths). >> >> v2: Ignore only for devcoredump case (not dmesg output). >> v3: Rebase to resolve parent tag mismatch. >> >> Signed-off-by: Julia Filipchuk <julia.filipchuk@intel.com> >> --- >> drivers/gpu/drm/xe/xe_devcoredump.c | 8 +++++--- >> include/drm/drm_print.h | 2 ++ >> 2 files changed, 7 insertions(+), 3 deletions(-) >> >> diff --git a/drivers/gpu/drm/xe/xe_devcoredump.c >> b/drivers/gpu/drm/xe/xe_devcoredump.c >> index 6980304c8903..8e5d1f9866a7 100644 >> --- a/drivers/gpu/drm/xe/xe_devcoredump.c >> +++ b/drivers/gpu/drm/xe/xe_devcoredump.c >> @@ -424,10 +424,12 @@ void xe_print_blob_ascii85(struct drm_printer >> *p, const char *prefix, >> * Splitting blobs across multiple lines is not compatible with >> the mesa >> * debug decoder tool. Note that even dropping the explicit '\n' >> below >> * doesn't help because the GuC log is so big some underlying >> implementation >> - * still splits the lines at 512K characters. So just bail >> completely for >> - * the moment. >> + * still splits the lines at 512K characters. > > did we investigate where this is done and how we can overcome it? I Yes. And the comment could be updated as part of this patch to make it clearer... * Splitting blobs across multiple lines is not compatible with the mesa * debug decoder tool. Note that even dropping the explicit line wrapping * below doesn't help because the GuC log can be so big it needs to be split * into multiple 2MB chunks, each of which must be printed individually and * therefore will be a separate line. The dump helper could be updated to never add any line feeds, not even at the end. And then the burden would be on the callers to add line feeds as appropriate. That seems extremely messy, though. And it will break the dmesg output facility. That does need the line wrapping at ~800 characters which can't be done from outside the helper. > > understand having to split it into multiple calls, but not something > adding a \n. particularly for the functions dealing with seq_file and > devcoredump. > >> + * >> + * Only disable from devcoredump output. >> */ >> - return; >> + if (p->coredump) > > but we do want the guc log to be inside the devcoredump, so rather than > adding more workarounds, can we fix it ? The simplest fix is your suggestion of adding an extra white space character at the end of the line in the helper function and updating the mesa tool to support multi-line output. That seems like it should be a trivial update to the mesa tool and it keeps the KMD side simple and consistent across all potential output methods. But Jose seemed absolutely dead set against any updates to the mesa tool at all :(. The more complex fix is Joonas' idea of using an official structured output format of some sort - TOML, YAML, JSON or whatever. Something that ideally supports binary data and compression natively and has a helper library that can be included in the kernel source tree. That will then remove any and all confusion over interpretation of the file forever more. But it would require updating all userland tools to use the appropriate helper library. John. > > Lucas De Marchi ^ permalink raw reply [flat|nested] 22+ messages in thread
* Re: [PATCH v3 1/1] drm/xe/guc: Fix GuC log/ct output via debugfs 2025-01-08 20:14 ` John Harrison @ 2025-01-08 22:11 ` Lucas De Marchi 2025-01-08 23:59 ` John Harrison 0 siblings, 1 reply; 22+ messages in thread From: Lucas De Marchi @ 2025-01-08 22:11 UTC (permalink / raw) To: John Harrison Cc: Julia Filipchuk, intel-xe, José Roberto de Souza, Rodrigo Vivi +Jose +Rodrigo On Wed, Jan 08, 2025 at 12:14:49PM -0800, John Harrison wrote: >On 1/7/2025 13:10, Lucas De Marchi wrote: >>On Tue, Jan 07, 2025 at 12:22:52PM -0800, Julia Filipchuk wrote: >>>Change to disable asci85 GuC logging only when output to devcoredump >>>(was temporarily disabled for all code paths). >>> >>>v2: Ignore only for devcoredump case (not dmesg output). >>>v3: Rebase to resolve parent tag mismatch. >>> >>>Signed-off-by: Julia Filipchuk <julia.filipchuk@intel.com> >>>--- >>>drivers/gpu/drm/xe/xe_devcoredump.c | 8 +++++--- >>>include/drm/drm_print.h | 2 ++ >>>2 files changed, 7 insertions(+), 3 deletions(-) >>> >>>diff --git a/drivers/gpu/drm/xe/xe_devcoredump.c >>>b/drivers/gpu/drm/xe/xe_devcoredump.c >>>index 6980304c8903..8e5d1f9866a7 100644 >>>--- a/drivers/gpu/drm/xe/xe_devcoredump.c >>>+++ b/drivers/gpu/drm/xe/xe_devcoredump.c >>>@@ -424,10 +424,12 @@ void xe_print_blob_ascii85(struct >>>drm_printer *p, const char *prefix, >>> * Splitting blobs across multiple lines is not compatible >>>with the mesa >>> * debug decoder tool. Note that even dropping the explicit >>>'\n' below >>> * doesn't help because the GuC log is so big some underlying >>>implementation >>>- * still splits the lines at 512K characters. So just bail >>>completely for >>>- * the moment. >>>+ * still splits the lines at 512K characters. >> >>did we investigate where this is done and how we can overcome it? I >Yes. And the comment could be updated as part of this patch to make it >clearer... > > > * Splitting blobs across multiple lines is not compatible with >the mesa > * debug decoder tool. Note that even dropping the explicit line >wrapping > * below doesn't help because the GuC log can be so big it needs >to be split > * into multiple 2MB chunks, each of which must be printed >individually and > * therefore will be a separate line. so there's no "underlying implemenation that splits like at 512K chars"? Nowe it's something else: a 2MB chunk because of what? I don't really want to keep updating this instead of fixing it. > >The dump helper could be updated to never add any line feeds, not even when you say "dump helper", what exactly are you talking about? xe_print_blob_ascii85(), __xe_devcoredump_read(), __drm_puts_coredump() or what? If it's about xe_print_blob_ascii85(), I think this would be the first step: drop the \n you are adding. AFAICS calling the print function in chunks of 800B would be fine, just don't add any \n. If that still adds \n somewhere, we can check how to drop it or you then may have a pretty solid argument to adapt the mesa tool with a newline continuar char and send them the MR. >at the end. And then the burden would be on the callers to add line >feeds as appropriate. That seems extremely messy, though. And it will >break the dmesg output facility. That does need the line wrapping at >~800 characters which can't be done from outside the helper. > >> >>understand having to split it into multiple calls, but not something >>adding a \n. particularly for the functions dealing with seq_file and >>devcoredump. >> >>>+ * >>>+ * Only disable from devcoredump output. >>> */ >>>- return; >>>+ if (p->coredump) >> >>but we do want the guc log to be inside the devcoredump, so rather than >>adding more workarounds, can we fix it ? >The simplest fix is your suggestion of adding an extra white space >character at the end of the line in the helper function and updating >the mesa tool to support multi-line output. That seems like it should >be a trivial update to the mesa tool and it keeps the KMD side simple >and consistent across all potential output methods. But Jose seemed >absolutely dead set against any updates to the mesa tool at all :(. > >The more complex fix is Joonas' idea of using an official structured >output format of some sort - TOML, YAML, JSON or whatever. Something it actually doesn't fix this particular issue. It fixes others, but not this one. "Guc Log": "<encoded data .........." if you need to split lines, you still need something to do do it in whatever format you choose. One json I remember working on in the past that embeds the binary is the .apj format... example: https://firmware.ardupilot.org/Copter/2024-12/2024-12-02-13:12/CubeBlack/arducopter.apj { "board_id": 9, "magic": "APJFWv1", "description": "Firmware for a STM32F427xx board", "image": "eNqUvAlcU1faMH5u7k1yCQGCICCgBoIaRW0EtVSxhg ... here "image" is base64-encoded afair. But in your case, just printing the json to dmesg wouldn't work because of needing to split the line. It wouldn't fix the kind of bugs we had in the past too: in json it would be the equivalent of adding a field to the wrong object and then move it elsewhere. An application trying to read that object in the previous place would be broken regardless. toml is more for configuration and yaml isn't a good one for this case as it further relies on indentation. I wouldn't oppose to use json, but don't expect to have dmesg to magically work because of that. So let's fix the issue at hand and let the talk about xe's coredump format for a later time. >that ideally supports binary data and compression natively and has a >helper library that can be included in the kernel source tree. That oh no, we'd need to define the schema - there are plenty of json libraries in multiple languages for users to choose from and that would be basically then main benefit of using it. Lucas De Marchi >will then remove any and all confusion over interpretation of the file >forever more. But it would require updating all userland tools to use >the appropriate helper library. > >John. > >> >>Lucas De Marchi > ^ permalink raw reply [flat|nested] 22+ messages in thread
* Re: [PATCH v3 1/1] drm/xe/guc: Fix GuC log/ct output via debugfs 2025-01-08 22:11 ` Lucas De Marchi @ 2025-01-08 23:59 ` John Harrison 2025-01-09 15:39 ` Lucas De Marchi 0 siblings, 1 reply; 22+ messages in thread From: John Harrison @ 2025-01-08 23:59 UTC (permalink / raw) To: Lucas De Marchi Cc: Julia Filipchuk, intel-xe, José Roberto de Souza, Rodrigo Vivi On 1/8/2025 14:11, Lucas De Marchi wrote: > +Jose > +Rodrigo > > On Wed, Jan 08, 2025 at 12:14:49PM -0800, John Harrison wrote: >> On 1/7/2025 13:10, Lucas De Marchi wrote: >>> On Tue, Jan 07, 2025 at 12:22:52PM -0800, Julia Filipchuk wrote: >>>> Change to disable asci85 GuC logging only when output to devcoredump >>>> (was temporarily disabled for all code paths). >>>> >>>> v2: Ignore only for devcoredump case (not dmesg output). >>>> v3: Rebase to resolve parent tag mismatch. >>>> >>>> Signed-off-by: Julia Filipchuk <julia.filipchuk@intel.com> >>>> --- >>>> drivers/gpu/drm/xe/xe_devcoredump.c | 8 +++++--- >>>> include/drm/drm_print.h | 2 ++ >>>> 2 files changed, 7 insertions(+), 3 deletions(-) >>>> >>>> diff --git a/drivers/gpu/drm/xe/xe_devcoredump.c >>>> b/drivers/gpu/drm/xe/xe_devcoredump.c >>>> index 6980304c8903..8e5d1f9866a7 100644 >>>> --- a/drivers/gpu/drm/xe/xe_devcoredump.c >>>> +++ b/drivers/gpu/drm/xe/xe_devcoredump.c >>>> @@ -424,10 +424,12 @@ void xe_print_blob_ascii85(struct drm_printer >>>> *p, const char *prefix, >>>> * Splitting blobs across multiple lines is not compatible with >>>> the mesa >>>> * debug decoder tool. Note that even dropping the explicit >>>> '\n' below >>>> * doesn't help because the GuC log is so big some underlying >>>> implementation >>>> - * still splits the lines at 512K characters. So just bail >>>> completely for >>>> - * the moment. >>>> + * still splits the lines at 512K characters. >>> >>> did we investigate where this is done and how we can overcome it? I >> Yes. And the comment could be updated as part of this patch to make >> it clearer... >> >> >> * Splitting blobs across multiple lines is not compatible with >> the mesa >> * debug decoder tool. Note that even dropping the explicit line >> wrapping >> * below doesn't help because the GuC log can be so big it needs >> to be split >> * into multiple 2MB chunks, each of which must be printed >> individually and >> * therefore will be a separate line. > > so there's no "underlying implemenation that splits like at 512K chars"? > Nowe it's something else: a 2MB chunk because of what? The GuC log is captured in multiple 2MB chunks because we can't kmalloc a full 16MB block at a single time irrespective of memory fragmentation - the kmalloc function aborts with a page size error above 8MB, I recall. Might even have been 4MB? The 2MB chunks become approx 512K characters of ASCII85 output (when mostly full of zeros). Because each chunk is a separate bo object the memory is not contiguous so each must be printed with a separate call to xe_print_blob_ascii85(). If xe_print_blob_ascii85() includes a terminating line feed at the end of the print then that means multiple lines for the GuC log. > > I don't really want to keep updating this instead of fixing it. > >> >> The dump helper could be updated to never add any line feeds, not even > > when you say "dump helper", what exactly are you talking about? > xe_print_blob_ascii85(), __xe_devcoredump_read(), __drm_puts_coredump() > or what? xe_print_blob_ascii85 > > If it's about xe_print_blob_ascii85(), I think this would be the first > step: > drop the \n you are adding. AFAICS calling the print function in chunks > of 800B would be fine, just don't add any \n. If that still adds \n > somewhere, we can check how to drop it or you then may have a pretty > solid argument to adapt the mesa tool with a newline > continuar char and send them the MR. As above, the chunking is at the next level out. So dropping the 800 byte \n won't help with the GuC log still being split into multiple lines. You have to either move the terminating \n outside of the helper and into the callers or add a bool parameter to enable/disable it. Either of which is just messy. Or extend the helper to take an array/list of pointers in a scatter/gather fashion. And if you drop the 800B \n then you break the dmesg output facility. Which means we can't get logs out from CI panic type situations. >> at the end. And then the burden would be on the callers to add line >> feeds as appropriate. That seems extremely messy, though. And it will >> break the dmesg output facility. That does need the line wrapping at >> ~800 characters which can't be done from outside the helper. >> >>> >>> understand having to split it into multiple calls, but not something >>> adding a \n. particularly for the functions dealing with seq_file and >>> devcoredump. >>> >>>> + * >>>> + * Only disable from devcoredump output. >>>> */ >>>> - return; >>>> + if (p->coredump) >>> >>> but we do want the guc log to be inside the devcoredump, so rather than >>> adding more workarounds, can we fix it ? >> The simplest fix is your suggestion of adding an extra white space >> character at the end of the line in the helper function and updating >> the mesa tool to support multi-line output. That seems like it should >> be a trivial update to the mesa tool and it keeps the KMD side simple >> and consistent across all potential output methods. But Jose seemed >> absolutely dead set against any updates to the mesa tool at all :(. >> >> The more complex fix is Joonas' idea of using an official structured >> output format of some sort - TOML, YAML, JSON or whatever. Something > > it actually doesn't fix this particular issue. It fixes others, but not > this one. If we do it properly then it fixes everything. The format library would have helper functions that the devcoredump code can call to print integers, bools, strings and BLOBs. The debugfs/sysfs output would just stream the encoded output exactly as is. The dmesg output layer would add the 800 character line wrapping in a way that the dmesg decoder can undo before passing to the decoder library. > > "Guc Log": "<encoded data .........." > > if you need to split lines, you still need something to do do it in > whatever format you choose. One json I remember working on in the past > that embeds the binary is the .apj format... example: > https://firmware.ardupilot.org/Copter/2024-12/2024-12-02-13:12/CubeBlack/arducopter.apj > > > { > "board_id": 9, > "magic": "APJFWv1", > "description": "Firmware for a STM32F427xx board", > "image": "eNqUvAlcU1faMH5u7k1yCQGCICCgBoIaRW0EtVSxhg ... > > here "image" is base64-encoded afair. But in your case, just printing > the json to dmesg wouldn't work because of needing to split the line. > It wouldn't fix the kind of bugs we had in the past too: in json it > would be the equivalent of adding a field to the wrong object and then > move it elsewhere. An application trying to read that object in the > previous place would be broken regardless. > > toml is more for configuration and yaml isn't a good one for this case > as it further relies on indentation. I wouldn't oppose to use json, but > don't expect to have dmesg to magically work because of that. TOML basically says 'use base64 and print it as a string'. And it supports multi-line strings, so the reader would have to drop newlines within a base64 object before doing the base64 decode. Or just use a base64 decoder that ignores whitespace. YAML seems to make even more explicit. From the 1.2.2 spec page: picture: !!binary | R0lGODlhDAAMAIQAAP//9/X 17unp5WZmZgAAAOfn515eXv Pz7Y6OjuDg4J+fn5OTk6enp 56enmleECcgggoBADs= So the userland reader just gets binary data straight out of the decoder library with no processing required. > > So let's fix the issue at hand and let the talk about xe's coredump > format for a later time. The issue at hand is that we have two fundamentally conflicting requirements. DMesg output requires line wrapping but the mesa tool has been coded in such a way that it breaks when given wrapped lines. There is nothing we can do about dmesg but making the mesa tool's parser more robust does not seem difficult. Switching to an externally defined encoding scheme that internally manages binary objects and supports wrapped lines would fix all issues and guarantee future compatibility. Note that line wrapping is not the only problem with the current mesa tool. Unless it has been updated since? The tool breaks if the context information is not part of the "GuC Communication Transport" section. Which is totally incorrect. Context state is very definitely not part of the GuC CT layer. That absolutely needs to be fixed. And generally, anything we can do to make the decoding more robust and future proof would be a very good thing. Note that the devcoredump content is highly dependent upon the internal workings of the driver. It is going to change over time. So the more robust the decoder, the better chance it has of not breaking when some new piece of data is added to the dump or an existing item removed or modified. > >> that ideally supports binary data and compression natively and has a >> helper library that can be included in the kernel source tree. That > > oh no, we'd need to define the schema - there are plenty of json > libraries > in multiple languages for users to choose from and that would be > basically > then main benefit of using it. Well, we can certainly define extra formats on top of a base format but it seems like it would be simpler if the base format supported all the data types we need already. Doesn't really matter either way as long as the underlying file format supports all the uses we want of it. John. > > Lucas De Marchi > >> will then remove any and all confusion over interpretation of the >> file forever more. But it would require updating all userland tools >> to use the appropriate helper library. >> >> John. >> >>> >>> Lucas De Marchi >> ^ permalink raw reply [flat|nested] 22+ messages in thread
* Re: [PATCH v3 1/1] drm/xe/guc: Fix GuC log/ct output via debugfs 2025-01-08 23:59 ` John Harrison @ 2025-01-09 15:39 ` Lucas De Marchi 2025-01-09 20:40 ` John Harrison 0 siblings, 1 reply; 22+ messages in thread From: Lucas De Marchi @ 2025-01-09 15:39 UTC (permalink / raw) To: John Harrison Cc: Julia Filipchuk, intel-xe, José Roberto de Souza, Rodrigo Vivi On Wed, Jan 08, 2025 at 03:59:58PM -0800, John Harrison wrote: >On 1/8/2025 14:11, Lucas De Marchi wrote: >>+Jose >>+Rodrigo >> >>On Wed, Jan 08, 2025 at 12:14:49PM -0800, John Harrison wrote: >>>On 1/7/2025 13:10, Lucas De Marchi wrote: >>>>On Tue, Jan 07, 2025 at 12:22:52PM -0800, Julia Filipchuk wrote: >>>>>Change to disable asci85 GuC logging only when output to devcoredump >>>>>(was temporarily disabled for all code paths). >>>>> >>>>>v2: Ignore only for devcoredump case (not dmesg output). >>>>>v3: Rebase to resolve parent tag mismatch. >>>>> >>>>>Signed-off-by: Julia Filipchuk <julia.filipchuk@intel.com> >>>>>--- >>>>>drivers/gpu/drm/xe/xe_devcoredump.c | 8 +++++--- >>>>>include/drm/drm_print.h | 2 ++ >>>>>2 files changed, 7 insertions(+), 3 deletions(-) >>>>> >>>>>diff --git a/drivers/gpu/drm/xe/xe_devcoredump.c >>>>>b/drivers/gpu/drm/xe/xe_devcoredump.c >>>>>index 6980304c8903..8e5d1f9866a7 100644 >>>>>--- a/drivers/gpu/drm/xe/xe_devcoredump.c >>>>>+++ b/drivers/gpu/drm/xe/xe_devcoredump.c >>>>>@@ -424,10 +424,12 @@ void xe_print_blob_ascii85(struct >>>>>drm_printer *p, const char *prefix, >>>>> * Splitting blobs across multiple lines is not compatible >>>>>with the mesa >>>>> * debug decoder tool. Note that even dropping the >>>>>explicit '\n' below >>>>> * doesn't help because the GuC log is so big some >>>>>underlying implementation >>>>>- * still splits the lines at 512K characters. So just >>>>>bail completely for >>>>>- * the moment. >>>>>+ * still splits the lines at 512K characters. >>>> >>>>did we investigate where this is done and how we can overcome it? I >>>Yes. And the comment could be updated as part of this patch to >>>make it clearer... >>> >>> >>> * Splitting blobs across multiple lines is not compatible >>>with the mesa >>> * debug decoder tool. Note that even dropping the explicit >>>line wrapping >>> * below doesn't help because the GuC log can be so big it >>>needs to be split >>> * into multiple 2MB chunks, each of which must be printed >>>individually and >>> * therefore will be a separate line. >> >>so there's no "underlying implemenation that splits like at 512K chars"? >>Nowe it's something else: a 2MB chunk because of what? >The GuC log is captured in multiple 2MB chunks because we can't >kmalloc a full 16MB block at a single time irrespective of memory >fragmentation - the kmalloc function aborts with a page size error >above 8MB, I recall. Might even have been 4MB? The 2MB chunks become >approx 512K characters of ASCII85 output (when mostly full of zeros). >Because each chunk is a separate bo object the memory is not >contiguous so each must be printed with a separate call to >xe_print_blob_ascii85(). If xe_print_blob_ascii85() includes a >terminating line feed at the end of the print then that means multiple >lines for the GuC log. now it makes sense... and contradicts what was said earlier about the "underlying implementation still splits the lines at 512K characters". It's this very function that is splitting it. > >> >>I don't really want to keep updating this instead of fixing it. >> >>> >>>The dump helper could be updated to never add any line feeds, not >>>even >> >>when you say "dump helper", what exactly are you talking about? >>xe_print_blob_ascii85(), __xe_devcoredump_read(), __drm_puts_coredump() >>or what? >xe_print_blob_ascii85 > >> >>If it's about xe_print_blob_ascii85(), I think this would be the >>first step: >>drop the \n you are adding. AFAICS calling the print function in chunks >>of 800B would be fine, just don't add any \n. If that still adds \n >>somewhere, we can check how to drop it or you then may have a pretty >>solid argument to adapt the mesa tool with a newline >>continuar char and send them the MR. >As above, the chunking is at the next level out. So dropping the 800 >byte \n won't help with the GuC log still being split into multiple >lines. You have to either move the terminating \n outside of the >helper and into the callers or add a bool parameter to enable/disable >it. Either of which is just messy. If the caller knows it's calling the function multiple times to continue previous data, it's not unreasonable to have an arg to terminate it or not. It's for example what python does with its 'end' arg to the print() function. > >Or extend the helper to take an array/list of pointers in a >scatter/gather fashion. > >And if you drop the 800B \n then you break the dmesg output facility. >Which means we can't get logs out from CI panic type situations. Or that we should have another way to get a devcoredump. I don't think we are going to print the devcoredump to dmesg when the kernel panics. We may print it when we fail to probe, but the cpu should still be very much alive - we tie the devcoredump lifecycle to the lifecycle of the device, so we don't have an opportunity to get that data. The workaround you add is to dump the whole thing to dmesg, but we could dump it somewhere else like a debugfs that is tied to the module lifecycle. The dmesg (kmsg) format already contains other things you have to ignore to extract the message: * /dev/kmsg exports the structured data in the following line format: * "<level>,<sequnum>,<timestamp>,<contflag>[,additional_values, ... ];<message text>\n" so you will always have to preprocess it, ignore lines that don't belong to the log, etc. And if you print it correctly, you can even make use of the LOG_CONT to mark the new line as continuation of the previous one. > >>>at the end. And then the burden would be on the callers to add >>>line feeds as appropriate. That seems extremely messy, though. And >>>it will break the dmesg output facility. That does need the line >>>wrapping at ~800 characters which can't be done from outside the >>>helper. >>> >>>> >>>>understand having to split it into multiple calls, but not something >>>>adding a \n. particularly for the functions dealing with seq_file and >>>>devcoredump. >>>> >>>>>+ * >>>>>+ * Only disable from devcoredump output. >>>>> */ >>>>>- return; >>>>>+ if (p->coredump) >>>> >>>>but we do want the guc log to be inside the devcoredump, so rather than >>>>adding more workarounds, can we fix it ? >>>The simplest fix is your suggestion of adding an extra white space >>>character at the end of the line in the helper function and >>>updating the mesa tool to support multi-line output. That seems >>>like it should be a trivial update to the mesa tool and it keeps >>>the KMD side simple and consistent across all potential output >>>methods. But Jose seemed absolutely dead set against any updates >>>to the mesa tool at all :(. >>> >>>The more complex fix is Joonas' idea of using an official >>>structured output format of some sort - TOML, YAML, JSON or >>>whatever. Something >> >>it actually doesn't fix this particular issue. It fixes others, but not >>this one. >If we do it properly then it fixes everything. The format library >would have helper functions that the devcoredump code can call to but we are *NOT* going to export a library for that. You are just shifting the problem to "we have only one userspace that is our own library, deal with it". >print integers, bools, strings and BLOBs. The debugfs/sysfs output >would just stream the encoded output exactly as is. The dmesg output >layer would add the 800 character line wrapping in a way that the >dmesg decoder can undo before passing to the decoder library. > >> >> "Guc Log": "<encoded data .........." >> >>if you need to split lines, you still need something to do do it in >>whatever format you choose. One json I remember working on in the past >>that embeds the binary is the .apj format... example: >>https://firmware.ardupilot.org/Copter/2024-12/2024-12-02-13:12/CubeBlack/arducopter.apj >> >> >> { >> "board_id": 9, >> "magic": "APJFWv1", >> "description": "Firmware for a STM32F427xx board", >> "image": "eNqUvAlcU1faMH5u7k1yCQGCICCgBoIaRW0EtVSxhg ... >> >>here "image" is base64-encoded afair. But in your case, just printing >>the json to dmesg wouldn't work because of needing to split the line. >>It wouldn't fix the kind of bugs we had in the past too: in json it >>would be the equivalent of adding a field to the wrong object and then >>move it elsewhere. An application trying to read that object in the >>previous place would be broken regardless. >> >>toml is more for configuration and yaml isn't a good one for this case >>as it further relies on indentation. I wouldn't oppose to use json, but >>don't expect to have dmesg to magically work because of that. >TOML basically says 'use base64 and print it as a string'. And it >supports multi-line strings, so the reader would have to drop newlines >within a base64 object before doing the base64 decode. Or just use a >base64 decoder that ignores whitespace. > >YAML seems to make even more explicit. From the 1.2.2 spec page: > picture: !!binary | > R0lGODlhDAAMAIQAAP//9/X ^ space here for line continuation, as I mentioned. > 17unp5WZmZgAAAOfn515eXv > Pz7Y6OjuDg4J+fn5OTk6enp > 56enmleECcgggoBADs= > >So the userland reader just gets binary data straight out of the >decoder library with no processing required. A decoder library that we are *NOT* going to write. > > >> >>So let's fix the issue at hand and let the talk about xe's coredump >>format for a later time. >The issue at hand is that we have two fundamentally conflicting >requirements. DMesg output requires line wrapping but the mesa tool >has been coded in such a way that it breaks when given wrapped lines. >There is nothing we can do about dmesg but making the mesa tool's >parser more robust does not seem difficult. > >Switching to an externally defined encoding scheme that internally >manages binary objects and supports wrapped lines would fix all issues >and guarantee future compatibility. > >Note that line wrapping is not the only problem with the current mesa >tool. Unless it has been updated since? The tool breaks if the context >information is not part of the "GuC Communication Transport" section. >Which is totally incorrect. Context state is very definitely not part We reverted it because it's not ok to just move it to the "correct" place and break the users. If it's in the incorrect place and we know there's this parser already using it incorrectly, we can treat as a bug in the kernel and adjust the userspace (it'd be considered a bug there too and backported to their earlier releases). What we don't do is simply merge the fix and break userspace. Send the fix to the mesa tool if you want to change this in the kernel. And as I said, for this particular change it doesn't matter if it's a custom format, json, toml or whatever... the bug would still be the same. >of the GuC CT layer. That absolutely needs to be fixed. And generally, >anything we can do to make the decoding more robust and future proof >would be a very good thing. > >Note that the devcoredump content is highly dependent upon the >internal workings of the driver. It is going to change over time. So >the more robust the decoder, the better chance it has of not breaking >when some new piece of data is added to the dump or an existing item >removed or modified. > >> >>>that ideally supports binary data and compression natively and has >>>a helper library that can be included in the kernel source tree. >>>That >> >>oh no, we'd need to define the schema - there are plenty of json >>libraries >>in multiple languages for users to choose from and that would be >>basically >>then main benefit of using it. >Well, we can certainly define extra formats on top of a base format >but it seems like it would be simpler if the base format supported all >the data types we need already. Doesn't really matter either way as >long as the underlying file format supports all the uses we want of >it. My point is that we are not going to add a decoder library that all userspace consumers have to use. The kernel interface is not a library. You are relying on having just one userspace to not break userspace. The benefit of a common format like json, toml etc is exactly that it's a format already understood by hundreds of libraries and we can even do something like this instead of having to write our own parser: cat devcoredump | jq '.[] | .foo, .bar' Lucas De Marchi > >John. > >> >>Lucas De Marchi >> >>>will then remove any and all confusion over interpretation of the >>>file forever more. But it would require updating all userland >>>tools to use the appropriate helper library. >>> >>>John. >>> >>>> >>>>Lucas De Marchi >>> > ^ permalink raw reply [flat|nested] 22+ messages in thread
* Re: [PATCH v3 1/1] drm/xe/guc: Fix GuC log/ct output via debugfs 2025-01-09 15:39 ` Lucas De Marchi @ 2025-01-09 20:40 ` John Harrison 2025-01-09 22:43 ` Lucas De Marchi 0 siblings, 1 reply; 22+ messages in thread From: John Harrison @ 2025-01-09 20:40 UTC (permalink / raw) To: Lucas De Marchi Cc: Julia Filipchuk, intel-xe, José Roberto de Souza, Rodrigo Vivi On 1/9/2025 07:39, Lucas De Marchi wrote: > On Wed, Jan 08, 2025 at 03:59:58PM -0800, John Harrison wrote: >> On 1/8/2025 14:11, Lucas De Marchi wrote: >>> +Jose >>> +Rodrigo >>> >>> On Wed, Jan 08, 2025 at 12:14:49PM -0800, John Harrison wrote: >>>> On 1/7/2025 13:10, Lucas De Marchi wrote: >>>>> On Tue, Jan 07, 2025 at 12:22:52PM -0800, Julia Filipchuk wrote: >>>>>> Change to disable asci85 GuC logging only when output to devcoredump >>>>>> (was temporarily disabled for all code paths). >>>>>> >>>>>> v2: Ignore only for devcoredump case (not dmesg output). >>>>>> v3: Rebase to resolve parent tag mismatch. >>>>>> >>>>>> Signed-off-by: Julia Filipchuk <julia.filipchuk@intel.com> >>>>>> --- >>>>>> drivers/gpu/drm/xe/xe_devcoredump.c | 8 +++++--- >>>>>> include/drm/drm_print.h | 2 ++ >>>>>> 2 files changed, 7 insertions(+), 3 deletions(-) >>>>>> >>>>>> diff --git a/drivers/gpu/drm/xe/xe_devcoredump.c >>>>>> b/drivers/gpu/drm/xe/xe_devcoredump.c >>>>>> index 6980304c8903..8e5d1f9866a7 100644 >>>>>> --- a/drivers/gpu/drm/xe/xe_devcoredump.c >>>>>> +++ b/drivers/gpu/drm/xe/xe_devcoredump.c >>>>>> @@ -424,10 +424,12 @@ void xe_print_blob_ascii85(struct >>>>>> drm_printer *p, const char *prefix, >>>>>> * Splitting blobs across multiple lines is not compatible >>>>>> with the mesa >>>>>> * debug decoder tool. Note that even dropping the explicit >>>>>> '\n' below >>>>>> * doesn't help because the GuC log is so big some underlying >>>>>> implementation >>>>>> - * still splits the lines at 512K characters. So just bail >>>>>> completely for >>>>>> - * the moment. >>>>>> + * still splits the lines at 512K characters. >>>>> >>>>> did we investigate where this is done and how we can overcome it? I >>>> Yes. And the comment could be updated as part of this patch to make >>>> it clearer... >>>> >>>> >>>> * Splitting blobs across multiple lines is not compatible with >>>> the mesa >>>> * debug decoder tool. Note that even dropping the explicit >>>> line wrapping >>>> * below doesn't help because the GuC log can be so big it >>>> needs to be split >>>> * into multiple 2MB chunks, each of which must be printed >>>> individually and >>>> * therefore will be a separate line. >>> >>> so there's no "underlying implemenation that splits like at 512K >>> chars"? >>> Nowe it's something else: a 2MB chunk because of what? >> The GuC log is captured in multiple 2MB chunks because we can't >> kmalloc a full 16MB block at a single time irrespective of memory >> fragmentation - the kmalloc function aborts with a page size error >> above 8MB, I recall. Might even have been 4MB? The 2MB chunks become >> approx 512K characters of ASCII85 output (when mostly full of zeros). >> Because each chunk is a separate bo object the memory is not >> contiguous so each must be printed with a separate call to >> xe_print_blob_ascii85(). If xe_print_blob_ascii85() includes a >> terminating line feed at the end of the print then that means >> multiple lines for the GuC log. > > now it makes sense... and contradicts what was said earlier about the > "underlying implementation still splits the lines at 512K characters". > It's this very function that is splitting it. The initial comment was written before the situation was fully understood because it was a quick hack to get the mesa debug tool working again. The split is a combination of the helper function adding a linefeed to the end of the output and the GuC log being so large it must be split into multiple malloc buffers. But it is not related to the 800 character line wrapping within the helper's output. > >> >>> >>> I don't really want to keep updating this instead of fixing it. >>> >>>> >>>> The dump helper could be updated to never add any line feeds, not even >>> >>> when you say "dump helper", what exactly are you talking about? >>> xe_print_blob_ascii85(), __xe_devcoredump_read(), __drm_puts_coredump() >>> or what? >> xe_print_blob_ascii85 >> >>> >>> If it's about xe_print_blob_ascii85(), I think this would be the >>> first step: >>> drop the \n you are adding. AFAICS calling the print function in chunks >>> of 800B would be fine, just don't add any \n. If that still adds \n >>> somewhere, we can check how to drop it or you then may have a pretty >>> solid argument to adapt the mesa tool with a newline >>> continuar char and send them the MR. >> As above, the chunking is at the next level out. So dropping the 800 >> byte \n won't help with the GuC log still being split into multiple >> lines. You have to either move the terminating \n outside of the >> helper and into the callers or add a bool parameter to enable/disable >> it. Either of which is just messy. > > If the caller knows it's calling the function multiple times to continue > previous data, it's not unreasonable to have an arg to terminate it or > not. It's for example what python does with its 'end' arg to the print() > function. Just because someone else does it does not make it clean or the best solution. > >> >> Or extend the helper to take an array/list of pointers in a >> scatter/gather fashion. >> >> And if you drop the 800B \n then you break the dmesg output facility. >> Which means we can't get logs out from CI panic type situations. > > Or that we should have another way to get a devcoredump. I don't think > we are going to print the devcoredump to dmesg when the kernel panics. > We may print it when we fail to probe, but the cpu should still be very > much alive - we tie the devcoredump lifecycle to the lifecycle of the > device, so we don't have an opportunity to get that data. > > The workaround you add is to dump the whole thing to dmesg, but we could > dump it somewhere else like a debugfs that is tied to the module > lifecycle. The point is to get usable logs out of CI. There are multiple situations in which CI fails to save logs. By 'panic' I was more meaning situations where we have very rare bugs that can't be hit locally and for which CI is not providing useful logs. I.e. we are in a panic about how to debug it and dumping via dmesg is the only viable option. > > The dmesg (kmsg) format already contains other things you have to ignore > to extract the message: > > * /dev/kmsg exports the structured data in the following line > format: * > "<level>,<sequnum>,<timestamp>,<contflag>[,additional_values, ... > ];<message text>\n" > > so you will always have to preprocess it, ignore lines that don't belong > to the log, etc. I never said this was not the case. The GuC log decoding tool already copes with myriad different dmesg, syslog, serial console, etc. output formats. > > And if you print it correctly, you can even make use of the LOG_CONT to > mark the new line as continuation of the previous one. Reconstructing split lines has never been a problem for GuC decoder tool. It is only the mesa tool that has a problem with line feeds. > >> >>>> at the end. And then the burden would be on the callers to add line >>>> feeds as appropriate. That seems extremely messy, though. And it >>>> will break the dmesg output facility. That does need the line >>>> wrapping at ~800 characters which can't be done from outside the >>>> helper. >>>> >>>>> >>>>> understand having to split it into multiple calls, but not something >>>>> adding a \n. particularly for the functions dealing with seq_file and >>>>> devcoredump. >>>>> >>>>>> + * >>>>>> + * Only disable from devcoredump output. >>>>>> */ >>>>>> - return; >>>>>> + if (p->coredump) >>>>> >>>>> but we do want the guc log to be inside the devcoredump, so rather >>>>> than >>>>> adding more workarounds, can we fix it ? >>>> The simplest fix is your suggestion of adding an extra white space >>>> character at the end of the line in the helper function and >>>> updating the mesa tool to support multi-line output. That seems >>>> like it should be a trivial update to the mesa tool and it keeps >>>> the KMD side simple and consistent across all potential output >>>> methods. But Jose seemed absolutely dead set against any updates to >>>> the mesa tool at all :(. >>>> >>>> The more complex fix is Joonas' idea of using an official >>>> structured output format of some sort - TOML, YAML, JSON or >>>> whatever. Something >>> >>> it actually doesn't fix this particular issue. It fixes others, but not >>> this one. >> If we do it properly then it fixes everything. The format library >> would have helper functions that the devcoredump code can call to > > but we are *NOT* going to export a library for that. You are just > shifting the problem to "we have only one userspace that is our own > library, deal with it". No. By library, I mean libjson or libyaml or whatever. The whole point of using an externally defined file format is that you can use an externally written library to read that format. Whatever userspace tool only has to worry about processing data/value pairs or whatever you get from the library's read interface, it no longer has to worry about file formats, character encodings, line wraps, etc. All that is handled by the third party library / file format definition. > >> print integers, bools, strings and BLOBs. The debugfs/sysfs output >> would just stream the encoded output exactly as is. The dmesg output >> layer would add the 800 character line wrapping in a way that the >> dmesg decoder can undo before passing to the decoder library. >> >>> >>> "Guc Log": "<encoded data .........." >>> >>> if you need to split lines, you still need something to do do it in >>> whatever format you choose. One json I remember working on in the past >>> that embeds the binary is the .apj format... example: >>> https://firmware.ardupilot.org/Copter/2024-12/2024-12-02-13:12/CubeBlack/arducopter.apj >>> >>> >>> >>> { >>> "board_id": 9, >>> "magic": "APJFWv1", >>> "description": "Firmware for a STM32F427xx board", >>> "image": "eNqUvAlcU1faMH5u7k1yCQGCICCgBoIaRW0EtVSxhg ... >>> >>> here "image" is base64-encoded afair. But in your case, just printing >>> the json to dmesg wouldn't work because of needing to split the line. >>> It wouldn't fix the kind of bugs we had in the past too: in json it >>> would be the equivalent of adding a field to the wrong object and then >>> move it elsewhere. An application trying to read that object in the >>> previous place would be broken regardless. >>> >>> toml is more for configuration and yaml isn't a good one for this case >>> as it further relies on indentation. I wouldn't oppose to use json, but >>> don't expect to have dmesg to magically work because of that. >> TOML basically says 'use base64 and print it as a string'. And it >> supports multi-line strings, so the reader would have to drop >> newlines within a base64 object before doing the base64 decode. Or >> just use a base64 decoder that ignores whitespace. >> >> YAML seems to make even more explicit. From the 1.2.2 spec page: >> picture: !!binary | >> R0lGODlhDAAMAIQAAP//9/X > ^ space here for line continuation, as I mentioned. > >> 17unp5WZmZgAAAOfn515eXv >> Pz7Y6OjuDg4J+fn5OTk6enp >> 56enmleECcgggoBADs= >> >> So the userland reader just gets binary data straight out of the >> decoder library with no processing required. > > A decoder library that we are *NOT* going to write. As above, the decoder library is definitely not written by us. It is libyaml or some such. > > >> >> >>> >>> So let's fix the issue at hand and let the talk about xe's coredump >>> format for a later time. >> The issue at hand is that we have two fundamentally conflicting >> requirements. DMesg output requires line wrapping but the mesa tool >> has been coded in such a way that it breaks when given wrapped lines. >> There is nothing we can do about dmesg but making the mesa tool's >> parser more robust does not seem difficult. >> >> Switching to an externally defined encoding scheme that internally >> manages binary objects and supports wrapped lines would fix all >> issues and guarantee future compatibility. >> >> Note that line wrapping is not the only problem with the current mesa >> tool. Unless it has been updated since? The tool breaks if the >> context information is not part of the "GuC Communication Transport" >> section. Which is totally incorrect. Context state is very definitely >> not part > > We reverted it because it's not ok to just move it to the "correct" > place and break the users. If it's in the incorrect place and we know > there's this parser already using it incorrectly, we can treat as a bug > in the kernel and adjust the userspace (it'd be considered a bug there > too and backported to their earlier releases). What we don't do is > simply merge the fix and break userspace. Can we not repeat old arguments? No-one realised that that change would break userspace. Or if they did, there was confusion over what exactly had or had not been tested and was causing a problem. Certainly it was not an intentional "merge and everyone be damned". My point was that there are multiple issues here. Line feeds is only one. But using a structured file format would prevent both of the problems we have currently hit. > > Send the fix to the mesa tool if you want to change this in the kernel. When I can finally work out how to build mesa (it seems to require libraries that are newer than any Ubuntu release has access to!?) and have spent time learning yet another code base and how the tool is implemented... > > And as I said, for this particular change it doesn't matter if it's a > custom format, json, toml or whatever... the bug would still be the > same. Ideally not. Part of moving to a structured file format would be ensuring that the structure of the data is correct. > >> of the GuC CT layer. That absolutely needs to be fixed. And >> generally, anything we can do to make the decoding more robust and >> future proof would be a very good thing. >> >> Note that the devcoredump content is highly dependent upon the >> internal workings of the driver. It is going to change over time. So >> the more robust the decoder, the better chance it has of not breaking >> when some new piece of data is added to the dump or an existing item >> removed or modified. >> >>> >>>> that ideally supports binary data and compression natively and has >>>> a helper library that can be included in the kernel source tree. That >>> >>> oh no, we'd need to define the schema - there are plenty of json >>> libraries >>> in multiple languages for users to choose from and that would be >>> basically >>> then main benefit of using it. >> Well, we can certainly define extra formats on top of a base format >> but it seems like it would be simpler if the base format supported >> all the data types we need already. Doesn't really matter either way >> as long as the underlying file format supports all the uses we want >> of it. > > My point is that we are not going to add a decoder library that all > userspace consumers have to use. The kernel interface is not a library. > You are relying on having just one userspace to not break userspace. That is not at all what I am saying. > > The benefit of a common format like json, toml etc is exactly that it's > a format already understood by hundreds of libraries and we can even do > something like this instead of having to write our own parser: > > cat devcoredump | jq '.[] | .foo, .bar' That is exactly what I am saying. The mesa debug tool becomes something like: #include <libyaml> info = yaml.read_file(file_name); foreach_engine(info.engines, i) printf( "Got hang on %s\n", info.engines[i].name ); The external library handles all the file encoding issues. The tool just has to put meaning to the fields returned from that library. John. > > Lucas De Marchi > >> >> John. >> >>> >>> Lucas De Marchi >>> >>>> will then remove any and all confusion over interpretation of the >>>> file forever more. But it would require updating all userland tools >>>> to use the appropriate helper library. >>>> >>>> John. >>>> >>>>> >>>>> Lucas De Marchi >>>> >> ^ permalink raw reply [flat|nested] 22+ messages in thread
* Re: [PATCH v3 1/1] drm/xe/guc: Fix GuC log/ct output via debugfs 2025-01-09 20:40 ` John Harrison @ 2025-01-09 22:43 ` Lucas De Marchi 2025-01-22 16:45 ` John Harrison 0 siblings, 1 reply; 22+ messages in thread From: Lucas De Marchi @ 2025-01-09 22:43 UTC (permalink / raw) To: John Harrison Cc: Julia Filipchuk, intel-xe, José Roberto de Souza, Rodrigo Vivi On Thu, Jan 09, 2025 at 12:40:51PM -0800, John Harrison wrote: >On 1/9/2025 07:39, Lucas De Marchi wrote: >>On Wed, Jan 08, 2025 at 03:59:58PM -0800, John Harrison wrote: >>>On 1/8/2025 14:11, Lucas De Marchi wrote: >>>>+Jose >>>>+Rodrigo >>>> >>>>On Wed, Jan 08, 2025 at 12:14:49PM -0800, John Harrison wrote: >>>>>On 1/7/2025 13:10, Lucas De Marchi wrote: >>>>>>On Tue, Jan 07, 2025 at 12:22:52PM -0800, Julia Filipchuk wrote: >>>>>>>Change to disable asci85 GuC logging only when output to devcoredump >>>>>>>(was temporarily disabled for all code paths). >>>>>>> >>>>>>>v2: Ignore only for devcoredump case (not dmesg output). >>>>>>>v3: Rebase to resolve parent tag mismatch. >>>>>>> >>>>>>>Signed-off-by: Julia Filipchuk <julia.filipchuk@intel.com> >>>>>>>--- >>>>>>>drivers/gpu/drm/xe/xe_devcoredump.c | 8 +++++--- >>>>>>>include/drm/drm_print.h | 2 ++ >>>>>>>2 files changed, 7 insertions(+), 3 deletions(-) >>>>>>> >>>>>>>diff --git a/drivers/gpu/drm/xe/xe_devcoredump.c >>>>>>>b/drivers/gpu/drm/xe/xe_devcoredump.c >>>>>>>index 6980304c8903..8e5d1f9866a7 100644 >>>>>>>--- a/drivers/gpu/drm/xe/xe_devcoredump.c >>>>>>>+++ b/drivers/gpu/drm/xe/xe_devcoredump.c >>>>>>>@@ -424,10 +424,12 @@ void xe_print_blob_ascii85(struct >>>>>>>drm_printer *p, const char *prefix, >>>>>>> * Splitting blobs across multiple lines is not >>>>>>>compatible with the mesa >>>>>>> * debug decoder tool. Note that even dropping the >>>>>>>explicit '\n' below >>>>>>> * doesn't help because the GuC log is so big some >>>>>>>underlying implementation >>>>>>>- * still splits the lines at 512K characters. So just >>>>>>>bail completely for >>>>>>>- * the moment. >>>>>>>+ * still splits the lines at 512K characters. >>>>>> >>>>>>did we investigate where this is done and how we can overcome it? I >>>>>Yes. And the comment could be updated as part of this patch to >>>>>make it clearer... >>>>> >>>>> >>>>> * Splitting blobs across multiple lines is not compatible >>>>>with the mesa >>>>> * debug decoder tool. Note that even dropping the >>>>>explicit line wrapping >>>>> * below doesn't help because the GuC log can be so big it >>>>>needs to be split >>>>> * into multiple 2MB chunks, each of which must be printed >>>>>individually and >>>>> * therefore will be a separate line. >>>> >>>>so there's no "underlying implemenation that splits like at 512K >>>>chars"? >>>>Nowe it's something else: a 2MB chunk because of what? >>>The GuC log is captured in multiple 2MB chunks because we can't >>>kmalloc a full 16MB block at a single time irrespective of memory >>>fragmentation - the kmalloc function aborts with a page size error >>>above 8MB, I recall. Might even have been 4MB? The 2MB chunks >>>become approx 512K characters of ASCII85 output (when mostly full >>>of zeros). Because each chunk is a separate bo object the memory >>>is not contiguous so each must be printed with a separate call to >>>xe_print_blob_ascii85(). If xe_print_blob_ascii85() includes a >>>terminating line feed at the end of the print then that means >>>multiple lines for the GuC log. >> >>now it makes sense... and contradicts what was said earlier about the >>"underlying implementation still splits the lines at 512K characters". >>It's this very function that is splitting it. >The initial comment was written before the situation was fully >understood because it was a quick hack to get the mesa debug tool >working again. > >The split is a combination of the helper function adding a linefeed to >the end of the output and the GuC log being so large it must be split >into multiple malloc buffers. But it is not related to the 800 >character line wrapping within the helper's output. > >> >>> >>>> >>>>I don't really want to keep updating this instead of fixing it. >>>> >>>>> >>>>>The dump helper could be updated to never add any line feeds, not even >>>> >>>>when you say "dump helper", what exactly are you talking about? >>>>xe_print_blob_ascii85(), __xe_devcoredump_read(), __drm_puts_coredump() >>>>or what? >>>xe_print_blob_ascii85 >>> >>>> >>>>If it's about xe_print_blob_ascii85(), I think this would be the >>>>first step: >>>>drop the \n you are adding. AFAICS calling the print function in chunks >>>>of 800B would be fine, just don't add any \n. If that still adds \n >>>>somewhere, we can check how to drop it or you then may have a pretty >>>>solid argument to adapt the mesa tool with a newline >>>>continuar char and send them the MR. >>>As above, the chunking is at the next level out. So dropping the >>>800 byte \n won't help with the GuC log still being split into >>>multiple lines. You have to either move the terminating \n outside >>>of the helper and into the callers or add a bool parameter to >>>enable/disable it. Either of which is just messy. >> >>If the caller knows it's calling the function multiple times to continue >>previous data, it's not unreasonable to have an arg to terminate it or >>not. It's for example what python does with its 'end' arg to the print() >>function. >Just because someone else does it does not make it clean or the best >solution. > >> >>> >>>Or extend the helper to take an array/list of pointers in a >>>scatter/gather fashion. >>> >>>And if you drop the 800B \n then you break the dmesg output >>>facility. Which means we can't get logs out from CI panic type >>>situations. >> >>Or that we should have another way to get a devcoredump. I don't think >>we are going to print the devcoredump to dmesg when the kernel panics. >>We may print it when we fail to probe, but the cpu should still be very >>much alive - we tie the devcoredump lifecycle to the lifecycle of the >>device, so we don't have an opportunity to get that data. >> >>The workaround you add is to dump the whole thing to dmesg, but we could >>dump it somewhere else like a debugfs that is tied to the module >>lifecycle. >The point is to get usable logs out of CI. There are multiple >situations in which CI fails to save logs. By 'panic' I was more >meaning situations where we have very rare bugs that can't be hit >locally and for which CI is not providing useful logs. I.e. we are in >a panic about how to debug it and dumping via dmesg is the only viable >option. > >> >>The dmesg (kmsg) format already contains other things you have to ignore >>to extract the message: >> >> * /dev/kmsg exports the structured data in the following line >>format: * >>"<level>,<sequnum>,<timestamp>,<contflag>[,additional_values, ... >>];<message text>\n" >> >>so you will always have to preprocess it, ignore lines that don't belong >>to the log, etc. >I never said this was not the case. The GuC log decoding tool already >copes with myriad different dmesg, syslog, serial console, etc. output >formats. > >> >>And if you print it correctly, you can even make use of the LOG_CONT to >>mark the new line as continuation of the previous one. >Reconstructing split lines has never been a problem for GuC decoder >tool. It is only the mesa tool that has a problem with line feeds. > >> >>> >>>>>at the end. And then the burden would be on the callers to add >>>>>line feeds as appropriate. That seems extremely messy, though. >>>>>And it will break the dmesg output facility. That does need >>>>>the line wrapping at ~800 characters which can't be done from >>>>>outside the helper. >>>>> >>>>>> >>>>>>understand having to split it into multiple calls, but not something >>>>>>adding a \n. particularly for the functions dealing with seq_file and >>>>>>devcoredump. >>>>>> >>>>>>>+ * >>>>>>>+ * Only disable from devcoredump output. >>>>>>> */ >>>>>>>- return; >>>>>>>+ if (p->coredump) >>>>>> >>>>>>but we do want the guc log to be inside the devcoredump, so >>>>>>rather than >>>>>>adding more workarounds, can we fix it ? >>>>>The simplest fix is your suggestion of adding an extra white >>>>>space character at the end of the line in the helper function >>>>>and updating the mesa tool to support multi-line output. That >>>>>seems like it should be a trivial update to the mesa tool and >>>>>it keeps the KMD side simple and consistent across all >>>>>potential output methods. But Jose seemed absolutely dead set >>>>>against any updates to the mesa tool at all :(. >>>>> >>>>>The more complex fix is Joonas' idea of using an official >>>>>structured output format of some sort - TOML, YAML, JSON or >>>>>whatever. Something >>>> >>>>it actually doesn't fix this particular issue. It fixes others, but not >>>>this one. >>>If we do it properly then it fixes everything. The format library >>>would have helper functions that the devcoredump code can call to >> >>but we are *NOT* going to export a library for that. You are just >>shifting the problem to "we have only one userspace that is our own >>library, deal with it". >No. By library, I mean libjson or libyaml or whatever. The whole point >of using an externally defined file format is that you can use an >externally written library to read that format. Whatever userspace >tool only has to worry about processing data/value pairs or whatever >you get from the library's read interface, it no longer has to worry >about file formats, character encodings, line wraps, etc. All that is >handled by the third party library / file format definition. > >> >>>print integers, bools, strings and BLOBs. The debugfs/sysfs output >>>would just stream the encoded output exactly as is. The dmesg >>>output layer would add the 800 character line wrapping in a way >>>that the dmesg decoder can undo before passing to the decoder >>>library. >>> >>>> >>>> "Guc Log": "<encoded data .........." >>>> >>>>if you need to split lines, you still need something to do do it in >>>>whatever format you choose. One json I remember working on in the past >>>>that embeds the binary is the .apj format... example: >>>>https://firmware.ardupilot.org/Copter/2024-12/2024-12-02-13:12/CubeBlack/arducopter.apj >>>> >>>> >>>> >>>> { >>>> "board_id": 9, >>>> "magic": "APJFWv1", >>>> "description": "Firmware for a STM32F427xx board", >>>> "image": "eNqUvAlcU1faMH5u7k1yCQGCICCgBoIaRW0EtVSxhg ... >>>> >>>>here "image" is base64-encoded afair. But in your case, just printing >>>>the json to dmesg wouldn't work because of needing to split the line. >>>>It wouldn't fix the kind of bugs we had in the past too: in json it >>>>would be the equivalent of adding a field to the wrong object and then >>>>move it elsewhere. An application trying to read that object in the >>>>previous place would be broken regardless. >>>> >>>>toml is more for configuration and yaml isn't a good one for this case >>>>as it further relies on indentation. I wouldn't oppose to use json, but >>>>don't expect to have dmesg to magically work because of that. >>>TOML basically says 'use base64 and print it as a string'. And it >>>supports multi-line strings, so the reader would have to drop >>>newlines within a base64 object before doing the base64 decode. Or >>>just use a base64 decoder that ignores whitespace. >>> >>>YAML seems to make even more explicit. From the 1.2.2 spec page: >>> picture: !!binary | >>> R0lGODlhDAAMAIQAAP//9/X >> ^ space here for line continuation, as I mentioned. >> >>> 17unp5WZmZgAAAOfn515eXv >>> Pz7Y6OjuDg4J+fn5OTk6enp >>> 56enmleECcgggoBADs= >>> >>>So the userland reader just gets binary data straight out of the >>>decoder library with no processing required. >> >>A decoder library that we are *NOT* going to write. >As above, the decoder library is definitely not written by us. It is >libyaml or some such. > >> >> >>> >>> >>>> >>>>So let's fix the issue at hand and let the talk about xe's coredump >>>>format for a later time. >>>The issue at hand is that we have two fundamentally conflicting >>>requirements. DMesg output requires line wrapping but the mesa >>>tool has been coded in such a way that it breaks when given >>>wrapped lines. There is nothing we can do about dmesg but making >>>the mesa tool's parser more robust does not seem difficult. >>> >>>Switching to an externally defined encoding scheme that internally >>>manages binary objects and supports wrapped lines would fix all >>>issues and guarantee future compatibility. >>> >>>Note that line wrapping is not the only problem with the current >>>mesa tool. Unless it has been updated since? The tool breaks if >>>the context information is not part of the "GuC Communication >>>Transport" section. Which is totally incorrect. Context state is >>>very definitely not part >> >>We reverted it because it's not ok to just move it to the "correct" >>place and break the users. If it's in the incorrect place and we know >>there's this parser already using it incorrectly, we can treat as a bug >>in the kernel and adjust the userspace (it'd be considered a bug there >>too and backported to their earlier releases). What we don't do is >>simply merge the fix and break userspace. >Can we not repeat old arguments? No-one realised that that change >would break userspace. Or if they did, there was confusion over what >exactly had or had not been tested and was causing a problem. >Certainly it was not an intentional "merge and everyone be damned". > >My point was that there are multiple issues here. Line feeds is only >one. But using a structured file format would prevent both of the >problems we have currently hit. > >> >>Send the fix to the mesa tool if you want to change this in the kernel. >When I can finally work out how to build mesa (it seems to require >libraries that are newer than any Ubuntu release has access to!?) and https://docs.mesa3d.org/install.html has the docs for that. For ubuntu, in our internal docs we document to install deps with: sudo apt build-dep mesa You can disable stuff you don't use. Our internal docs have this useful set of args: meson setup \ -Dprefix=/usr \ -Dgallium-rusticl=false \ -Dgallium-drivers=iris \ -Dvulkan-drivers=intel \ build I think you are probably talking about the llvm dep, that can be workarounded by the setup flags above. >have spent time learning yet another code base and how the tool is >implemented... > >> >>And as I said, for this particular change it doesn't matter if it's a >>custom format, json, toml or whatever... the bug would still be the >>same. >Ideally not. Part of moving to a structured file format would be >ensuring that the structure of the data is correct. > >> >>>of the GuC CT layer. That absolutely needs to be fixed. And >>>generally, anything we can do to make the decoding more robust and >>>future proof would be a very good thing. >>> >>>Note that the devcoredump content is highly dependent upon the >>>internal workings of the driver. It is going to change over time. >>>So the more robust the decoder, the better chance it has of not >>>breaking when some new piece of data is added to the dump or an >>>existing item removed or modified. >>> >>>> >>>>>that ideally supports binary data and compression natively and >>>>>has a helper library that can be included in the kernel source >>>>>tree. That >>>> >>>>oh no, we'd need to define the schema - there are plenty of json >>>>libraries >>>>in multiple languages for users to choose from and that would >>>>be basically >>>>then main benefit of using it. >>>Well, we can certainly define extra formats on top of a base >>>format but it seems like it would be simpler if the base format >>>supported all the data types we need already. Doesn't really >>>matter either way as long as the underlying file format supports >>>all the uses we want of it. >> >>My point is that we are not going to add a decoder library that all >>userspace consumers have to use. The kernel interface is not a library. >>You are relying on having just one userspace to not break userspace. >That is not at all what I am saying. > >> >>The benefit of a common format like json, toml etc is exactly that it's >>a format already understood by hundreds of libraries and we can even do >>something like this instead of having to write our own parser: >> >>cat devcoredump | jq '.[] | .foo, .bar' >That is exactly what I am saying. > >The mesa debug tool becomes something like: > #include <libyaml> > > info = yaml.read_file(file_name); > foreach_engine(info.engines, i) > printf( "Got hang on %s\n", info.engines[i].name ); > >The external library handles all the file encoding issues. The tool >just has to put meaning to the fields returned from that library. to reiterate my point that it doesn't fix all the problems: if you move something from info.guc_ct.bla to info.contexts.bla (exactly what happened in the other bug) you may still break stuff, regardless of using a better well-known format. Lucas De Marchi > >John. > >> >>Lucas De Marchi >> >>> >>>John. >>> >>>> >>>>Lucas De Marchi >>>> >>>>>will then remove any and all confusion over interpretation of >>>>>the file forever more. But it would require updating all >>>>>userland tools to use the appropriate helper library. >>>>> >>>>>John. >>>>> >>>>>> >>>>>>Lucas De Marchi >>>>> >>> > ^ permalink raw reply [flat|nested] 22+ messages in thread
* Re: [PATCH v3 1/1] drm/xe/guc: Fix GuC log/ct output via debugfs 2025-01-09 22:43 ` Lucas De Marchi @ 2025-01-22 16:45 ` John Harrison 2025-01-22 16:59 ` Souza, Jose 0 siblings, 1 reply; 22+ messages in thread From: John Harrison @ 2025-01-22 16:45 UTC (permalink / raw) To: Lucas De Marchi Cc: Julia Filipchuk, intel-xe, José Roberto de Souza, Rodrigo Vivi On 1/9/2025 14:43, Lucas De Marchi wrote: > On Thu, Jan 09, 2025 at 12:40:51PM -0800, John Harrison wrote: >> On 1/9/2025 07:39, Lucas De Marchi wrote: >>> On Wed, Jan 08, 2025 at 03:59:58PM -0800, John Harrison wrote: >>>> On 1/8/2025 14:11, Lucas De Marchi wrote: >>>>> +Jose >>>>> +Rodrigo >>>>> >>>>> On Wed, Jan 08, 2025 at 12:14:49PM -0800, John Harrison wrote: >>>>>> On 1/7/2025 13:10, Lucas De Marchi wrote: >>>>>>> On Tue, Jan 07, 2025 at 12:22:52PM -0800, Julia Filipchuk wrote: >>>>>>>> Change to disable asci85 GuC logging only when output to >>>>>>>> devcoredump >>>>>>>> (was temporarily disabled for all code paths). >>>>>>>> >>>>>>>> v2: Ignore only for devcoredump case (not dmesg output). >>>>>>>> v3: Rebase to resolve parent tag mismatch. >>>>>>>> >>>>>>>> Signed-off-by: Julia Filipchuk <julia.filipchuk@intel.com> >>>>>>>> --- >>>>>>>> drivers/gpu/drm/xe/xe_devcoredump.c | 8 +++++--- >>>>>>>> include/drm/drm_print.h | 2 ++ >>>>>>>> 2 files changed, 7 insertions(+), 3 deletions(-) >>>>>>>> >>>>>>>> diff --git a/drivers/gpu/drm/xe/xe_devcoredump.c >>>>>>>> b/drivers/gpu/drm/xe/xe_devcoredump.c >>>>>>>> index 6980304c8903..8e5d1f9866a7 100644 >>>>>>>> --- a/drivers/gpu/drm/xe/xe_devcoredump.c >>>>>>>> +++ b/drivers/gpu/drm/xe/xe_devcoredump.c >>>>>>>> @@ -424,10 +424,12 @@ void xe_print_blob_ascii85(struct >>>>>>>> drm_printer *p, const char *prefix, >>>>>>>> * Splitting blobs across multiple lines is not compatible >>>>>>>> with the mesa >>>>>>>> * debug decoder tool. Note that even dropping the explicit >>>>>>>> '\n' below >>>>>>>> * doesn't help because the GuC log is so big some >>>>>>>> underlying implementation >>>>>>>> - * still splits the lines at 512K characters. So just bail >>>>>>>> completely for >>>>>>>> - * the moment. >>>>>>>> + * still splits the lines at 512K characters. >>>>>>> >>>>>>> did we investigate where this is done and how we can overcome it? I >>>>>> Yes. And the comment could be updated as part of this patch to >>>>>> make it clearer... >>>>>> >>>>>> >>>>>> * Splitting blobs across multiple lines is not compatible >>>>>> with the mesa >>>>>> * debug decoder tool. Note that even dropping the explicit >>>>>> line wrapping >>>>>> * below doesn't help because the GuC log can be so big it >>>>>> needs to be split >>>>>> * into multiple 2MB chunks, each of which must be printed >>>>>> individually and >>>>>> * therefore will be a separate line. >>>>> >>>>> so there's no "underlying implemenation that splits like at 512K >>>>> chars"? >>>>> Nowe it's something else: a 2MB chunk because of what? >>>> The GuC log is captured in multiple 2MB chunks because we can't >>>> kmalloc a full 16MB block at a single time irrespective of memory >>>> fragmentation - the kmalloc function aborts with a page size error >>>> above 8MB, I recall. Might even have been 4MB? The 2MB chunks >>>> become approx 512K characters of ASCII85 output (when mostly full >>>> of zeros). Because each chunk is a separate bo object the memory is >>>> not contiguous so each must be printed with a separate call to >>>> xe_print_blob_ascii85(). If xe_print_blob_ascii85() includes a >>>> terminating line feed at the end of the print then that means >>>> multiple lines for the GuC log. >>> >>> now it makes sense... and contradicts what was said earlier about the >>> "underlying implementation still splits the lines at 512K characters". >>> It's this very function that is splitting it. >> The initial comment was written before the situation was fully >> understood because it was a quick hack to get the mesa debug tool >> working again. >> >> The split is a combination of the helper function adding a linefeed >> to the end of the output and the GuC log being so large it must be >> split into multiple malloc buffers. But it is not related to the 800 >> character line wrapping within the helper's output. @Lucas, are you happy with the above now? If the patch is updated with the comment as above can we get it merged? We currently have no access to GuC logs via debugfs which makes debugging issues difficult. Multiple people have already complained about this not working. >> >>> >>>> >>>>> >>>>> I don't really want to keep updating this instead of fixing it. >>>>> >>>>>> >>>>>> The dump helper could be updated to never add any line feeds, not >>>>>> even >>>>> >>>>> when you say "dump helper", what exactly are you talking about? >>>>> xe_print_blob_ascii85(), __xe_devcoredump_read(), >>>>> __drm_puts_coredump() >>>>> or what? >>>> xe_print_blob_ascii85 >>>> >>>>> >>>>> If it's about xe_print_blob_ascii85(), I think this would be the >>>>> first step: >>>>> drop the \n you are adding. AFAICS calling the print function in >>>>> chunks >>>>> of 800B would be fine, just don't add any \n. If that still adds \n >>>>> somewhere, we can check how to drop it or you then may have a pretty >>>>> solid argument to adapt the mesa tool with a newline >>>>> continuar char and send them the MR. >>>> As above, the chunking is at the next level out. So dropping the >>>> 800 byte \n won't help with the GuC log still being split into >>>> multiple lines. You have to either move the terminating \n outside >>>> of the helper and into the callers or add a bool parameter to >>>> enable/disable it. Either of which is just messy. >>> >>> If the caller knows it's calling the function multiple times to >>> continue >>> previous data, it's not unreasonable to have an arg to terminate it or >>> not. It's for example what python does with its 'end' arg to the >>> print() >>> function. >> Just because someone else does it does not make it clean or the best >> solution. >> >>> >>>> >>>> Or extend the helper to take an array/list of pointers in a >>>> scatter/gather fashion. >>>> >>>> And if you drop the 800B \n then you break the dmesg output >>>> facility. Which means we can't get logs out from CI panic type >>>> situations. >>> >>> Or that we should have another way to get a devcoredump. I don't think >>> we are going to print the devcoredump to dmesg when the kernel panics. >>> We may print it when we fail to probe, but the cpu should still be very >>> much alive - we tie the devcoredump lifecycle to the lifecycle of the >>> device, so we don't have an opportunity to get that data. >>> >>> The workaround you add is to dump the whole thing to dmesg, but we >>> could >>> dump it somewhere else like a debugfs that is tied to the module >>> lifecycle. >> The point is to get usable logs out of CI. There are multiple >> situations in which CI fails to save logs. By 'panic' I was more >> meaning situations where we have very rare bugs that can't be hit >> locally and for which CI is not providing useful logs. I.e. we are in >> a panic about how to debug it and dumping via dmesg is the only >> viable option. >> >>> >>> The dmesg (kmsg) format already contains other things you have to >>> ignore >>> to extract the message: >>> >>> * /dev/kmsg exports the structured data in the following line >>> format: * >>> "<level>,<sequnum>,<timestamp>,<contflag>[,additional_values, ... >>> ];<message text>\n" >>> >>> so you will always have to preprocess it, ignore lines that don't >>> belong >>> to the log, etc. >> I never said this was not the case. The GuC log decoding tool already >> copes with myriad different dmesg, syslog, serial console, etc. >> output formats. >> >>> >>> And if you print it correctly, you can even make use of the LOG_CONT to >>> mark the new line as continuation of the previous one. >> Reconstructing split lines has never been a problem for GuC decoder >> tool. It is only the mesa tool that has a problem with line feeds. >> >>> >>>> >>>>>> at the end. And then the burden would be on the callers to add >>>>>> line feeds as appropriate. That seems extremely messy, though. >>>>>> And it will break the dmesg output facility. That does need the >>>>>> line wrapping at ~800 characters which can't be done from outside >>>>>> the helper. >>>>>> >>>>>>> >>>>>>> understand having to split it into multiple calls, but not >>>>>>> something >>>>>>> adding a \n. particularly for the functions dealing with >>>>>>> seq_file and >>>>>>> devcoredump. >>>>>>> >>>>>>>> + * >>>>>>>> + * Only disable from devcoredump output. >>>>>>>> */ >>>>>>>> - return; >>>>>>>> + if (p->coredump) >>>>>>> >>>>>>> but we do want the guc log to be inside the devcoredump, so >>>>>>> rather than >>>>>>> adding more workarounds, can we fix it ? >>>>>> The simplest fix is your suggestion of adding an extra white >>>>>> space character at the end of the line in the helper function and >>>>>> updating the mesa tool to support multi-line output. That seems >>>>>> like it should be a trivial update to the mesa tool and it keeps >>>>>> the KMD side simple and consistent across all potential output >>>>>> methods. But Jose seemed absolutely dead set against any updates >>>>>> to the mesa tool at all :(. >>>>>> >>>>>> The more complex fix is Joonas' idea of using an official >>>>>> structured output format of some sort - TOML, YAML, JSON or >>>>>> whatever. Something >>>>> >>>>> it actually doesn't fix this particular issue. It fixes others, >>>>> but not >>>>> this one. >>>> If we do it properly then it fixes everything. The format library >>>> would have helper functions that the devcoredump code can call to >>> >>> but we are *NOT* going to export a library for that. You are just >>> shifting the problem to "we have only one userspace that is our own >>> library, deal with it". >> No. By library, I mean libjson or libyaml or whatever. The whole >> point of using an externally defined file format is that you can use >> an externally written library to read that format. Whatever userspace >> tool only has to worry about processing data/value pairs or whatever >> you get from the library's read interface, it no longer has to worry >> about file formats, character encodings, line wraps, etc. All that is >> handled by the third party library / file format definition. >> >>> >>>> print integers, bools, strings and BLOBs. The debugfs/sysfs output >>>> would just stream the encoded output exactly as is. The dmesg >>>> output layer would add the 800 character line wrapping in a way >>>> that the dmesg decoder can undo before passing to the decoder library. >>>> >>>>> >>>>> "Guc Log": "<encoded data .........." >>>>> >>>>> if you need to split lines, you still need something to do do it in >>>>> whatever format you choose. One json I remember working on in the >>>>> past >>>>> that embeds the binary is the .apj format... example: >>>>> https://firmware.ardupilot.org/Copter/2024-12/2024-12-02-13:12/CubeBlack/arducopter.apj >>>>> >>>>> >>>>> >>>>> >>>>> { >>>>> "board_id": 9, >>>>> "magic": "APJFWv1", >>>>> "description": "Firmware for a STM32F427xx board", >>>>> "image": "eNqUvAlcU1faMH5u7k1yCQGCICCgBoIaRW0EtVSxhg ... >>>>> >>>>> here "image" is base64-encoded afair. But in your case, just >>>>> printing >>>>> the json to dmesg wouldn't work because of needing to split the line. >>>>> It wouldn't fix the kind of bugs we had in the past too: in json it >>>>> would be the equivalent of adding a field to the wrong object and >>>>> then >>>>> move it elsewhere. An application trying to read that object in the >>>>> previous place would be broken regardless. >>>>> >>>>> toml is more for configuration and yaml isn't a good one for this >>>>> case >>>>> as it further relies on indentation. I wouldn't oppose to use >>>>> json, but >>>>> don't expect to have dmesg to magically work because of that. >>>> TOML basically says 'use base64 and print it as a string'. And it >>>> supports multi-line strings, so the reader would have to drop >>>> newlines within a base64 object before doing the base64 decode. Or >>>> just use a base64 decoder that ignores whitespace. >>>> >>>> YAML seems to make even more explicit. From the 1.2.2 spec page: >>>> picture: !!binary | >>>> R0lGODlhDAAMAIQAAP//9/X >>> ^ space here for line continuation, as I mentioned. >>> >>>> 17unp5WZmZgAAAOfn515eXv >>>> Pz7Y6OjuDg4J+fn5OTk6enp >>>> 56enmleECcgggoBADs= >>>> >>>> So the userland reader just gets binary data straight out of the >>>> decoder library with no processing required. >>> >>> A decoder library that we are *NOT* going to write. >> As above, the decoder library is definitely not written by us. It is >> libyaml or some such. >> >>> >>> >>>> >>>> >>>>> >>>>> So let's fix the issue at hand and let the talk about xe's coredump >>>>> format for a later time. >>>> The issue at hand is that we have two fundamentally conflicting >>>> requirements. DMesg output requires line wrapping but the mesa tool >>>> has been coded in such a way that it breaks when given wrapped >>>> lines. There is nothing we can do about dmesg but making the mesa >>>> tool's parser more robust does not seem difficult. >>>> >>>> Switching to an externally defined encoding scheme that internally >>>> manages binary objects and supports wrapped lines would fix all >>>> issues and guarantee future compatibility. >>>> >>>> Note that line wrapping is not the only problem with the current >>>> mesa tool. Unless it has been updated since? The tool breaks if the >>>> context information is not part of the "GuC Communication >>>> Transport" section. Which is totally incorrect. Context state is >>>> very definitely not part >>> >>> We reverted it because it's not ok to just move it to the "correct" >>> place and break the users. If it's in the incorrect place and we know >>> there's this parser already using it incorrectly, we can treat as a bug >>> in the kernel and adjust the userspace (it'd be considered a bug there >>> too and backported to their earlier releases). What we don't do is >>> simply merge the fix and break userspace. >> Can we not repeat old arguments? No-one realised that that change >> would break userspace. Or if they did, there was confusion over what >> exactly had or had not been tested and was causing a problem. >> Certainly it was not an intentional "merge and everyone be damned". >> >> My point was that there are multiple issues here. Line feeds is only >> one. But using a structured file format would prevent both of the >> problems we have currently hit. >> >>> >>> Send the fix to the mesa tool if you want to change this in the kernel. >> When I can finally work out how to build mesa (it seems to require >> libraries that are newer than any Ubuntu release has access to!?) and > > https://docs.mesa3d.org/install.html has the docs for that. Pretty sure that's what I was following last time. > > For ubuntu, in our internal docs we document to install deps with: > > sudo apt build-dep mesa > > You can disable stuff you don't use. Our internal docs have this useful > set of args: > > meson setup \ > -Dprefix=/usr \ > -Dgallium-rusticl=false \ > -Dgallium-drivers=iris \ > -Dvulkan-drivers=intel \ > build > > I think you are probably talking about the llvm dep, that can be > workarounded by the setup flags above. I don't recall what the specific problem was last time. It looks like I have managed to get everything installed this time. However, the build does not appear to include the aubinator program. Nothing in src/intel/tools appears to get built at all. And I can't find any mention of how to build or use it in the Mesa docs or elsewhere. > >> have spent time learning yet another code base and how the tool is >> implemented... >> >>> >>> And as I said, for this particular change it doesn't matter if it's a >>> custom format, json, toml or whatever... the bug would still be the >>> same. >> Ideally not. Part of moving to a structured file format would be >> ensuring that the structure of the data is correct. >> >>> >>>> of the GuC CT layer. That absolutely needs to be fixed. And >>>> generally, anything we can do to make the decoding more robust and >>>> future proof would be a very good thing. >>>> >>>> Note that the devcoredump content is highly dependent upon the >>>> internal workings of the driver. It is going to change over time. >>>> So the more robust the decoder, the better chance it has of not >>>> breaking when some new piece of data is added to the dump or an >>>> existing item removed or modified. >>>> >>>>> >>>>>> that ideally supports binary data and compression natively and >>>>>> has a helper library that can be included in the kernel source >>>>>> tree. That >>>>> >>>>> oh no, we'd need to define the schema - there are plenty of json >>>>> libraries >>>>> in multiple languages for users to choose from and that would be >>>>> basically >>>>> then main benefit of using it. >>>> Well, we can certainly define extra formats on top of a base format >>>> but it seems like it would be simpler if the base format supported >>>> all the data types we need already. Doesn't really matter either >>>> way as long as the underlying file format supports all the uses we >>>> want of it. >>> >>> My point is that we are not going to add a decoder library that all >>> userspace consumers have to use. The kernel interface is not a library. >>> You are relying on having just one userspace to not break userspace. >> That is not at all what I am saying. >> >>> >>> The benefit of a common format like json, toml etc is exactly that it's >>> a format already understood by hundreds of libraries and we can even do >>> something like this instead of having to write our own parser: >>> >>> cat devcoredump | jq '.[] | .foo, .bar' >> That is exactly what I am saying. >> >> The mesa debug tool becomes something like: >> #include <libyaml> >> >> info = yaml.read_file(file_name); >> foreach_engine(info.engines, i) >> printf( "Got hang on %s\n", info.engines[i].name ); >> >> The external library handles all the file encoding issues. The tool >> just has to put meaning to the fields returned from that library. > > to reiterate my point that it doesn't fix all the problems: > > if you move something from info.guc_ct.bla to info.contexts.bla > (exactly what happened in the other bug) you may still break stuff, > regardless of using a better well-known format. But having the structure means that data will not be added to the wrong section in the first place. The problem here was that we had no structure to begin with. Then structure started to be added. But a tool was already making incorrect assumptions based on the lack of structure. Sure, when something needs to be moved, that will still cause the same kind of issue. But that is much less likely to happen if we are more careful about adding new entries within a sensible structure to begin with. John. > > Lucas De Marchi > >> >> John. >> >>> >>> Lucas De Marchi >>> >>>> >>>> John. >>>> >>>>> >>>>> Lucas De Marchi >>>>> >>>>>> will then remove any and all confusion over interpretation of the >>>>>> file forever more. But it would require updating all userland >>>>>> tools to use the appropriate helper library. >>>>>> >>>>>> John. >>>>>> >>>>>>> >>>>>>> Lucas De Marchi >>>>>> >>>> >> ^ permalink raw reply [flat|nested] 22+ messages in thread
* Re: [PATCH v3 1/1] drm/xe/guc: Fix GuC log/ct output via debugfs 2025-01-22 16:45 ` John Harrison @ 2025-01-22 16:59 ` Souza, Jose 2025-01-22 18:29 ` Souza, Jose 0 siblings, 1 reply; 22+ messages in thread From: Souza, Jose @ 2025-01-22 16:59 UTC (permalink / raw) To: Harrison, John C, De Marchi, Lucas Cc: intel-xe@lists.freedesktop.org, Vivi, Rodrigo, Filipchuk, Julia On Wed, 2025-01-22 at 08:45 -0800, John Harrison wrote: > On 1/9/2025 14:43, Lucas De Marchi wrote: > > On Thu, Jan 09, 2025 at 12:40:51PM -0800, John Harrison wrote: > > > On 1/9/2025 07:39, Lucas De Marchi wrote: > > > > On Wed, Jan 08, 2025 at 03:59:58PM -0800, John Harrison wrote: > > > > > On 1/8/2025 14:11, Lucas De Marchi wrote: > > > > > > +Jose > > > > > > +Rodrigo > > > > > > > > > > > > On Wed, Jan 08, 2025 at 12:14:49PM -0800, John Harrison wrote: > > > > > > > On 1/7/2025 13:10, Lucas De Marchi wrote: > > > > > > > > On Tue, Jan 07, 2025 at 12:22:52PM -0800, Julia Filipchuk wrote: > > > > > > > > > Change to disable asci85 GuC logging only when output to > > > > > > > > > devcoredump > > > > > > > > > (was temporarily disabled for all code paths). > > > > > > > > > > > > > > > > > > v2: Ignore only for devcoredump case (not dmesg output). > > > > > > > > > v3: Rebase to resolve parent tag mismatch. > > > > > > > > > > > > > > > > > > Signed-off-by: Julia Filipchuk <julia.filipchuk@intel.com> > > > > > > > > > --- > > > > > > > > > drivers/gpu/drm/xe/xe_devcoredump.c | 8 +++++--- > > > > > > > > > include/drm/drm_print.h | 2 ++ > > > > > > > > > 2 files changed, 7 insertions(+), 3 deletions(-) > > > > > > > > > > > > > > > > > > diff --git a/drivers/gpu/drm/xe/xe_devcoredump.c > > > > > > > > > b/drivers/gpu/drm/xe/xe_devcoredump.c > > > > > > > > > index 6980304c8903..8e5d1f9866a7 100644 > > > > > > > > > --- a/drivers/gpu/drm/xe/xe_devcoredump.c > > > > > > > > > +++ b/drivers/gpu/drm/xe/xe_devcoredump.c > > > > > > > > > @@ -424,10 +424,12 @@ void xe_print_blob_ascii85(struct > > > > > > > > > drm_printer *p, const char *prefix, > > > > > > > > > * Splitting blobs across multiple lines is not compatible > > > > > > > > > with the mesa > > > > > > > > > * debug decoder tool. Note that even dropping the explicit > > > > > > > > > '\n' below > > > > > > > > > * doesn't help because the GuC log is so big some > > > > > > > > > underlying implementation > > > > > > > > > - * still splits the lines at 512K characters. So just bail > > > > > > > > > completely for > > > > > > > > > - * the moment. > > > > > > > > > + * still splits the lines at 512K characters. > > > > > > > > > > > > > > > > did we investigate where this is done and how we can overcome it? I > > > > > > > Yes. And the comment could be updated as part of this patch to > > > > > > > make it clearer... > > > > > > > > > > > > > > > > > > > > > * Splitting blobs across multiple lines is not compatible > > > > > > > with the mesa > > > > > > > * debug decoder tool. Note that even dropping the explicit > > > > > > > line wrapping > > > > > > > * below doesn't help because the GuC log can be so big it > > > > > > > needs to be split > > > > > > > * into multiple 2MB chunks, each of which must be printed > > > > > > > individually and > > > > > > > * therefore will be a separate line. > > > > > > > > > > > > so there's no "underlying implemenation that splits like at 512K > > > > > > chars"? > > > > > > Nowe it's something else: a 2MB chunk because of what? > > > > > The GuC log is captured in multiple 2MB chunks because we can't > > > > > kmalloc a full 16MB block at a single time irrespective of memory > > > > > fragmentation - the kmalloc function aborts with a page size error > > > > > above 8MB, I recall. Might even have been 4MB? The 2MB chunks > > > > > become approx 512K characters of ASCII85 output (when mostly full > > > > > of zeros). Because each chunk is a separate bo object the memory is > > > > > not contiguous so each must be printed with a separate call to > > > > > xe_print_blob_ascii85(). If xe_print_blob_ascii85() includes a > > > > > terminating line feed at the end of the print then that means > > > > > multiple lines for the GuC log. > > > > > > > > now it makes sense... and contradicts what was said earlier about the > > > > "underlying implementation still splits the lines at 512K characters". > > > > It's this very function that is splitting it. > > > The initial comment was written before the situation was fully > > > understood because it was a quick hack to get the mesa debug tool > > > working again. > > > > > > The split is a combination of the helper function adding a linefeed > > > to the end of the output and the GuC log being so large it must be > > > split into multiple malloc buffers. But it is not related to the 800 > > > character line wrapping within the helper's output. > @Lucas, are you happy with the above now? If the patch is updated with > the comment as above can we get it merged? We currently have no access > to GuC logs via debugfs which makes debugging issues difficult. Multiple > people have already complained about this not working. > > > > > > > > > > > > > > > > > > > > > > > > > > I don't really want to keep updating this instead of fixing it. > > > > > > > > > > > > > > > > > > > > The dump helper could be updated to never add any line feeds, not > > > > > > > even > > > > > > > > > > > > when you say "dump helper", what exactly are you talking about? > > > > > > xe_print_blob_ascii85(), __xe_devcoredump_read(), > > > > > > __drm_puts_coredump() > > > > > > or what? > > > > > xe_print_blob_ascii85 > > > > > > > > > > > > > > > > > If it's about xe_print_blob_ascii85(), I think this would be the > > > > > > first step: > > > > > > drop the \n you are adding. AFAICS calling the print function in > > > > > > chunks > > > > > > of 800B would be fine, just don't add any \n. If that still adds \n > > > > > > somewhere, we can check how to drop it or you then may have a pretty > > > > > > solid argument to adapt the mesa tool with a newline > > > > > > continuar char and send them the MR. > > > > > As above, the chunking is at the next level out. So dropping the > > > > > 800 byte \n won't help with the GuC log still being split into > > > > > multiple lines. You have to either move the terminating \n outside > > > > > of the helper and into the callers or add a bool parameter to > > > > > enable/disable it. Either of which is just messy. > > > > > > > > If the caller knows it's calling the function multiple times to > > > > continue > > > > previous data, it's not unreasonable to have an arg to terminate it or > > > > not. It's for example what python does with its 'end' arg to the > > > > print() > > > > function. > > > Just because someone else does it does not make it clean or the best > > > solution. > > > > > > > > > > > > > > > > > Or extend the helper to take an array/list of pointers in a > > > > > scatter/gather fashion. > > > > > > > > > > And if you drop the 800B \n then you break the dmesg output > > > > > facility. Which means we can't get logs out from CI panic type > > > > > situations. > > > > > > > > Or that we should have another way to get a devcoredump. I don't think > > > > we are going to print the devcoredump to dmesg when the kernel panics. > > > > We may print it when we fail to probe, but the cpu should still be very > > > > much alive - we tie the devcoredump lifecycle to the lifecycle of the > > > > device, so we don't have an opportunity to get that data. > > > > > > > > The workaround you add is to dump the whole thing to dmesg, but we > > > > could > > > > dump it somewhere else like a debugfs that is tied to the module > > > > lifecycle. > > > The point is to get usable logs out of CI. There are multiple > > > situations in which CI fails to save logs. By 'panic' I was more > > > meaning situations where we have very rare bugs that can't be hit > > > locally and for which CI is not providing useful logs. I.e. we are in > > > a panic about how to debug it and dumping via dmesg is the only > > > viable option. > > > > > > > > > > > The dmesg (kmsg) format already contains other things you have to > > > > ignore > > > > to extract the message: > > > > > > > > * /dev/kmsg exports the structured data in the following line > > > > format: * > > > > "<level>,<sequnum>,<timestamp>,<contflag>[,additional_values, ... > > > > ];<message text>\n" > > > > > > > > so you will always have to preprocess it, ignore lines that don't > > > > belong > > > > to the log, etc. > > > I never said this was not the case. The GuC log decoding tool already > > > copes with myriad different dmesg, syslog, serial console, etc. > > > output formats. > > > > > > > > > > > And if you print it correctly, you can even make use of the LOG_CONT to > > > > mark the new line as continuation of the previous one. > > > Reconstructing split lines has never been a problem for GuC decoder > > > tool. It is only the mesa tool that has a problem with line feeds. > > > > > > > > > > > > > > > > > > > at the end. And then the burden would be on the callers to add > > > > > > > line feeds as appropriate. That seems extremely messy, though. > > > > > > > And it will break the dmesg output facility. That does need the > > > > > > > line wrapping at ~800 characters which can't be done from outside > > > > > > > the helper. > > > > > > > > > > > > > > > > > > > > > > > understand having to split it into multiple calls, but not > > > > > > > > something > > > > > > > > adding a \n. particularly for the functions dealing with > > > > > > > > seq_file and > > > > > > > > devcoredump. > > > > > > > > > > > > > > > > > + * > > > > > > > > > + * Only disable from devcoredump output. > > > > > > > > > */ > > > > > > > > > - return; > > > > > > > > > + if (p->coredump) > > > > > > > > > > > > > > > > but we do want the guc log to be inside the devcoredump, so > > > > > > > > rather than > > > > > > > > adding more workarounds, can we fix it ? > > > > > > > The simplest fix is your suggestion of adding an extra white > > > > > > > space character at the end of the line in the helper function and > > > > > > > updating the mesa tool to support multi-line output. That seems > > > > > > > like it should be a trivial update to the mesa tool and it keeps > > > > > > > the KMD side simple and consistent across all potential output > > > > > > > methods. But Jose seemed absolutely dead set against any updates > > > > > > > to the mesa tool at all :(. > > > > > > > > > > > > > > The more complex fix is Joonas' idea of using an official > > > > > > > structured output format of some sort - TOML, YAML, JSON or > > > > > > > whatever. Something > > > > > > > > > > > > it actually doesn't fix this particular issue. It fixes others, > > > > > > but not > > > > > > this one. > > > > > If we do it properly then it fixes everything. The format library > > > > > would have helper functions that the devcoredump code can call to > > > > > > > > but we are *NOT* going to export a library for that. You are just > > > > shifting the problem to "we have only one userspace that is our own > > > > library, deal with it". > > > No. By library, I mean libjson or libyaml or whatever. The whole > > > point of using an externally defined file format is that you can use > > > an externally written library to read that format. Whatever userspace > > > tool only has to worry about processing data/value pairs or whatever > > > you get from the library's read interface, it no longer has to worry > > > about file formats, character encodings, line wraps, etc. All that is > > > handled by the third party library / file format definition. > > > > > > > > > > > > print integers, bools, strings and BLOBs. The debugfs/sysfs output > > > > > would just stream the encoded output exactly as is. The dmesg > > > > > output layer would add the 800 character line wrapping in a way > > > > > that the dmesg decoder can undo before passing to the decoder library. > > > > > > > > > > > > > > > > > "Guc Log": "<encoded data .........." > > > > > > > > > > > > if you need to split lines, you still need something to do do it in > > > > > > whatever format you choose. One json I remember working on in the > > > > > > past > > > > > > that embeds the binary is the .apj format... example: > > > > > > https://firmware.ardupilot.org/Copter/2024-12/2024-12-02-13:12/CubeBlack/arducopter.apj > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > { > > > > > > "board_id": 9, > > > > > > "magic": "APJFWv1", > > > > > > "description": "Firmware for a STM32F427xx board", > > > > > > "image": "eNqUvAlcU1faMH5u7k1yCQGCICCgBoIaRW0EtVSxhg ... > > > > > > > > > > > > here "image" is base64-encoded afair. But in your case, just > > > > > > printing > > > > > > the json to dmesg wouldn't work because of needing to split the line. > > > > > > It wouldn't fix the kind of bugs we had in the past too: in json it > > > > > > would be the equivalent of adding a field to the wrong object and > > > > > > then > > > > > > move it elsewhere. An application trying to read that object in the > > > > > > previous place would be broken regardless. > > > > > > > > > > > > toml is more for configuration and yaml isn't a good one for this > > > > > > case > > > > > > as it further relies on indentation. I wouldn't oppose to use > > > > > > json, but > > > > > > don't expect to have dmesg to magically work because of that. > > > > > TOML basically says 'use base64 and print it as a string'. And it > > > > > supports multi-line strings, so the reader would have to drop > > > > > newlines within a base64 object before doing the base64 decode. Or > > > > > just use a base64 decoder that ignores whitespace. > > > > > > > > > > YAML seems to make even more explicit. From the 1.2.2 spec page: > > > > > picture: !!binary | > > > > > R0lGODlhDAAMAIQAAP//9/X > > > > ^ space here for line continuation, as I mentioned. > > > > > > > > > 17unp5WZmZgAAAOfn515eXv > > > > > Pz7Y6OjuDg4J+fn5OTk6enp > > > > > 56enmleECcgggoBADs= > > > > > > > > > > So the userland reader just gets binary data straight out of the > > > > > decoder library with no processing required. > > > > > > > > A decoder library that we are *NOT* going to write. > > > As above, the decoder library is definitely not written by us. It is > > > libyaml or some such. > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > So let's fix the issue at hand and let the talk about xe's coredump > > > > > > format for a later time. > > > > > The issue at hand is that we have two fundamentally conflicting > > > > > requirements. DMesg output requires line wrapping but the mesa tool > > > > > has been coded in such a way that it breaks when given wrapped > > > > > lines. There is nothing we can do about dmesg but making the mesa > > > > > tool's parser more robust does not seem difficult. > > > > > > > > > > Switching to an externally defined encoding scheme that internally > > > > > manages binary objects and supports wrapped lines would fix all > > > > > issues and guarantee future compatibility. > > > > > > > > > > Note that line wrapping is not the only problem with the current > > > > > mesa tool. Unless it has been updated since? The tool breaks if the > > > > > context information is not part of the "GuC Communication > > > > > Transport" section. Which is totally incorrect. Context state is > > > > > very definitely not part > > > > > > > > We reverted it because it's not ok to just move it to the "correct" > > > > place and break the users. If it's in the incorrect place and we know > > > > there's this parser already using it incorrectly, we can treat as a bug > > > > in the kernel and adjust the userspace (it'd be considered a bug there > > > > too and backported to their earlier releases). What we don't do is > > > > simply merge the fix and break userspace. > > > Can we not repeat old arguments? No-one realised that that change > > > would break userspace. Or if they did, there was confusion over what > > > exactly had or had not been tested and was causing a problem. > > > Certainly it was not an intentional "merge and everyone be damned". > > > > > > My point was that there are multiple issues here. Line feeds is only > > > one. But using a structured file format would prevent both of the > > > problems we have currently hit. > > > > > > > > > > > Send the fix to the mesa tool if you want to change this in the kernel. > > > When I can finally work out how to build mesa (it seems to require > > > libraries that are newer than any Ubuntu release has access to!?) and > > > > https://docs.mesa3d.org/install.html has the docs for that. > Pretty sure that's what I was following last time. > > > > > For ubuntu, in our internal docs we document to install deps with: > > > > sudo apt build-dep mesa > > > > You can disable stuff you don't use. Our internal docs have this useful > > set of args: > > > > meson setup \ > > -Dprefix=/usr \ > > -Dgallium-rusticl=false \ > > -Dgallium-drivers=iris \ > > -Dvulkan-drivers=intel \ > > build > > > > I think you are probably talking about the llvm dep, that can be > > workarounded by the setup flags above. > I don't recall what the specific problem was last time. It looks like I > have managed to get everything installed this time. However, the build > does not appear to include the aubinator program. Nothing in > src/intel/tools appears to get built at all. And I can't find any > mention of how to build or use it in the Mesa docs or elsewhere. Add -Dtools=intel to build it. > > > > > > > have spent time learning yet another code base and how the tool is > > > implemented... > > > > > > > > > > > And as I said, for this particular change it doesn't matter if it's a > > > > custom format, json, toml or whatever... the bug would still be the > > > > same. > > > Ideally not. Part of moving to a structured file format would be > > > ensuring that the structure of the data is correct. > > > > > > > > > > > > of the GuC CT layer. That absolutely needs to be fixed. And > > > > > generally, anything we can do to make the decoding more robust and > > > > > future proof would be a very good thing. > > > > > > > > > > Note that the devcoredump content is highly dependent upon the > > > > > internal workings of the driver. It is going to change over time. > > > > > So the more robust the decoder, the better chance it has of not > > > > > breaking when some new piece of data is added to the dump or an > > > > > existing item removed or modified. > > > > > > > > > > > > > > > > > > that ideally supports binary data and compression natively and > > > > > > > has a helper library that can be included in the kernel source > > > > > > > tree. That > > > > > > > > > > > > oh no, we'd need to define the schema - there are plenty of json > > > > > > libraries > > > > > > in multiple languages for users to choose from and that would be > > > > > > basically > > > > > > then main benefit of using it. > > > > > Well, we can certainly define extra formats on top of a base format > > > > > but it seems like it would be simpler if the base format supported > > > > > all the data types we need already. Doesn't really matter either > > > > > way as long as the underlying file format supports all the uses we > > > > > want of it. > > > > > > > > My point is that we are not going to add a decoder library that all > > > > userspace consumers have to use. The kernel interface is not a library. > > > > You are relying on having just one userspace to not break userspace. > > > That is not at all what I am saying. > > > > > > > > > > > The benefit of a common format like json, toml etc is exactly that it's > > > > a format already understood by hundreds of libraries and we can even do > > > > something like this instead of having to write our own parser: > > > > > > > > cat devcoredump | jq '.[] | .foo, .bar' > > > That is exactly what I am saying. > > > > > > The mesa debug tool becomes something like: > > > #include <libyaml> > > > > > > info = yaml.read_file(file_name); > > > foreach_engine(info.engines, i) > > > printf( "Got hang on %s\n", info.engines[i].name ); > > > > > > The external library handles all the file encoding issues. The tool > > > just has to put meaning to the fields returned from that library. > > > > to reiterate my point that it doesn't fix all the problems: > > > > if you move something from info.guc_ct.bla to info.contexts.bla > > (exactly what happened in the other bug) you may still break stuff, > > regardless of using a better well-known format. > But having the structure means that data will not be added to the wrong > section in the first place. > > The problem here was that we had no structure to begin with. Then > structure started to be added. But a tool was already making incorrect > assumptions based on the lack of structure. > > Sure, when something needs to be moved, that will still cause the same > kind of issue. But that is much less likely to happen if we are more > careful about adding new entries within a sensible structure to begin with. > > John. > > > > > Lucas De Marchi > > > > > > > > John. > > > > > > > > > > > Lucas De Marchi > > > > > > > > > > > > > > John. > > > > > > > > > > > > > > > > > Lucas De Marchi > > > > > > > > > > > > > will then remove any and all confusion over interpretation of the > > > > > > > file forever more. But it would require updating all userland > > > > > > > tools to use the appropriate helper library. > > > > > > > > > > > > > > John. > > > > > > > > > > > > > > > > > > > > > > > Lucas De Marchi > > > > > > > > > > > > > > > > ^ permalink raw reply [flat|nested] 22+ messages in thread
* Re: [PATCH v3 1/1] drm/xe/guc: Fix GuC log/ct output via debugfs 2025-01-22 16:59 ` Souza, Jose @ 2025-01-22 18:29 ` Souza, Jose 2025-01-22 21:09 ` John Harrison 0 siblings, 1 reply; 22+ messages in thread From: Souza, Jose @ 2025-01-22 18:29 UTC (permalink / raw) To: Harrison, John C, De Marchi, Lucas Cc: intel-xe@lists.freedesktop.org, Vivi, Rodrigo, Filipchuk, Julia On Wed, 2025-01-22 at 08:59 -0800, José Roberto de Souza wrote: > On Wed, 2025-01-22 at 08:45 -0800, John Harrison wrote: > > On 1/9/2025 14:43, Lucas De Marchi wrote: > > > On Thu, Jan 09, 2025 at 12:40:51PM -0800, John Harrison wrote: > > > > On 1/9/2025 07:39, Lucas De Marchi wrote: > > > > > On Wed, Jan 08, 2025 at 03:59:58PM -0800, John Harrison wrote: > > > > > > On 1/8/2025 14:11, Lucas De Marchi wrote: > > > > > > > +Jose > > > > > > > +Rodrigo > > > > > > > > > > > > > > On Wed, Jan 08, 2025 at 12:14:49PM -0800, John Harrison wrote: > > > > > > > > On 1/7/2025 13:10, Lucas De Marchi wrote: > > > > > > > > > On Tue, Jan 07, 2025 at 12:22:52PM -0800, Julia Filipchuk wrote: > > > > > > > > > > Change to disable asci85 GuC logging only when output to > > > > > > > > > > devcoredump > > > > > > > > > > (was temporarily disabled for all code paths). > > > > > > > > > > > > > > > > > > > > v2: Ignore only for devcoredump case (not dmesg output). > > > > > > > > > > v3: Rebase to resolve parent tag mismatch. > > > > > > > > > > > > > > > > > > > > Signed-off-by: Julia Filipchuk <julia.filipchuk@intel.com> > > > > > > > > > > --- > > > > > > > > > > drivers/gpu/drm/xe/xe_devcoredump.c | 8 +++++--- > > > > > > > > > > include/drm/drm_print.h | 2 ++ > > > > > > > > > > 2 files changed, 7 insertions(+), 3 deletions(-) > > > > > > > > > > > > > > > > > > > > diff --git a/drivers/gpu/drm/xe/xe_devcoredump.c > > > > > > > > > > b/drivers/gpu/drm/xe/xe_devcoredump.c > > > > > > > > > > index 6980304c8903..8e5d1f9866a7 100644 > > > > > > > > > > --- a/drivers/gpu/drm/xe/xe_devcoredump.c > > > > > > > > > > +++ b/drivers/gpu/drm/xe/xe_devcoredump.c > > > > > > > > > > @@ -424,10 +424,12 @@ void xe_print_blob_ascii85(struct > > > > > > > > > > drm_printer *p, const char *prefix, > > > > > > > > > > * Splitting blobs across multiple lines is not compatible > > > > > > > > > > with the mesa > > > > > > > > > > * debug decoder tool. Note that even dropping the explicit > > > > > > > > > > '\n' below > > > > > > > > > > * doesn't help because the GuC log is so big some > > > > > > > > > > underlying implementation > > > > > > > > > > - * still splits the lines at 512K characters. So just bail > > > > > > > > > > completely for > > > > > > > > > > - * the moment. > > > > > > > > > > + * still splits the lines at 512K characters. > > > > > > > > > > > > > > > > > > did we investigate where this is done and how we can overcome it? I > > > > > > > > Yes. And the comment could be updated as part of this patch to > > > > > > > > make it clearer... > > > > > > > > > > > > > > > > > > > > > > > > * Splitting blobs across multiple lines is not compatible > > > > > > > > with the mesa > > > > > > > > * debug decoder tool. Note that even dropping the explicit > > > > > > > > line wrapping > > > > > > > > * below doesn't help because the GuC log can be so big it > > > > > > > > needs to be split > > > > > > > > * into multiple 2MB chunks, each of which must be printed > > > > > > > > individually and > > > > > > > > * therefore will be a separate line. > > > > > > > > > > > > > > so there's no "underlying implemenation that splits like at 512K > > > > > > > chars"? > > > > > > > Nowe it's something else: a 2MB chunk because of what? > > > > > > The GuC log is captured in multiple 2MB chunks because we can't > > > > > > kmalloc a full 16MB block at a single time irrespective of memory > > > > > > fragmentation - the kmalloc function aborts with a page size error > > > > > > above 8MB, I recall. Might even have been 4MB? The 2MB chunks > > > > > > become approx 512K characters of ASCII85 output (when mostly full > > > > > > of zeros). Because each chunk is a separate bo object the memory is > > > > > > not contiguous so each must be printed with a separate call to > > > > > > xe_print_blob_ascii85(). If xe_print_blob_ascii85() includes a > > > > > > terminating line feed at the end of the print then that means > > > > > > multiple lines for the GuC log. > > > > > > > > > > now it makes sense... and contradicts what was said earlier about the > > > > > "underlying implementation still splits the lines at 512K characters". > > > > > It's this very function that is splitting it. > > > > The initial comment was written before the situation was fully > > > > understood because it was a quick hack to get the mesa debug tool > > > > working again. > > > > > > > > The split is a combination of the helper function adding a linefeed > > > > to the end of the output and the GuC log being so large it must be > > > > split into multiple malloc buffers. But it is not related to the 800 > > > > character line wrapping within the helper's output. > > @Lucas, are you happy with the above now? If the patch is updated with > > the comment as above can we get it merged? We currently have no access > > to GuC logs via debugfs which makes debugging issues difficult. Multiple > > people have already complained about this not working. I thought it was agreed that the line break were not necessary and was being added because of the way GuC log output code was written, so why it is still being used? In my opinion this patch is changing a struct that is used by all drm drivers, not sure if we can change without an ack from a drm maintainer. Also would be nice if GuC log follow the same pattern as other binaries in devcoredump like: [HWCTX].length: 0x1000 [HWCTX].data: xxxxx [200000].length: 0x40000 [200000].data: xxxxx And again we should avoid break the Mesa parser as much as possible, customers open bugs and attach it. And soon the same devcoredump will be used to replay the batch buffer and all the context that cause the GPU hang in simulator and real HW. > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > I don't really want to keep updating this instead of fixing it. > > > > > > > > > > > > > > > > > > > > > > > The dump helper could be updated to never add any line feeds, not > > > > > > > > even > > > > > > > > > > > > > > when you say "dump helper", what exactly are you talking about? > > > > > > > xe_print_blob_ascii85(), __xe_devcoredump_read(), > > > > > > > __drm_puts_coredump() > > > > > > > or what? > > > > > > xe_print_blob_ascii85 > > > > > > > > > > > > > > > > > > > > If it's about xe_print_blob_ascii85(), I think this would be the > > > > > > > first step: > > > > > > > drop the \n you are adding. AFAICS calling the print function in > > > > > > > chunks > > > > > > > of 800B would be fine, just don't add any \n. If that still adds \n > > > > > > > somewhere, we can check how to drop it or you then may have a pretty > > > > > > > solid argument to adapt the mesa tool with a newline > > > > > > > continuar char and send them the MR. > > > > > > As above, the chunking is at the next level out. So dropping the > > > > > > 800 byte \n won't help with the GuC log still being split into > > > > > > multiple lines. You have to either move the terminating \n outside > > > > > > of the helper and into the callers or add a bool parameter to > > > > > > enable/disable it. Either of which is just messy. > > > > > > > > > > If the caller knows it's calling the function multiple times to > > > > > continue > > > > > previous data, it's not unreasonable to have an arg to terminate it or > > > > > not. It's for example what python does with its 'end' arg to the > > > > > print() > > > > > function. > > > > Just because someone else does it does not make it clean or the best > > > > solution. > > > > > > > > > > > > > > > > > > > > > Or extend the helper to take an array/list of pointers in a > > > > > > scatter/gather fashion. > > > > > > > > > > > > And if you drop the 800B \n then you break the dmesg output > > > > > > facility. Which means we can't get logs out from CI panic type > > > > > > situations. > > > > > > > > > > Or that we should have another way to get a devcoredump. I don't think > > > > > we are going to print the devcoredump to dmesg when the kernel panics. > > > > > We may print it when we fail to probe, but the cpu should still be very > > > > > much alive - we tie the devcoredump lifecycle to the lifecycle of the > > > > > device, so we don't have an opportunity to get that data. > > > > > > > > > > The workaround you add is to dump the whole thing to dmesg, but we > > > > > could > > > > > dump it somewhere else like a debugfs that is tied to the module > > > > > lifecycle. > > > > The point is to get usable logs out of CI. There are multiple > > > > situations in which CI fails to save logs. By 'panic' I was more > > > > meaning situations where we have very rare bugs that can't be hit > > > > locally and for which CI is not providing useful logs. I.e. we are in > > > > a panic about how to debug it and dumping via dmesg is the only > > > > viable option. > > > > > > > > > > > > > > The dmesg (kmsg) format already contains other things you have to > > > > > ignore > > > > > to extract the message: > > > > > > > > > > * /dev/kmsg exports the structured data in the following line > > > > > format: * > > > > > "<level>,<sequnum>,<timestamp>,<contflag>[,additional_values, ... > > > > > ];<message text>\n" > > > > > > > > > > so you will always have to preprocess it, ignore lines that don't > > > > > belong > > > > > to the log, etc. > > > > I never said this was not the case. The GuC log decoding tool already > > > > copes with myriad different dmesg, syslog, serial console, etc. > > > > output formats. > > > > > > > > > > > > > > And if you print it correctly, you can even make use of the LOG_CONT to > > > > > mark the new line as continuation of the previous one. > > > > Reconstructing split lines has never been a problem for GuC decoder > > > > tool. It is only the mesa tool that has a problem with line feeds. > > > > > > > > > > > > > > > > > > > > > > > at the end. And then the burden would be on the callers to add > > > > > > > > line feeds as appropriate. That seems extremely messy, though. > > > > > > > > And it will break the dmesg output facility. That does need the > > > > > > > > line wrapping at ~800 characters which can't be done from outside > > > > > > > > the helper. > > > > > > > > > > > > > > > > > > > > > > > > > > understand having to split it into multiple calls, but not > > > > > > > > > something > > > > > > > > > adding a \n. particularly for the functions dealing with > > > > > > > > > seq_file and > > > > > > > > > devcoredump. > > > > > > > > > > > > > > > > > > > + * > > > > > > > > > > + * Only disable from devcoredump output. > > > > > > > > > > */ > > > > > > > > > > - return; > > > > > > > > > > + if (p->coredump) > > > > > > > > > > > > > > > > > > but we do want the guc log to be inside the devcoredump, so > > > > > > > > > rather than > > > > > > > > > adding more workarounds, can we fix it ? > > > > > > > > The simplest fix is your suggestion of adding an extra white > > > > > > > > space character at the end of the line in the helper function and > > > > > > > > updating the mesa tool to support multi-line output. That seems > > > > > > > > like it should be a trivial update to the mesa tool and it keeps > > > > > > > > the KMD side simple and consistent across all potential output > > > > > > > > methods. But Jose seemed absolutely dead set against any updates > > > > > > > > to the mesa tool at all :(. > > > > > > > > > > > > > > > > The more complex fix is Joonas' idea of using an official > > > > > > > > structured output format of some sort - TOML, YAML, JSON or > > > > > > > > whatever. Something > > > > > > > > > > > > > > it actually doesn't fix this particular issue. It fixes others, > > > > > > > but not > > > > > > > this one. > > > > > > If we do it properly then it fixes everything. The format library > > > > > > would have helper functions that the devcoredump code can call to > > > > > > > > > > but we are *NOT* going to export a library for that. You are just > > > > > shifting the problem to "we have only one userspace that is our own > > > > > library, deal with it". > > > > No. By library, I mean libjson or libyaml or whatever. The whole > > > > point of using an externally defined file format is that you can use > > > > an externally written library to read that format. Whatever userspace > > > > tool only has to worry about processing data/value pairs or whatever > > > > you get from the library's read interface, it no longer has to worry > > > > about file formats, character encodings, line wraps, etc. All that is > > > > handled by the third party library / file format definition. > > > > > > > > > > > > > > > print integers, bools, strings and BLOBs. The debugfs/sysfs output > > > > > > would just stream the encoded output exactly as is. The dmesg > > > > > > output layer would add the 800 character line wrapping in a way > > > > > > that the dmesg decoder can undo before passing to the decoder library. > > > > > > > > > > > > > > > > > > > > "Guc Log": "<encoded data .........." > > > > > > > > > > > > > > if you need to split lines, you still need something to do do it in > > > > > > > whatever format you choose. One json I remember working on in the > > > > > > > past > > > > > > > that embeds the binary is the .apj format... example: > > > > > > > https://firmware.ardupilot.org/Copter/2024-12/2024-12-02-13:12/CubeBlack/arducopter.apj > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > { > > > > > > > "board_id": 9, > > > > > > > "magic": "APJFWv1", > > > > > > > "description": "Firmware for a STM32F427xx board", > > > > > > > "image": "eNqUvAlcU1faMH5u7k1yCQGCICCgBoIaRW0EtVSxhg ... > > > > > > > > > > > > > > here "image" is base64-encoded afair. But in your case, just > > > > > > > printing > > > > > > > the json to dmesg wouldn't work because of needing to split the line. > > > > > > > It wouldn't fix the kind of bugs we had in the past too: in json it > > > > > > > would be the equivalent of adding a field to the wrong object and > > > > > > > then > > > > > > > move it elsewhere. An application trying to read that object in the > > > > > > > previous place would be broken regardless. > > > > > > > > > > > > > > toml is more for configuration and yaml isn't a good one for this > > > > > > > case > > > > > > > as it further relies on indentation. I wouldn't oppose to use > > > > > > > json, but > > > > > > > don't expect to have dmesg to magically work because of that. > > > > > > TOML basically says 'use base64 and print it as a string'. And it > > > > > > supports multi-line strings, so the reader would have to drop > > > > > > newlines within a base64 object before doing the base64 decode. Or > > > > > > just use a base64 decoder that ignores whitespace. > > > > > > > > > > > > YAML seems to make even more explicit. From the 1.2.2 spec page: > > > > > > picture: !!binary | > > > > > > R0lGODlhDAAMAIQAAP//9/X > > > > > ^ space here for line continuation, as I mentioned. > > > > > > > > > > > 17unp5WZmZgAAAOfn515eXv > > > > > > Pz7Y6OjuDg4J+fn5OTk6enp > > > > > > 56enmleECcgggoBADs= > > > > > > > > > > > > So the userland reader just gets binary data straight out of the > > > > > > decoder library with no processing required. > > > > > > > > > > A decoder library that we are *NOT* going to write. > > > > As above, the decoder library is definitely not written by us. It is > > > > libyaml or some such. > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > So let's fix the issue at hand and let the talk about xe's coredump > > > > > > > format for a later time. > > > > > > The issue at hand is that we have two fundamentally conflicting > > > > > > requirements. DMesg output requires line wrapping but the mesa tool > > > > > > has been coded in such a way that it breaks when given wrapped > > > > > > lines. There is nothing we can do about dmesg but making the mesa > > > > > > tool's parser more robust does not seem difficult. > > > > > > > > > > > > Switching to an externally defined encoding scheme that internally > > > > > > manages binary objects and supports wrapped lines would fix all > > > > > > issues and guarantee future compatibility. > > > > > > > > > > > > Note that line wrapping is not the only problem with the current > > > > > > mesa tool. Unless it has been updated since? The tool breaks if the > > > > > > context information is not part of the "GuC Communication > > > > > > Transport" section. Which is totally incorrect. Context state is > > > > > > very definitely not part > > > > > > > > > > We reverted it because it's not ok to just move it to the "correct" > > > > > place and break the users. If it's in the incorrect place and we know > > > > > there's this parser already using it incorrectly, we can treat as a bug > > > > > in the kernel and adjust the userspace (it'd be considered a bug there > > > > > too and backported to their earlier releases). What we don't do is > > > > > simply merge the fix and break userspace. > > > > Can we not repeat old arguments? No-one realised that that change > > > > would break userspace. Or if they did, there was confusion over what > > > > exactly had or had not been tested and was causing a problem. > > > > Certainly it was not an intentional "merge and everyone be damned". > > > > > > > > My point was that there are multiple issues here. Line feeds is only > > > > one. But using a structured file format would prevent both of the > > > > problems we have currently hit. > > > > > > > > > > > > > > Send the fix to the mesa tool if you want to change this in the kernel. > > > > When I can finally work out how to build mesa (it seems to require > > > > libraries that are newer than any Ubuntu release has access to!?) and > > > > > > https://docs.mesa3d.org/install.html has the docs for that. > > Pretty sure that's what I was following last time. > > > > > > > > For ubuntu, in our internal docs we document to install deps with: > > > > > > sudo apt build-dep mesa > > > > > > You can disable stuff you don't use. Our internal docs have this useful > > > set of args: > > > > > > meson setup \ > > > -Dprefix=/usr \ > > > -Dgallium-rusticl=false \ > > > -Dgallium-drivers=iris \ > > > -Dvulkan-drivers=intel \ > > > build > > > > > > I think you are probably talking about the llvm dep, that can be > > > workarounded by the setup flags above. > > I don't recall what the specific problem was last time. It looks like I > > have managed to get everything installed this time. However, the build > > does not appear to include the aubinator program. Nothing in > > src/intel/tools appears to get built at all. And I can't find any > > mention of how to build or use it in the Mesa docs or elsewhere. > > Add -Dtools=intel to build it. > > > > > > > > > > > > have spent time learning yet another code base and how the tool is > > > > implemented... > > > > > > > > > > > > > > And as I said, for this particular change it doesn't matter if it's a > > > > > custom format, json, toml or whatever... the bug would still be the > > > > > same. > > > > Ideally not. Part of moving to a structured file format would be > > > > ensuring that the structure of the data is correct. > > > > > > > > > > > > > > > of the GuC CT layer. That absolutely needs to be fixed. And > > > > > > generally, anything we can do to make the decoding more robust and > > > > > > future proof would be a very good thing. > > > > > > > > > > > > Note that the devcoredump content is highly dependent upon the > > > > > > internal workings of the driver. It is going to change over time. > > > > > > So the more robust the decoder, the better chance it has of not > > > > > > breaking when some new piece of data is added to the dump or an > > > > > > existing item removed or modified. > > > > > > > > > > > > > > > > > > > > > that ideally supports binary data and compression natively and > > > > > > > > has a helper library that can be included in the kernel source > > > > > > > > tree. That > > > > > > > > > > > > > > oh no, we'd need to define the schema - there are plenty of json > > > > > > > libraries > > > > > > > in multiple languages for users to choose from and that would be > > > > > > > basically > > > > > > > then main benefit of using it. > > > > > > Well, we can certainly define extra formats on top of a base format > > > > > > but it seems like it would be simpler if the base format supported > > > > > > all the data types we need already. Doesn't really matter either > > > > > > way as long as the underlying file format supports all the uses we > > > > > > want of it. > > > > > > > > > > My point is that we are not going to add a decoder library that all > > > > > userspace consumers have to use. The kernel interface is not a library. > > > > > You are relying on having just one userspace to not break userspace. > > > > That is not at all what I am saying. > > > > > > > > > > > > > > The benefit of a common format like json, toml etc is exactly that it's > > > > > a format already understood by hundreds of libraries and we can even do > > > > > something like this instead of having to write our own parser: > > > > > > > > > > cat devcoredump | jq '.[] | .foo, .bar' > > > > That is exactly what I am saying. > > > > > > > > The mesa debug tool becomes something like: > > > > #include <libyaml> > > > > > > > > info = yaml.read_file(file_name); > > > > foreach_engine(info.engines, i) > > > > printf( "Got hang on %s\n", info.engines[i].name ); > > > > > > > > The external library handles all the file encoding issues. The tool > > > > just has to put meaning to the fields returned from that library. > > > > > > to reiterate my point that it doesn't fix all the problems: > > > > > > if you move something from info.guc_ct.bla to info.contexts.bla > > > (exactly what happened in the other bug) you may still break stuff, > > > regardless of using a better well-known format. > > But having the structure means that data will not be added to the wrong > > section in the first place. > > > > The problem here was that we had no structure to begin with. Then > > structure started to be added. But a tool was already making incorrect > > assumptions based on the lack of structure. > > > > Sure, when something needs to be moved, that will still cause the same > > kind of issue. But that is much less likely to happen if we are more > > careful about adding new entries within a sensible structure to begin with. > > > > John. > > > > > > > > Lucas De Marchi > > > > > > > > > > > John. > > > > > > > > > > > > > > Lucas De Marchi > > > > > > > > > > > > > > > > > John. > > > > > > > > > > > > > > > > > > > > Lucas De Marchi > > > > > > > > > > > > > > > will then remove any and all confusion over interpretation of the > > > > > > > > file forever more. But it would require updating all userland > > > > > > > > tools to use the appropriate helper library. > > > > > > > > > > > > > > > > John. > > > > > > > > > > > > > > > > > > > > > > > > > > Lucas De Marchi > > > > > > > > > > > > > > > > > > > > > ^ permalink raw reply [flat|nested] 22+ messages in thread
* Re: [PATCH v3 1/1] drm/xe/guc: Fix GuC log/ct output via debugfs 2025-01-22 18:29 ` Souza, Jose @ 2025-01-22 21:09 ` John Harrison 2025-01-23 14:02 ` Souza, Jose 0 siblings, 1 reply; 22+ messages in thread From: John Harrison @ 2025-01-22 21:09 UTC (permalink / raw) To: Souza, Jose, De Marchi, Lucas Cc: intel-xe@lists.freedesktop.org, Vivi, Rodrigo, Filipchuk, Julia On 1/22/2025 10:29, Souza, Jose wrote: > On Wed, 2025-01-22 at 08:59 -0800, José Roberto de Souza wrote: >> On Wed, 2025-01-22 at 08:45 -0800, John Harrison wrote: >>> On 1/9/2025 14:43, Lucas De Marchi wrote: >>>> On Thu, Jan 09, 2025 at 12:40:51PM -0800, John Harrison wrote: >>>>> On 1/9/2025 07:39, Lucas De Marchi wrote: >>>>>> On Wed, Jan 08, 2025 at 03:59:58PM -0800, John Harrison wrote: >>>>>>> On 1/8/2025 14:11, Lucas De Marchi wrote: >>>>>>>> +Jose >>>>>>>> +Rodrigo >>>>>>>> >>>>>>>> On Wed, Jan 08, 2025 at 12:14:49PM -0800, John Harrison wrote: >>>>>>>>> On 1/7/2025 13:10, Lucas De Marchi wrote: >>>>>>>>>> On Tue, Jan 07, 2025 at 12:22:52PM -0800, Julia Filipchuk wrote: >>>>>>>>>>> Change to disable asci85 GuC logging only when output to >>>>>>>>>>> devcoredump >>>>>>>>>>> (was temporarily disabled for all code paths). >>>>>>>>>>> >>>>>>>>>>> v2: Ignore only for devcoredump case (not dmesg output). >>>>>>>>>>> v3: Rebase to resolve parent tag mismatch. >>>>>>>>>>> >>>>>>>>>>> Signed-off-by: Julia Filipchuk <julia.filipchuk@intel.com> >>>>>>>>>>> --- >>>>>>>>>>> drivers/gpu/drm/xe/xe_devcoredump.c | 8 +++++--- >>>>>>>>>>> include/drm/drm_print.h | 2 ++ >>>>>>>>>>> 2 files changed, 7 insertions(+), 3 deletions(-) >>>>>>>>>>> >>>>>>>>>>> diff --git a/drivers/gpu/drm/xe/xe_devcoredump.c >>>>>>>>>>> b/drivers/gpu/drm/xe/xe_devcoredump.c >>>>>>>>>>> index 6980304c8903..8e5d1f9866a7 100644 >>>>>>>>>>> --- a/drivers/gpu/drm/xe/xe_devcoredump.c >>>>>>>>>>> +++ b/drivers/gpu/drm/xe/xe_devcoredump.c >>>>>>>>>>> @@ -424,10 +424,12 @@ void xe_print_blob_ascii85(struct >>>>>>>>>>> drm_printer *p, const char *prefix, >>>>>>>>>>> * Splitting blobs across multiple lines is not compatible >>>>>>>>>>> with the mesa >>>>>>>>>>> * debug decoder tool. Note that even dropping the explicit >>>>>>>>>>> '\n' below >>>>>>>>>>> * doesn't help because the GuC log is so big some >>>>>>>>>>> underlying implementation >>>>>>>>>>> - * still splits the lines at 512K characters. So just bail >>>>>>>>>>> completely for >>>>>>>>>>> - * the moment. >>>>>>>>>>> + * still splits the lines at 512K characters. >>>>>>>>>> did we investigate where this is done and how we can overcome it? I >>>>>>>>> Yes. And the comment could be updated as part of this patch to >>>>>>>>> make it clearer... >>>>>>>>> >>>>>>>>> >>>>>>>>> * Splitting blobs across multiple lines is not compatible >>>>>>>>> with the mesa >>>>>>>>> * debug decoder tool. Note that even dropping the explicit >>>>>>>>> line wrapping >>>>>>>>> * below doesn't help because the GuC log can be so big it >>>>>>>>> needs to be split >>>>>>>>> * into multiple 2MB chunks, each of which must be printed >>>>>>>>> individually and >>>>>>>>> * therefore will be a separate line. >>>>>>>> so there's no "underlying implemenation that splits like at 512K >>>>>>>> chars"? >>>>>>>> Nowe it's something else: a 2MB chunk because of what? >>>>>>> The GuC log is captured in multiple 2MB chunks because we can't >>>>>>> kmalloc a full 16MB block at a single time irrespective of memory >>>>>>> fragmentation - the kmalloc function aborts with a page size error >>>>>>> above 8MB, I recall. Might even have been 4MB? The 2MB chunks >>>>>>> become approx 512K characters of ASCII85 output (when mostly full >>>>>>> of zeros). Because each chunk is a separate bo object the memory is >>>>>>> not contiguous so each must be printed with a separate call to >>>>>>> xe_print_blob_ascii85(). If xe_print_blob_ascii85() includes a >>>>>>> terminating line feed at the end of the print then that means >>>>>>> multiple lines for the GuC log. >>>>>> now it makes sense... and contradicts what was said earlier about the >>>>>> "underlying implementation still splits the lines at 512K characters". >>>>>> It's this very function that is splitting it. >>>>> The initial comment was written before the situation was fully >>>>> understood because it was a quick hack to get the mesa debug tool >>>>> working again. >>>>> >>>>> The split is a combination of the helper function adding a linefeed >>>>> to the end of the output and the GuC log being so large it must be >>>>> split into multiple malloc buffers. But it is not related to the 800 >>>>> character line wrapping within the helper's output. >>> @Lucas, are you happy with the above now? If the patch is updated with >>> the comment as above can we get it merged? We currently have no access >>> to GuC logs via debugfs which makes debugging issues difficult. Multiple >>> people have already complained about this not working. > > I thought it was agreed that the line break were not necessary and was being added because of the way GuC log output code was written, so why it is > still being used? As per earlier comments, removing the line breaks requires doing hacky things and/or having messy interfaces in the kernel. Being understood is not the same thing as saying removing it is the perfect solution. Whereas supporting wrapped lines is defensive programming. It makes the tool more robust for when core dump files arrive from random end users that have passed them through who knows what text editor or email tool. > > In my opinion this patch is changing a struct that is used by all drm drivers, not sure if we can change without an ack from a drm maintainer. > > Also would be nice if GuC log follow the same pattern as other binaries in devcoredump like: > > > [HWCTX].length: 0x1000 > [HWCTX].data: xxxxx > > [200000].length: 0x40000 > [200000].data: xxxxx I'm not seeing how that helps. The size above is the decoded size. That does not tell you anything about the amount of ASCII85 data because the encoding is variable length. The ASCII85 spec includes basic run length encoding of zero filled data. So the amount of ASCII data is not a simple function of the input buffer size. > > And again we should avoid break the Mesa parser as much as possible, customers open bugs and attach it. And soon the same devcoredump will be used to > replay the batch buffer and all the context that cause the GPU hang in simulator and real HW. Avoiding breaks is not the same thing as not allowing improvements. > >>> >>>>>>>> I don't really want to keep updating this instead of fixing it. >>>>>>>> >>>>>>>>> The dump helper could be updated to never add any line feeds, not >>>>>>>>> even >>>>>>>> when you say "dump helper", what exactly are you talking about? >>>>>>>> xe_print_blob_ascii85(), __xe_devcoredump_read(), >>>>>>>> __drm_puts_coredump() >>>>>>>> or what? >>>>>>> xe_print_blob_ascii85 >>>>>>> >>>>>>>> If it's about xe_print_blob_ascii85(), I think this would be the >>>>>>>> first step: >>>>>>>> drop the \n you are adding. AFAICS calling the print function in >>>>>>>> chunks >>>>>>>> of 800B would be fine, just don't add any \n. If that still adds \n >>>>>>>> somewhere, we can check how to drop it or you then may have a pretty >>>>>>>> solid argument to adapt the mesa tool with a newline >>>>>>>> continuar char and send them the MR. >>>>>>> As above, the chunking is at the next level out. So dropping the >>>>>>> 800 byte \n won't help with the GuC log still being split into >>>>>>> multiple lines. You have to either move the terminating \n outside >>>>>>> of the helper and into the callers or add a bool parameter to >>>>>>> enable/disable it. Either of which is just messy. >>>>>> If the caller knows it's calling the function multiple times to >>>>>> continue >>>>>> previous data, it's not unreasonable to have an arg to terminate it or >>>>>> not. It's for example what python does with its 'end' arg to the >>>>>> print() >>>>>> function. >>>>> Just because someone else does it does not make it clean or the best >>>>> solution. >>>>> >>>>>>> Or extend the helper to take an array/list of pointers in a >>>>>>> scatter/gather fashion. >>>>>>> >>>>>>> And if you drop the 800B \n then you break the dmesg output >>>>>>> facility. Which means we can't get logs out from CI panic type >>>>>>> situations. >>>>>> Or that we should have another way to get a devcoredump. I don't think >>>>>> we are going to print the devcoredump to dmesg when the kernel panics. >>>>>> We may print it when we fail to probe, but the cpu should still be very >>>>>> much alive - we tie the devcoredump lifecycle to the lifecycle of the >>>>>> device, so we don't have an opportunity to get that data. >>>>>> >>>>>> The workaround you add is to dump the whole thing to dmesg, but we >>>>>> could >>>>>> dump it somewhere else like a debugfs that is tied to the module >>>>>> lifecycle. >>>>> The point is to get usable logs out of CI. There are multiple >>>>> situations in which CI fails to save logs. By 'panic' I was more >>>>> meaning situations where we have very rare bugs that can't be hit >>>>> locally and for which CI is not providing useful logs. I.e. we are in >>>>> a panic about how to debug it and dumping via dmesg is the only >>>>> viable option. >>>>> >>>>>> The dmesg (kmsg) format already contains other things you have to >>>>>> ignore >>>>>> to extract the message: >>>>>> >>>>>> * /dev/kmsg exports the structured data in the following line >>>>>> format: * >>>>>> "<level>,<sequnum>,<timestamp>,<contflag>[,additional_values, ... >>>>>> ];<message text>\n" >>>>>> >>>>>> so you will always have to preprocess it, ignore lines that don't >>>>>> belong >>>>>> to the log, etc. >>>>> I never said this was not the case. The GuC log decoding tool already >>>>> copes with myriad different dmesg, syslog, serial console, etc. >>>>> output formats. >>>>> >>>>>> And if you print it correctly, you can even make use of the LOG_CONT to >>>>>> mark the new line as continuation of the previous one. >>>>> Reconstructing split lines has never been a problem for GuC decoder >>>>> tool. It is only the mesa tool that has a problem with line feeds. >>>>> >>>>>>>>> at the end. And then the burden would be on the callers to add >>>>>>>>> line feeds as appropriate. That seems extremely messy, though. >>>>>>>>> And it will break the dmesg output facility. That does need the >>>>>>>>> line wrapping at ~800 characters which can't be done from outside >>>>>>>>> the helper. >>>>>>>>> >>>>>>>>>> understand having to split it into multiple calls, but not >>>>>>>>>> something >>>>>>>>>> adding a \n. particularly for the functions dealing with >>>>>>>>>> seq_file and >>>>>>>>>> devcoredump. >>>>>>>>>> >>>>>>>>>>> + * >>>>>>>>>>> + * Only disable from devcoredump output. >>>>>>>>>>> */ >>>>>>>>>>> - return; >>>>>>>>>>> + if (p->coredump) >>>>>>>>>> but we do want the guc log to be inside the devcoredump, so >>>>>>>>>> rather than >>>>>>>>>> adding more workarounds, can we fix it ? >>>>>>>>> The simplest fix is your suggestion of adding an extra white >>>>>>>>> space character at the end of the line in the helper function and >>>>>>>>> updating the mesa tool to support multi-line output. That seems >>>>>>>>> like it should be a trivial update to the mesa tool and it keeps >>>>>>>>> the KMD side simple and consistent across all potential output >>>>>>>>> methods. But Jose seemed absolutely dead set against any updates >>>>>>>>> to the mesa tool at all :(. >>>>>>>>> >>>>>>>>> The more complex fix is Joonas' idea of using an official >>>>>>>>> structured output format of some sort - TOML, YAML, JSON or >>>>>>>>> whatever. Something >>>>>>>> it actually doesn't fix this particular issue. It fixes others, >>>>>>>> but not >>>>>>>> this one. >>>>>>> If we do it properly then it fixes everything. The format library >>>>>>> would have helper functions that the devcoredump code can call to >>>>>> but we are *NOT* going to export a library for that. You are just >>>>>> shifting the problem to "we have only one userspace that is our own >>>>>> library, deal with it". >>>>> No. By library, I mean libjson or libyaml or whatever. The whole >>>>> point of using an externally defined file format is that you can use >>>>> an externally written library to read that format. Whatever userspace >>>>> tool only has to worry about processing data/value pairs or whatever >>>>> you get from the library's read interface, it no longer has to worry >>>>> about file formats, character encodings, line wraps, etc. All that is >>>>> handled by the third party library / file format definition. >>>>> >>>>>>> print integers, bools, strings and BLOBs. The debugfs/sysfs output >>>>>>> would just stream the encoded output exactly as is. The dmesg >>>>>>> output layer would add the 800 character line wrapping in a way >>>>>>> that the dmesg decoder can undo before passing to the decoder library. >>>>>>> >>>>>>>> "Guc Log": "<encoded data .........." >>>>>>>> >>>>>>>> if you need to split lines, you still need something to do do it in >>>>>>>> whatever format you choose. One json I remember working on in the >>>>>>>> past >>>>>>>> that embeds the binary is the .apj format... example: >>>>>>>> https://firmware.ardupilot.org/Copter/2024-12/2024-12-02-13:12/CubeBlack/arducopter.apj >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> { >>>>>>>> "board_id": 9, >>>>>>>> "magic": "APJFWv1", >>>>>>>> "description": "Firmware for a STM32F427xx board", >>>>>>>> "image": "eNqUvAlcU1faMH5u7k1yCQGCICCgBoIaRW0EtVSxhg ... >>>>>>>> >>>>>>>> here "image" is base64-encoded afair. But in your case, just >>>>>>>> printing >>>>>>>> the json to dmesg wouldn't work because of needing to split the line. >>>>>>>> It wouldn't fix the kind of bugs we had in the past too: in json it >>>>>>>> would be the equivalent of adding a field to the wrong object and >>>>>>>> then >>>>>>>> move it elsewhere. An application trying to read that object in the >>>>>>>> previous place would be broken regardless. >>>>>>>> >>>>>>>> toml is more for configuration and yaml isn't a good one for this >>>>>>>> case >>>>>>>> as it further relies on indentation. I wouldn't oppose to use >>>>>>>> json, but >>>>>>>> don't expect to have dmesg to magically work because of that. >>>>>>> TOML basically says 'use base64 and print it as a string'. And it >>>>>>> supports multi-line strings, so the reader would have to drop >>>>>>> newlines within a base64 object before doing the base64 decode. Or >>>>>>> just use a base64 decoder that ignores whitespace. >>>>>>> >>>>>>> YAML seems to make even more explicit. From the 1.2.2 spec page: >>>>>>> picture: !!binary | >>>>>>> R0lGODlhDAAMAIQAAP//9/X >>>>>> ^ space here for line continuation, as I mentioned. >>>>>> >>>>>>> 17unp5WZmZgAAAOfn515eXv >>>>>>> Pz7Y6OjuDg4J+fn5OTk6enp >>>>>>> 56enmleECcgggoBADs= >>>>>>> >>>>>>> So the userland reader just gets binary data straight out of the >>>>>>> decoder library with no processing required. >>>>>> A decoder library that we are *NOT* going to write. >>>>> As above, the decoder library is definitely not written by us. It is >>>>> libyaml or some such. >>>>> >>>>>> >>>>>>> >>>>>>>> So let's fix the issue at hand and let the talk about xe's coredump >>>>>>>> format for a later time. >>>>>>> The issue at hand is that we have two fundamentally conflicting >>>>>>> requirements. DMesg output requires line wrapping but the mesa tool >>>>>>> has been coded in such a way that it breaks when given wrapped >>>>>>> lines. There is nothing we can do about dmesg but making the mesa >>>>>>> tool's parser more robust does not seem difficult. >>>>>>> >>>>>>> Switching to an externally defined encoding scheme that internally >>>>>>> manages binary objects and supports wrapped lines would fix all >>>>>>> issues and guarantee future compatibility. >>>>>>> >>>>>>> Note that line wrapping is not the only problem with the current >>>>>>> mesa tool. Unless it has been updated since? The tool breaks if the >>>>>>> context information is not part of the "GuC Communication >>>>>>> Transport" section. Which is totally incorrect. Context state is >>>>>>> very definitely not part >>>>>> We reverted it because it's not ok to just move it to the "correct" >>>>>> place and break the users. If it's in the incorrect place and we know >>>>>> there's this parser already using it incorrectly, we can treat as a bug >>>>>> in the kernel and adjust the userspace (it'd be considered a bug there >>>>>> too and backported to their earlier releases). What we don't do is >>>>>> simply merge the fix and break userspace. >>>>> Can we not repeat old arguments? No-one realised that that change >>>>> would break userspace. Or if they did, there was confusion over what >>>>> exactly had or had not been tested and was causing a problem. >>>>> Certainly it was not an intentional "merge and everyone be damned". >>>>> >>>>> My point was that there are multiple issues here. Line feeds is only >>>>> one. But using a structured file format would prevent both of the >>>>> problems we have currently hit. >>>>> >>>>>> Send the fix to the mesa tool if you want to change this in the kernel. >>>>> When I can finally work out how to build mesa (it seems to require >>>>> libraries that are newer than any Ubuntu release has access to!?) and >>>> https://docs.mesa3d.org/install.html has the docs for that. >>> Pretty sure that's what I was following last time. >>> >>>> For ubuntu, in our internal docs we document to install deps with: >>>> >>>> sudo apt build-dep mesa >>>> >>>> You can disable stuff you don't use. Our internal docs have this useful >>>> set of args: >>>> >>>> meson setup \ >>>> -Dprefix=/usr \ >>>> -Dgallium-rusticl=false \ >>>> -Dgallium-drivers=iris \ >>>> -Dvulkan-drivers=intel \ >>>> build >>>> >>>> I think you are probably talking about the llvm dep, that can be >>>> workarounded by the setup flags above. >>> I don't recall what the specific problem was last time. It looks like I >>> have managed to get everything installed this time. However, the build >>> does not appear to include the aubinator program. Nothing in >>> src/intel/tools appears to get built at all. And I can't find any >>> mention of how to build or use it in the Mesa docs or elsewhere. >> Add -Dtools=intel to build it. And how does one use it? Are there any regression tests that one can run to verify operation? John. >> >>> >>>>> have spent time learning yet another code base and how the tool is >>>>> implemented... >>>>> >>>>>> And as I said, for this particular change it doesn't matter if it's a >>>>>> custom format, json, toml or whatever... the bug would still be the >>>>>> same. >>>>> Ideally not. Part of moving to a structured file format would be >>>>> ensuring that the structure of the data is correct. >>>>> >>>>>>> of the GuC CT layer. That absolutely needs to be fixed. And >>>>>>> generally, anything we can do to make the decoding more robust and >>>>>>> future proof would be a very good thing. >>>>>>> >>>>>>> Note that the devcoredump content is highly dependent upon the >>>>>>> internal workings of the driver. It is going to change over time. >>>>>>> So the more robust the decoder, the better chance it has of not >>>>>>> breaking when some new piece of data is added to the dump or an >>>>>>> existing item removed or modified. >>>>>>> >>>>>>>>> that ideally supports binary data and compression natively and >>>>>>>>> has a helper library that can be included in the kernel source >>>>>>>>> tree. That >>>>>>>> oh no, we'd need to define the schema - there are plenty of json >>>>>>>> libraries >>>>>>>> in multiple languages for users to choose from and that would be >>>>>>>> basically >>>>>>>> then main benefit of using it. >>>>>>> Well, we can certainly define extra formats on top of a base format >>>>>>> but it seems like it would be simpler if the base format supported >>>>>>> all the data types we need already. Doesn't really matter either >>>>>>> way as long as the underlying file format supports all the uses we >>>>>>> want of it. >>>>>> My point is that we are not going to add a decoder library that all >>>>>> userspace consumers have to use. The kernel interface is not a library. >>>>>> You are relying on having just one userspace to not break userspace. >>>>> That is not at all what I am saying. >>>>> >>>>>> The benefit of a common format like json, toml etc is exactly that it's >>>>>> a format already understood by hundreds of libraries and we can even do >>>>>> something like this instead of having to write our own parser: >>>>>> >>>>>> cat devcoredump | jq '.[] | .foo, .bar' >>>>> That is exactly what I am saying. >>>>> >>>>> The mesa debug tool becomes something like: >>>>> #include <libyaml> >>>>> >>>>> info = yaml.read_file(file_name); >>>>> foreach_engine(info.engines, i) >>>>> printf( "Got hang on %s\n", info.engines[i].name ); >>>>> >>>>> The external library handles all the file encoding issues. The tool >>>>> just has to put meaning to the fields returned from that library. >>>> to reiterate my point that it doesn't fix all the problems: >>>> >>>> if you move something from info.guc_ct.bla to info.contexts.bla >>>> (exactly what happened in the other bug) you may still break stuff, >>>> regardless of using a better well-known format. >>> But having the structure means that data will not be added to the wrong >>> section in the first place. >>> >>> The problem here was that we had no structure to begin with. Then >>> structure started to be added. But a tool was already making incorrect >>> assumptions based on the lack of structure. >>> >>> Sure, when something needs to be moved, that will still cause the same >>> kind of issue. But that is much less likely to happen if we are more >>> careful about adding new entries within a sensible structure to begin with. >>> >>> John. >>> >>>> Lucas De Marchi >>>> >>>>> John. >>>>> >>>>>> Lucas De Marchi >>>>>> >>>>>>> John. >>>>>>> >>>>>>>> Lucas De Marchi >>>>>>>> >>>>>>>>> will then remove any and all confusion over interpretation of the >>>>>>>>> file forever more. But it would require updating all userland >>>>>>>>> tools to use the appropriate helper library. >>>>>>>>> >>>>>>>>> John. >>>>>>>>> >>>>>>>>>> Lucas De Marchi ^ permalink raw reply [flat|nested] 22+ messages in thread
* Re: [PATCH v3 1/1] drm/xe/guc: Fix GuC log/ct output via debugfs 2025-01-22 21:09 ` John Harrison @ 2025-01-23 14:02 ` Souza, Jose 2025-01-23 14:21 ` Lucas De Marchi 0 siblings, 1 reply; 22+ messages in thread From: Souza, Jose @ 2025-01-23 14:02 UTC (permalink / raw) To: Harrison, John C, De Marchi, Lucas Cc: intel-xe@lists.freedesktop.org, Vivi, Rodrigo, Filipchuk, Julia On Wed, 2025-01-22 at 13:09 -0800, John Harrison wrote: > On 1/22/2025 10:29, Souza, Jose wrote: > > On Wed, 2025-01-22 at 08:59 -0800, José Roberto de Souza wrote: > > > On Wed, 2025-01-22 at 08:45 -0800, John Harrison wrote: > > > > On 1/9/2025 14:43, Lucas De Marchi wrote: > > > > > On Thu, Jan 09, 2025 at 12:40:51PM -0800, John Harrison wrote: > > > > > > On 1/9/2025 07:39, Lucas De Marchi wrote: > > > > > > > On Wed, Jan 08, 2025 at 03:59:58PM -0800, John Harrison wrote: > > > > > > > > On 1/8/2025 14:11, Lucas De Marchi wrote: > > > > > > > > > +Jose > > > > > > > > > +Rodrigo > > > > > > > > > > > > > > > > > > On Wed, Jan 08, 2025 at 12:14:49PM -0800, John Harrison wrote: > > > > > > > > > > On 1/7/2025 13:10, Lucas De Marchi wrote: > > > > > > > > > > > On Tue, Jan 07, 2025 at 12:22:52PM -0800, Julia Filipchuk wrote: > > > > > > > > > > > > Change to disable asci85 GuC logging only when output to > > > > > > > > > > > > devcoredump > > > > > > > > > > > > (was temporarily disabled for all code paths). > > > > > > > > > > > > > > > > > > > > > > > > v2: Ignore only for devcoredump case (not dmesg output). > > > > > > > > > > > > v3: Rebase to resolve parent tag mismatch. > > > > > > > > > > > > > > > > > > > > > > > > Signed-off-by: Julia Filipchuk <julia.filipchuk@intel.com> > > > > > > > > > > > > --- > > > > > > > > > > > > drivers/gpu/drm/xe/xe_devcoredump.c | 8 +++++--- > > > > > > > > > > > > include/drm/drm_print.h | 2 ++ > > > > > > > > > > > > 2 files changed, 7 insertions(+), 3 deletions(-) > > > > > > > > > > > > > > > > > > > > > > > > diff --git a/drivers/gpu/drm/xe/xe_devcoredump.c > > > > > > > > > > > > b/drivers/gpu/drm/xe/xe_devcoredump.c > > > > > > > > > > > > index 6980304c8903..8e5d1f9866a7 100644 > > > > > > > > > > > > --- a/drivers/gpu/drm/xe/xe_devcoredump.c > > > > > > > > > > > > +++ b/drivers/gpu/drm/xe/xe_devcoredump.c > > > > > > > > > > > > @@ -424,10 +424,12 @@ void xe_print_blob_ascii85(struct > > > > > > > > > > > > drm_printer *p, const char *prefix, > > > > > > > > > > > > * Splitting blobs across multiple lines is not compatible > > > > > > > > > > > > with the mesa > > > > > > > > > > > > * debug decoder tool. Note that even dropping the explicit > > > > > > > > > > > > '\n' below > > > > > > > > > > > > * doesn't help because the GuC log is so big some > > > > > > > > > > > > underlying implementation > > > > > > > > > > > > - * still splits the lines at 512K characters. So just bail > > > > > > > > > > > > completely for > > > > > > > > > > > > - * the moment. > > > > > > > > > > > > + * still splits the lines at 512K characters. > > > > > > > > > > > did we investigate where this is done and how we can overcome it? I > > > > > > > > > > Yes. And the comment could be updated as part of this patch to > > > > > > > > > > make it clearer... > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > * Splitting blobs across multiple lines is not compatible > > > > > > > > > > with the mesa > > > > > > > > > > * debug decoder tool. Note that even dropping the explicit > > > > > > > > > > line wrapping > > > > > > > > > > * below doesn't help because the GuC log can be so big it > > > > > > > > > > needs to be split > > > > > > > > > > * into multiple 2MB chunks, each of which must be printed > > > > > > > > > > individually and > > > > > > > > > > * therefore will be a separate line. > > > > > > > > > so there's no "underlying implemenation that splits like at 512K > > > > > > > > > chars"? > > > > > > > > > Nowe it's something else: a 2MB chunk because of what? > > > > > > > > The GuC log is captured in multiple 2MB chunks because we can't > > > > > > > > kmalloc a full 16MB block at a single time irrespective of memory > > > > > > > > fragmentation - the kmalloc function aborts with a page size error > > > > > > > > above 8MB, I recall. Might even have been 4MB? The 2MB chunks > > > > > > > > become approx 512K characters of ASCII85 output (when mostly full > > > > > > > > of zeros). Because each chunk is a separate bo object the memory is > > > > > > > > not contiguous so each must be printed with a separate call to > > > > > > > > xe_print_blob_ascii85(). If xe_print_blob_ascii85() includes a > > > > > > > > terminating line feed at the end of the print then that means > > > > > > > > multiple lines for the GuC log. > > > > > > > now it makes sense... and contradicts what was said earlier about the > > > > > > > "underlying implementation still splits the lines at 512K characters". > > > > > > > It's this very function that is splitting it. > > > > > > The initial comment was written before the situation was fully > > > > > > understood because it was a quick hack to get the mesa debug tool > > > > > > working again. > > > > > > > > > > > > The split is a combination of the helper function adding a linefeed > > > > > > to the end of the output and the GuC log being so large it must be > > > > > > split into multiple malloc buffers. But it is not related to the 800 > > > > > > character line wrapping within the helper's output. > > > > @Lucas, are you happy with the above now? If the patch is updated with > > > > the comment as above can we get it merged? We currently have no access > > > > to GuC logs via debugfs which makes debugging issues difficult. Multiple > > > > people have already complained about this not working. > > > > I thought it was agreed that the line break were not necessary and was being added because of the way GuC log output code was written, so why it is > > still being used? > As per earlier comments, removing the line breaks requires doing hacky > things and/or having messy interfaces in the kernel. Being understood is > not the same thing as saying removing it is the perfect solution. we have years of i915 having no line breaks and no issues. > > Whereas supporting wrapped lines is defensive programming. It makes the > tool more robust for when core dump files arrive from random end users > that have passed them through who knows what text editor or email tool. > it should be shared compressed or decoded(with mesa or other too). > > > > > In my opinion this patch is changing a struct that is used by all drm drivers, not sure if we can change without an ack from a drm maintainer. > > > > Also would be nice if GuC log follow the same pattern as other binaries in devcoredump like: > > > > > > [HWCTX].length: 0x1000 > > [HWCTX].data: xxxxx > > > > [200000].length: 0x40000 > > [200000].data: xxxxx > I'm not seeing how that helps. First consistency, second we can re-use the same code that parses other binaries to parse this one too. > > The size above is the decoded size. That does not tell you anything > about the amount of ASCII85 data because the encoding is variable > length. The ASCII85 spec includes basic run length encoding of zero > filled data. So the amount of ASCII data is not a simple function of the > input buffer size. At least for the other binaries I need to know the whole binary size, allocate the memory, then I will start to decode and store that in the allocated memory. Then at last I can check if the number of bytes decoded match with length, to make sure nothing was lost. > > > > > And again we should avoid break the Mesa parser as much as possible, customers open bugs and attach it. And soon the same devcoredump will be used to > > replay the batch buffer and all the context that cause the GPU hang in simulator and real HW. > Avoiding breaks is not the same thing as not allowing improvements. > > > > > > > > > > > > > > > > I don't really want to keep updating this instead of fixing it. > > > > > > > > > > > > > > > > > > > The dump helper could be updated to never add any line feeds, not > > > > > > > > > > even > > > > > > > > > when you say "dump helper", what exactly are you talking about? > > > > > > > > > xe_print_blob_ascii85(), __xe_devcoredump_read(), > > > > > > > > > __drm_puts_coredump() > > > > > > > > > or what? > > > > > > > > xe_print_blob_ascii85 > > > > > > > > > > > > > > > > > If it's about xe_print_blob_ascii85(), I think this would be the > > > > > > > > > first step: > > > > > > > > > drop the \n you are adding. AFAICS calling the print function in > > > > > > > > > chunks > > > > > > > > > of 800B would be fine, just don't add any \n. If that still adds \n > > > > > > > > > somewhere, we can check how to drop it or you then may have a pretty > > > > > > > > > solid argument to adapt the mesa tool with a newline > > > > > > > > > continuar char and send them the MR. > > > > > > > > As above, the chunking is at the next level out. So dropping the > > > > > > > > 800 byte \n won't help with the GuC log still being split into > > > > > > > > multiple lines. You have to either move the terminating \n outside > > > > > > > > of the helper and into the callers or add a bool parameter to > > > > > > > > enable/disable it. Either of which is just messy. > > > > > > > If the caller knows it's calling the function multiple times to > > > > > > > continue > > > > > > > previous data, it's not unreasonable to have an arg to terminate it or > > > > > > > not. It's for example what python does with its 'end' arg to the > > > > > > > print() > > > > > > > function. > > > > > > Just because someone else does it does not make it clean or the best > > > > > > solution. > > > > > > > > > > > > > > Or extend the helper to take an array/list of pointers in a > > > > > > > > scatter/gather fashion. > > > > > > > > > > > > > > > > And if you drop the 800B \n then you break the dmesg output > > > > > > > > facility. Which means we can't get logs out from CI panic type > > > > > > > > situations. > > > > > > > Or that we should have another way to get a devcoredump. I don't think > > > > > > > we are going to print the devcoredump to dmesg when the kernel panics. > > > > > > > We may print it when we fail to probe, but the cpu should still be very > > > > > > > much alive - we tie the devcoredump lifecycle to the lifecycle of the > > > > > > > device, so we don't have an opportunity to get that data. > > > > > > > > > > > > > > The workaround you add is to dump the whole thing to dmesg, but we > > > > > > > could > > > > > > > dump it somewhere else like a debugfs that is tied to the module > > > > > > > lifecycle. > > > > > > The point is to get usable logs out of CI. There are multiple > > > > > > situations in which CI fails to save logs. By 'panic' I was more > > > > > > meaning situations where we have very rare bugs that can't be hit > > > > > > locally and for which CI is not providing useful logs. I.e. we are in > > > > > > a panic about how to debug it and dumping via dmesg is the only > > > > > > viable option. > > > > > > > > > > > > > The dmesg (kmsg) format already contains other things you have to > > > > > > > ignore > > > > > > > to extract the message: > > > > > > > > > > > > > > * /dev/kmsg exports the structured data in the following line > > > > > > > format: * > > > > > > > "<level>,<sequnum>,<timestamp>,<contflag>[,additional_values, ... > > > > > > > ];<message text>\n" > > > > > > > > > > > > > > so you will always have to preprocess it, ignore lines that don't > > > > > > > belong > > > > > > > to the log, etc. > > > > > > I never said this was not the case. The GuC log decoding tool already > > > > > > copes with myriad different dmesg, syslog, serial console, etc. > > > > > > output formats. > > > > > > > > > > > > > And if you print it correctly, you can even make use of the LOG_CONT to > > > > > > > mark the new line as continuation of the previous one. > > > > > > Reconstructing split lines has never been a problem for GuC decoder > > > > > > tool. It is only the mesa tool that has a problem with line feeds. > > > > > > > > > > > > > > > > at the end. And then the burden would be on the callers to add > > > > > > > > > > line feeds as appropriate. That seems extremely messy, though. > > > > > > > > > > And it will break the dmesg output facility. That does need the > > > > > > > > > > line wrapping at ~800 characters which can't be done from outside > > > > > > > > > > the helper. > > > > > > > > > > > > > > > > > > > > > understand having to split it into multiple calls, but not > > > > > > > > > > > something > > > > > > > > > > > adding a \n. particularly for the functions dealing with > > > > > > > > > > > seq_file and > > > > > > > > > > > devcoredump. > > > > > > > > > > > > > > > > > > > > > > > + * > > > > > > > > > > > > + * Only disable from devcoredump output. > > > > > > > > > > > > */ > > > > > > > > > > > > - return; > > > > > > > > > > > > + if (p->coredump) > > > > > > > > > > > but we do want the guc log to be inside the devcoredump, so > > > > > > > > > > > rather than > > > > > > > > > > > adding more workarounds, can we fix it ? > > > > > > > > > > The simplest fix is your suggestion of adding an extra white > > > > > > > > > > space character at the end of the line in the helper function and > > > > > > > > > > updating the mesa tool to support multi-line output. That seems > > > > > > > > > > like it should be a trivial update to the mesa tool and it keeps > > > > > > > > > > the KMD side simple and consistent across all potential output > > > > > > > > > > methods. But Jose seemed absolutely dead set against any updates > > > > > > > > > > to the mesa tool at all :(. > > > > > > > > > > > > > > > > > > > > The more complex fix is Joonas' idea of using an official > > > > > > > > > > structured output format of some sort - TOML, YAML, JSON or > > > > > > > > > > whatever. Something > > > > > > > > > it actually doesn't fix this particular issue. It fixes others, > > > > > > > > > but not > > > > > > > > > this one. > > > > > > > > If we do it properly then it fixes everything. The format library > > > > > > > > would have helper functions that the devcoredump code can call to > > > > > > > but we are *NOT* going to export a library for that. You are just > > > > > > > shifting the problem to "we have only one userspace that is our own > > > > > > > library, deal with it". > > > > > > No. By library, I mean libjson or libyaml or whatever. The whole > > > > > > point of using an externally defined file format is that you can use > > > > > > an externally written library to read that format. Whatever userspace > > > > > > tool only has to worry about processing data/value pairs or whatever > > > > > > you get from the library's read interface, it no longer has to worry > > > > > > about file formats, character encodings, line wraps, etc. All that is > > > > > > handled by the third party library / file format definition. > > > > > > > > > > > > > > print integers, bools, strings and BLOBs. The debugfs/sysfs output > > > > > > > > would just stream the encoded output exactly as is. The dmesg > > > > > > > > output layer would add the 800 character line wrapping in a way > > > > > > > > that the dmesg decoder can undo before passing to the decoder library. > > > > > > > > > > > > > > > > > "Guc Log": "<encoded data .........." > > > > > > > > > > > > > > > > > > if you need to split lines, you still need something to do do it in > > > > > > > > > whatever format you choose. One json I remember working on in the > > > > > > > > > past > > > > > > > > > that embeds the binary is the .apj format... example: > > > > > > > > > https://firmware.ardupilot.org/Copter/2024-12/2024-12-02-13:12/CubeBlack/arducopter.apj > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > { > > > > > > > > > "board_id": 9, > > > > > > > > > "magic": "APJFWv1", > > > > > > > > > "description": "Firmware for a STM32F427xx board", > > > > > > > > > "image": "eNqUvAlcU1faMH5u7k1yCQGCICCgBoIaRW0EtVSxhg ... > > > > > > > > > > > > > > > > > > here "image" is base64-encoded afair. But in your case, just > > > > > > > > > printing > > > > > > > > > the json to dmesg wouldn't work because of needing to split the line. > > > > > > > > > It wouldn't fix the kind of bugs we had in the past too: in json it > > > > > > > > > would be the equivalent of adding a field to the wrong object and > > > > > > > > > then > > > > > > > > > move it elsewhere. An application trying to read that object in the > > > > > > > > > previous place would be broken regardless. > > > > > > > > > > > > > > > > > > toml is more for configuration and yaml isn't a good one for this > > > > > > > > > case > > > > > > > > > as it further relies on indentation. I wouldn't oppose to use > > > > > > > > > json, but > > > > > > > > > don't expect to have dmesg to magically work because of that. > > > > > > > > TOML basically says 'use base64 and print it as a string'. And it > > > > > > > > supports multi-line strings, so the reader would have to drop > > > > > > > > newlines within a base64 object before doing the base64 decode. Or > > > > > > > > just use a base64 decoder that ignores whitespace. > > > > > > > > > > > > > > > > YAML seems to make even more explicit. From the 1.2.2 spec page: > > > > > > > > picture: !!binary | > > > > > > > > R0lGODlhDAAMAIQAAP//9/X > > > > > > > ^ space here for line continuation, as I mentioned. > > > > > > > > > > > > > > > 17unp5WZmZgAAAOfn515eXv > > > > > > > > Pz7Y6OjuDg4J+fn5OTk6enp > > > > > > > > 56enmleECcgggoBADs= > > > > > > > > > > > > > > > > So the userland reader just gets binary data straight out of the > > > > > > > > decoder library with no processing required. > > > > > > > A decoder library that we are *NOT* going to write. > > > > > > As above, the decoder library is definitely not written by us. It is > > > > > > libyaml or some such. > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > So let's fix the issue at hand and let the talk about xe's coredump > > > > > > > > > format for a later time. > > > > > > > > The issue at hand is that we have two fundamentally conflicting > > > > > > > > requirements. DMesg output requires line wrapping but the mesa tool > > > > > > > > has been coded in such a way that it breaks when given wrapped > > > > > > > > lines. There is nothing we can do about dmesg but making the mesa > > > > > > > > tool's parser more robust does not seem difficult. > > > > > > > > > > > > > > > > Switching to an externally defined encoding scheme that internally > > > > > > > > manages binary objects and supports wrapped lines would fix all > > > > > > > > issues and guarantee future compatibility. > > > > > > > > > > > > > > > > Note that line wrapping is not the only problem with the current > > > > > > > > mesa tool. Unless it has been updated since? The tool breaks if the > > > > > > > > context information is not part of the "GuC Communication > > > > > > > > Transport" section. Which is totally incorrect. Context state is > > > > > > > > very definitely not part > > > > > > > We reverted it because it's not ok to just move it to the "correct" > > > > > > > place and break the users. If it's in the incorrect place and we know > > > > > > > there's this parser already using it incorrectly, we can treat as a bug > > > > > > > in the kernel and adjust the userspace (it'd be considered a bug there > > > > > > > too and backported to their earlier releases). What we don't do is > > > > > > > simply merge the fix and break userspace. > > > > > > Can we not repeat old arguments? No-one realised that that change > > > > > > would break userspace. Or if they did, there was confusion over what > > > > > > exactly had or had not been tested and was causing a problem. > > > > > > Certainly it was not an intentional "merge and everyone be damned". > > > > > > > > > > > > My point was that there are multiple issues here. Line feeds is only > > > > > > one. But using a structured file format would prevent both of the > > > > > > problems we have currently hit. > > > > > > > > > > > > > Send the fix to the mesa tool if you want to change this in the kernel. > > > > > > When I can finally work out how to build mesa (it seems to require > > > > > > libraries that are newer than any Ubuntu release has access to!?) and > > > > > https://docs.mesa3d.org/install.html has the docs for that. > > > > Pretty sure that's what I was following last time. > > > > > > > > > For ubuntu, in our internal docs we document to install deps with: > > > > > > > > > > sudo apt build-dep mesa > > > > > > > > > > You can disable stuff you don't use. Our internal docs have this useful > > > > > set of args: > > > > > > > > > > meson setup \ > > > > > -Dprefix=/usr \ > > > > > -Dgallium-rusticl=false \ > > > > > -Dgallium-drivers=iris \ > > > > > -Dvulkan-drivers=intel \ > > > > > build > > > > > > > > > > I think you are probably talking about the llvm dep, that can be > > > > > workarounded by the setup flags above. > > > > I don't recall what the specific problem was last time. It looks like I > > > > have managed to get everything installed this time. However, the build > > > > does not appear to include the aubinator program. Nothing in > > > > src/intel/tools appears to get built at all. And I can't find any > > > > mention of how to build or use it in the Mesa docs or elsewhere. > > > Add -Dtools=intel to build it. > And how does one use it? Are there any regression tests that one can run > to verify operation? > > John. > > > > > > > > > > > > > > have spent time learning yet another code base and how the tool is > > > > > > implemented... > > > > > > > > > > > > > And as I said, for this particular change it doesn't matter if it's a > > > > > > > custom format, json, toml or whatever... the bug would still be the > > > > > > > same. > > > > > > Ideally not. Part of moving to a structured file format would be > > > > > > ensuring that the structure of the data is correct. > > > > > > > > > > > > > > of the GuC CT layer. That absolutely needs to be fixed. And > > > > > > > > generally, anything we can do to make the decoding more robust and > > > > > > > > future proof would be a very good thing. > > > > > > > > > > > > > > > > Note that the devcoredump content is highly dependent upon the > > > > > > > > internal workings of the driver. It is going to change over time. > > > > > > > > So the more robust the decoder, the better chance it has of not > > > > > > > > breaking when some new piece of data is added to the dump or an > > > > > > > > existing item removed or modified. > > > > > > > > > > > > > > > > > > that ideally supports binary data and compression natively and > > > > > > > > > > has a helper library that can be included in the kernel source > > > > > > > > > > tree. That > > > > > > > > > oh no, we'd need to define the schema - there are plenty of json > > > > > > > > > libraries > > > > > > > > > in multiple languages for users to choose from and that would be > > > > > > > > > basically > > > > > > > > > then main benefit of using it. > > > > > > > > Well, we can certainly define extra formats on top of a base format > > > > > > > > but it seems like it would be simpler if the base format supported > > > > > > > > all the data types we need already. Doesn't really matter either > > > > > > > > way as long as the underlying file format supports all the uses we > > > > > > > > want of it. > > > > > > > My point is that we are not going to add a decoder library that all > > > > > > > userspace consumers have to use. The kernel interface is not a library. > > > > > > > You are relying on having just one userspace to not break userspace. > > > > > > That is not at all what I am saying. > > > > > > > > > > > > > The benefit of a common format like json, toml etc is exactly that it's > > > > > > > a format already understood by hundreds of libraries and we can even do > > > > > > > something like this instead of having to write our own parser: > > > > > > > > > > > > > > cat devcoredump | jq '.[] | .foo, .bar' > > > > > > That is exactly what I am saying. > > > > > > > > > > > > The mesa debug tool becomes something like: > > > > > > #include <libyaml> > > > > > > > > > > > > info = yaml.read_file(file_name); > > > > > > foreach_engine(info.engines, i) > > > > > > printf( "Got hang on %s\n", info.engines[i].name ); > > > > > > > > > > > > The external library handles all the file encoding issues. The tool > > > > > > just has to put meaning to the fields returned from that library. > > > > > to reiterate my point that it doesn't fix all the problems: > > > > > > > > > > if you move something from info.guc_ct.bla to info.contexts.bla > > > > > (exactly what happened in the other bug) you may still break stuff, > > > > > regardless of using a better well-known format. > > > > But having the structure means that data will not be added to the wrong > > > > section in the first place. > > > > > > > > The problem here was that we had no structure to begin with. Then > > > > structure started to be added. But a tool was already making incorrect > > > > assumptions based on the lack of structure. > > > > > > > > Sure, when something needs to be moved, that will still cause the same > > > > kind of issue. But that is much less likely to happen if we are more > > > > careful about adding new entries within a sensible structure to begin with. > > > > > > > > John. > > > > > > > > > Lucas De Marchi > > > > > > > > > > > John. > > > > > > > > > > > > > Lucas De Marchi > > > > > > > > > > > > > > > John. > > > > > > > > > > > > > > > > > Lucas De Marchi > > > > > > > > > > > > > > > > > > > will then remove any and all confusion over interpretation of the > > > > > > > > > > file forever more. But it would require updating all userland > > > > > > > > > > tools to use the appropriate helper library. > > > > > > > > > > > > > > > > > > > > John. > > > > > > > > > > > > > > > > > > > > > Lucas De Marchi > ^ permalink raw reply [flat|nested] 22+ messages in thread
* Re: [PATCH v3 1/1] drm/xe/guc: Fix GuC log/ct output via debugfs 2025-01-23 14:02 ` Souza, Jose @ 2025-01-23 14:21 ` Lucas De Marchi 0 siblings, 0 replies; 22+ messages in thread From: Lucas De Marchi @ 2025-01-23 14:21 UTC (permalink / raw) To: Souza, Jose Cc: Harrison, John C, intel-xe@lists.freedesktop.org, Vivi, Rodrigo, Filipchuk, Julia On Thu, Jan 23, 2025 at 08:02:28AM -0600, Jose Souza wrote: >On Wed, 2025-01-22 at 13:09 -0800, John Harrison wrote: >> On 1/22/2025 10:29, Souza, Jose wrote: >> > On Wed, 2025-01-22 at 08:59 -0800, José Roberto de Souza wrote: >> > > On Wed, 2025-01-22 at 08:45 -0800, John Harrison wrote: >> > > > On 1/9/2025 14:43, Lucas De Marchi wrote: >> > > > > On Thu, Jan 09, 2025 at 12:40:51PM -0800, John Harrison wrote: >> > > > > > On 1/9/2025 07:39, Lucas De Marchi wrote: >> > > > > > > On Wed, Jan 08, 2025 at 03:59:58PM -0800, John Harrison wrote: >> > > > > > > > On 1/8/2025 14:11, Lucas De Marchi wrote: >> > > > > > > > > +Jose >> > > > > > > > > +Rodrigo >> > > > > > > > > >> > > > > > > > > On Wed, Jan 08, 2025 at 12:14:49PM -0800, John Harrison wrote: >> > > > > > > > > > On 1/7/2025 13:10, Lucas De Marchi wrote: >> > > > > > > > > > > On Tue, Jan 07, 2025 at 12:22:52PM -0800, Julia Filipchuk wrote: >> > > > > > > > > > > > Change to disable asci85 GuC logging only when output to >> > > > > > > > > > > > devcoredump >> > > > > > > > > > > > (was temporarily disabled for all code paths). >> > > > > > > > > > > > >> > > > > > > > > > > > v2: Ignore only for devcoredump case (not dmesg output). >> > > > > > > > > > > > v3: Rebase to resolve parent tag mismatch. >> > > > > > > > > > > > >> > > > > > > > > > > > Signed-off-by: Julia Filipchuk <julia.filipchuk@intel.com> >> > > > > > > > > > > > --- >> > > > > > > > > > > > drivers/gpu/drm/xe/xe_devcoredump.c | 8 +++++--- >> > > > > > > > > > > > include/drm/drm_print.h | 2 ++ >> > > > > > > > > > > > 2 files changed, 7 insertions(+), 3 deletions(-) >> > > > > > > > > > > > >> > > > > > > > > > > > diff --git a/drivers/gpu/drm/xe/xe_devcoredump.c >> > > > > > > > > > > > b/drivers/gpu/drm/xe/xe_devcoredump.c >> > > > > > > > > > > > index 6980304c8903..8e5d1f9866a7 100644 >> > > > > > > > > > > > --- a/drivers/gpu/drm/xe/xe_devcoredump.c >> > > > > > > > > > > > +++ b/drivers/gpu/drm/xe/xe_devcoredump.c >> > > > > > > > > > > > @@ -424,10 +424,12 @@ void xe_print_blob_ascii85(struct >> > > > > > > > > > > > drm_printer *p, const char *prefix, >> > > > > > > > > > > > * Splitting blobs across multiple lines is not compatible >> > > > > > > > > > > > with the mesa >> > > > > > > > > > > > * debug decoder tool. Note that even dropping the explicit >> > > > > > > > > > > > '\n' below >> > > > > > > > > > > > * doesn't help because the GuC log is so big some >> > > > > > > > > > > > underlying implementation >> > > > > > > > > > > > - * still splits the lines at 512K characters. So just bail >> > > > > > > > > > > > completely for >> > > > > > > > > > > > - * the moment. >> > > > > > > > > > > > + * still splits the lines at 512K characters. >> > > > > > > > > > > did we investigate where this is done and how we can overcome it? I >> > > > > > > > > > Yes. And the comment could be updated as part of this patch to >> > > > > > > > > > make it clearer... >> > > > > > > > > > >> > > > > > > > > > >> > > > > > > > > > * Splitting blobs across multiple lines is not compatible >> > > > > > > > > > with the mesa >> > > > > > > > > > * debug decoder tool. Note that even dropping the explicit >> > > > > > > > > > line wrapping >> > > > > > > > > > * below doesn't help because the GuC log can be so big it >> > > > > > > > > > needs to be split >> > > > > > > > > > * into multiple 2MB chunks, each of which must be printed >> > > > > > > > > > individually and >> > > > > > > > > > * therefore will be a separate line. >> > > > > > > > > so there's no "underlying implemenation that splits like at 512K >> > > > > > > > > chars"? >> > > > > > > > > Nowe it's something else: a 2MB chunk because of what? >> > > > > > > > The GuC log is captured in multiple 2MB chunks because we can't >> > > > > > > > kmalloc a full 16MB block at a single time irrespective of memory >> > > > > > > > fragmentation - the kmalloc function aborts with a page size error >> > > > > > > > above 8MB, I recall. Might even have been 4MB? The 2MB chunks >> > > > > > > > become approx 512K characters of ASCII85 output (when mostly full >> > > > > > > > of zeros). Because each chunk is a separate bo object the memory is >> > > > > > > > not contiguous so each must be printed with a separate call to >> > > > > > > > xe_print_blob_ascii85(). If xe_print_blob_ascii85() includes a >> > > > > > > > terminating line feed at the end of the print then that means >> > > > > > > > multiple lines for the GuC log. >> > > > > > > now it makes sense... and contradicts what was said earlier about the >> > > > > > > "underlying implementation still splits the lines at 512K characters". >> > > > > > > It's this very function that is splitting it. >> > > > > > The initial comment was written before the situation was fully >> > > > > > understood because it was a quick hack to get the mesa debug tool >> > > > > > working again. >> > > > > > >> > > > > > The split is a combination of the helper function adding a linefeed >> > > > > > to the end of the output and the GuC log being so large it must be >> > > > > > split into multiple malloc buffers. But it is not related to the 800 >> > > > > > character line wrapping within the helper's output. >> > > > @Lucas, are you happy with the above now? If the patch is updated with >> > > > the comment as above can we get it merged? We currently have no access >> > > > to GuC logs via debugfs which makes debugging issues difficult. Multiple >> > > > people have already complained about this not working. >> > >> > I thought it was agreed that the line break were not necessary and was being added because of the way GuC log output code was written, so why it is >> > still being used? >> As per earlier comments, removing the line breaks requires doing hacky >> things and/or having messy interfaces in the kernel. Being understood is >> not the same thing as saying removing it is the perfect solution. > >we have years of i915 having no line breaks and no issues. This is done in https://patchwork.freedesktop.org/series/143872/ > >> >> Whereas supporting wrapped lines is defensive programming. It makes the >> tool more robust for when core dump files arrive from random end users >> that have passed them through who knows what text editor or email tool. >> > >it should be shared compressed or decoded(with mesa or other too). > >> >> > >> > In my opinion this patch is changing a struct that is used by all drm drivers, not sure if we can change without an ack from a drm maintainer. >> > >> > Also would be nice if GuC log follow the same pattern as other binaries in devcoredump like: >> > >> > >> > [HWCTX].length: 0x1000 >> > [HWCTX].data: xxxxx yeah, if you want to re-create the struct binary first by decoding it from devcoredump and as a second step handle the data, that's useful. Ideally we'd add the encoded size though, otherwise you'd have to decode even the fields you don't care about since you can't just jump e.g. 0x100 bytes to get the next one. I don't think it'd work for mesa to prevent random chars getting in the way since mesa skips fields it's not interest into. You'd have to parse every single field and it'd take just an addition of a new field to break the parser again since we don't have annotation of fields that are encoded or what algo is used for encoding it. If we add the decoded size, we may need to be careful what key to use so it's clear what it is and that it doesn't prevent us from adding the encoded size in future, which IMO is more useful when parsing binaries, but harder to add in this case. Lucas De Marchi >> > >> > [200000].length: 0x40000 >> > [200000].data: xxxxx >> I'm not seeing how that helps. > >First consistency, second we can re-use the same code that parses other binaries to parse this one too. > >> >> The size above is the decoded size. That does not tell you anything >> about the amount of ASCII85 data because the encoding is variable >> length. The ASCII85 spec includes basic run length encoding of zero >> filled data. So the amount of ASCII data is not a simple function of the >> input buffer size. > >At least for the other binaries I need to know the whole binary size, allocate the memory, then I will start to decode and store that in the allocated >memory. Then at last I can check if the number of bytes decoded match with length, to make sure nothing was lost. > >> >> > >> > And again we should avoid break the Mesa parser as much as possible, customers open bugs and attach it. And soon the same devcoredump will be used to >> > replay the batch buffer and all the context that cause the GPU hang in simulator and real HW. >> Avoiding breaks is not the same thing as not allowing improvements. >> >> > >> > > > >> > > > > > > > > I don't really want to keep updating this instead of fixing it. >> > > > > > > > > >> > > > > > > > > > The dump helper could be updated to never add any line feeds, not >> > > > > > > > > > even >> > > > > > > > > when you say "dump helper", what exactly are you talking about? >> > > > > > > > > xe_print_blob_ascii85(), __xe_devcoredump_read(), >> > > > > > > > > __drm_puts_coredump() >> > > > > > > > > or what? >> > > > > > > > xe_print_blob_ascii85 >> > > > > > > > >> > > > > > > > > If it's about xe_print_blob_ascii85(), I think this would be the >> > > > > > > > > first step: >> > > > > > > > > drop the \n you are adding. AFAICS calling the print function in >> > > > > > > > > chunks >> > > > > > > > > of 800B would be fine, just don't add any \n. If that still adds \n >> > > > > > > > > somewhere, we can check how to drop it or you then may have a pretty >> > > > > > > > > solid argument to adapt the mesa tool with a newline >> > > > > > > > > continuar char and send them the MR. >> > > > > > > > As above, the chunking is at the next level out. So dropping the >> > > > > > > > 800 byte \n won't help with the GuC log still being split into >> > > > > > > > multiple lines. You have to either move the terminating \n outside >> > > > > > > > of the helper and into the callers or add a bool parameter to >> > > > > > > > enable/disable it. Either of which is just messy. >> > > > > > > If the caller knows it's calling the function multiple times to >> > > > > > > continue >> > > > > > > previous data, it's not unreasonable to have an arg to terminate it or >> > > > > > > not. It's for example what python does with its 'end' arg to the >> > > > > > > print() >> > > > > > > function. >> > > > > > Just because someone else does it does not make it clean or the best >> > > > > > solution. >> > > > > > >> > > > > > > > Or extend the helper to take an array/list of pointers in a >> > > > > > > > scatter/gather fashion. >> > > > > > > > >> > > > > > > > And if you drop the 800B \n then you break the dmesg output >> > > > > > > > facility. Which means we can't get logs out from CI panic type >> > > > > > > > situations. >> > > > > > > Or that we should have another way to get a devcoredump. I don't think >> > > > > > > we are going to print the devcoredump to dmesg when the kernel panics. >> > > > > > > We may print it when we fail to probe, but the cpu should still be very >> > > > > > > much alive - we tie the devcoredump lifecycle to the lifecycle of the >> > > > > > > device, so we don't have an opportunity to get that data. >> > > > > > > >> > > > > > > The workaround you add is to dump the whole thing to dmesg, but we >> > > > > > > could >> > > > > > > dump it somewhere else like a debugfs that is tied to the module >> > > > > > > lifecycle. >> > > > > > The point is to get usable logs out of CI. There are multiple >> > > > > > situations in which CI fails to save logs. By 'panic' I was more >> > > > > > meaning situations where we have very rare bugs that can't be hit >> > > > > > locally and for which CI is not providing useful logs. I.e. we are in >> > > > > > a panic about how to debug it and dumping via dmesg is the only >> > > > > > viable option. >> > > > > > >> > > > > > > The dmesg (kmsg) format already contains other things you have to >> > > > > > > ignore >> > > > > > > to extract the message: >> > > > > > > >> > > > > > > * /dev/kmsg exports the structured data in the following line >> > > > > > > format: * >> > > > > > > "<level>,<sequnum>,<timestamp>,<contflag>[,additional_values, ... >> > > > > > > ];<message text>\n" >> > > > > > > >> > > > > > > so you will always have to preprocess it, ignore lines that don't >> > > > > > > belong >> > > > > > > to the log, etc. >> > > > > > I never said this was not the case. The GuC log decoding tool already >> > > > > > copes with myriad different dmesg, syslog, serial console, etc. >> > > > > > output formats. >> > > > > > >> > > > > > > And if you print it correctly, you can even make use of the LOG_CONT to >> > > > > > > mark the new line as continuation of the previous one. >> > > > > > Reconstructing split lines has never been a problem for GuC decoder >> > > > > > tool. It is only the mesa tool that has a problem with line feeds. >> > > > > > >> > > > > > > > > > at the end. And then the burden would be on the callers to add >> > > > > > > > > > line feeds as appropriate. That seems extremely messy, though. >> > > > > > > > > > And it will break the dmesg output facility. That does need the >> > > > > > > > > > line wrapping at ~800 characters which can't be done from outside >> > > > > > > > > > the helper. >> > > > > > > > > > >> > > > > > > > > > > understand having to split it into multiple calls, but not >> > > > > > > > > > > something >> > > > > > > > > > > adding a \n. particularly for the functions dealing with >> > > > > > > > > > > seq_file and >> > > > > > > > > > > devcoredump. >> > > > > > > > > > > >> > > > > > > > > > > > + * >> > > > > > > > > > > > + * Only disable from devcoredump output. >> > > > > > > > > > > > */ >> > > > > > > > > > > > - return; >> > > > > > > > > > > > + if (p->coredump) >> > > > > > > > > > > but we do want the guc log to be inside the devcoredump, so >> > > > > > > > > > > rather than >> > > > > > > > > > > adding more workarounds, can we fix it ? >> > > > > > > > > > The simplest fix is your suggestion of adding an extra white >> > > > > > > > > > space character at the end of the line in the helper function and >> > > > > > > > > > updating the mesa tool to support multi-line output. That seems >> > > > > > > > > > like it should be a trivial update to the mesa tool and it keeps >> > > > > > > > > > the KMD side simple and consistent across all potential output >> > > > > > > > > > methods. But Jose seemed absolutely dead set against any updates >> > > > > > > > > > to the mesa tool at all :(. >> > > > > > > > > > >> > > > > > > > > > The more complex fix is Joonas' idea of using an official >> > > > > > > > > > structured output format of some sort - TOML, YAML, JSON or >> > > > > > > > > > whatever. Something >> > > > > > > > > it actually doesn't fix this particular issue. It fixes others, >> > > > > > > > > but not >> > > > > > > > > this one. >> > > > > > > > If we do it properly then it fixes everything. The format library >> > > > > > > > would have helper functions that the devcoredump code can call to >> > > > > > > but we are *NOT* going to export a library for that. You are just >> > > > > > > shifting the problem to "we have only one userspace that is our own >> > > > > > > library, deal with it". >> > > > > > No. By library, I mean libjson or libyaml or whatever. The whole >> > > > > > point of using an externally defined file format is that you can use >> > > > > > an externally written library to read that format. Whatever userspace >> > > > > > tool only has to worry about processing data/value pairs or whatever >> > > > > > you get from the library's read interface, it no longer has to worry >> > > > > > about file formats, character encodings, line wraps, etc. All that is >> > > > > > handled by the third party library / file format definition. >> > > > > > >> > > > > > > > print integers, bools, strings and BLOBs. The debugfs/sysfs output >> > > > > > > > would just stream the encoded output exactly as is. The dmesg >> > > > > > > > output layer would add the 800 character line wrapping in a way >> > > > > > > > that the dmesg decoder can undo before passing to the decoder library. >> > > > > > > > >> > > > > > > > > "Guc Log": "<encoded data .........." >> > > > > > > > > >> > > > > > > > > if you need to split lines, you still need something to do do it in >> > > > > > > > > whatever format you choose. One json I remember working on in the >> > > > > > > > > past >> > > > > > > > > that embeds the binary is the .apj format... example: >> > > > > > > > > https://firmware.ardupilot.org/Copter/2024-12/2024-12-02-13:12/CubeBlack/arducopter.apj >> > > > > > > > > >> > > > > > > > > >> > > > > > > > > >> > > > > > > > > >> > > > > > > > > { >> > > > > > > > > "board_id": 9, >> > > > > > > > > "magic": "APJFWv1", >> > > > > > > > > "description": "Firmware for a STM32F427xx board", >> > > > > > > > > "image": "eNqUvAlcU1faMH5u7k1yCQGCICCgBoIaRW0EtVSxhg ... >> > > > > > > > > >> > > > > > > > > here "image" is base64-encoded afair. But in your case, just >> > > > > > > > > printing >> > > > > > > > > the json to dmesg wouldn't work because of needing to split the line. >> > > > > > > > > It wouldn't fix the kind of bugs we had in the past too: in json it >> > > > > > > > > would be the equivalent of adding a field to the wrong object and >> > > > > > > > > then >> > > > > > > > > move it elsewhere. An application trying to read that object in the >> > > > > > > > > previous place would be broken regardless. >> > > > > > > > > >> > > > > > > > > toml is more for configuration and yaml isn't a good one for this >> > > > > > > > > case >> > > > > > > > > as it further relies on indentation. I wouldn't oppose to use >> > > > > > > > > json, but >> > > > > > > > > don't expect to have dmesg to magically work because of that. >> > > > > > > > TOML basically says 'use base64 and print it as a string'. And it >> > > > > > > > supports multi-line strings, so the reader would have to drop >> > > > > > > > newlines within a base64 object before doing the base64 decode. Or >> > > > > > > > just use a base64 decoder that ignores whitespace. >> > > > > > > > >> > > > > > > > YAML seems to make even more explicit. From the 1.2.2 spec page: >> > > > > > > > picture: !!binary | >> > > > > > > > R0lGODlhDAAMAIQAAP//9/X >> > > > > > > ^ space here for line continuation, as I mentioned. >> > > > > > > >> > > > > > > > 17unp5WZmZgAAAOfn515eXv >> > > > > > > > Pz7Y6OjuDg4J+fn5OTk6enp >> > > > > > > > 56enmleECcgggoBADs= >> > > > > > > > >> > > > > > > > So the userland reader just gets binary data straight out of the >> > > > > > > > decoder library with no processing required. >> > > > > > > A decoder library that we are *NOT* going to write. >> > > > > > As above, the decoder library is definitely not written by us. It is >> > > > > > libyaml or some such. >> > > > > > >> > > > > > > >> > > > > > > > >> > > > > > > > > So let's fix the issue at hand and let the talk about xe's coredump >> > > > > > > > > format for a later time. >> > > > > > > > The issue at hand is that we have two fundamentally conflicting >> > > > > > > > requirements. DMesg output requires line wrapping but the mesa tool >> > > > > > > > has been coded in such a way that it breaks when given wrapped >> > > > > > > > lines. There is nothing we can do about dmesg but making the mesa >> > > > > > > > tool's parser more robust does not seem difficult. >> > > > > > > > >> > > > > > > > Switching to an externally defined encoding scheme that internally >> > > > > > > > manages binary objects and supports wrapped lines would fix all >> > > > > > > > issues and guarantee future compatibility. >> > > > > > > > >> > > > > > > > Note that line wrapping is not the only problem with the current >> > > > > > > > mesa tool. Unless it has been updated since? The tool breaks if the >> > > > > > > > context information is not part of the "GuC Communication >> > > > > > > > Transport" section. Which is totally incorrect. Context state is >> > > > > > > > very definitely not part >> > > > > > > We reverted it because it's not ok to just move it to the "correct" >> > > > > > > place and break the users. If it's in the incorrect place and we know >> > > > > > > there's this parser already using it incorrectly, we can treat as a bug >> > > > > > > in the kernel and adjust the userspace (it'd be considered a bug there >> > > > > > > too and backported to their earlier releases). What we don't do is >> > > > > > > simply merge the fix and break userspace. >> > > > > > Can we not repeat old arguments? No-one realised that that change >> > > > > > would break userspace. Or if they did, there was confusion over what >> > > > > > exactly had or had not been tested and was causing a problem. >> > > > > > Certainly it was not an intentional "merge and everyone be damned". >> > > > > > >> > > > > > My point was that there are multiple issues here. Line feeds is only >> > > > > > one. But using a structured file format would prevent both of the >> > > > > > problems we have currently hit. >> > > > > > >> > > > > > > Send the fix to the mesa tool if you want to change this in the kernel. >> > > > > > When I can finally work out how to build mesa (it seems to require >> > > > > > libraries that are newer than any Ubuntu release has access to!?) and >> > > > > https://docs.mesa3d.org/install.html has the docs for that. >> > > > Pretty sure that's what I was following last time. >> > > > >> > > > > For ubuntu, in our internal docs we document to install deps with: >> > > > > >> > > > > sudo apt build-dep mesa >> > > > > >> > > > > You can disable stuff you don't use. Our internal docs have this useful >> > > > > set of args: >> > > > > >> > > > > meson setup \ >> > > > > -Dprefix=/usr \ >> > > > > -Dgallium-rusticl=false \ >> > > > > -Dgallium-drivers=iris \ >> > > > > -Dvulkan-drivers=intel \ >> > > > > build >> > > > > >> > > > > I think you are probably talking about the llvm dep, that can be >> > > > > workarounded by the setup flags above. >> > > > I don't recall what the specific problem was last time. It looks like I >> > > > have managed to get everything installed this time. However, the build >> > > > does not appear to include the aubinator program. Nothing in >> > > > src/intel/tools appears to get built at all. And I can't find any >> > > > mention of how to build or use it in the Mesa docs or elsewhere. >> > > Add -Dtools=intel to build it. >> And how does one use it? Are there any regression tests that one can run >> to verify operation? >> >> John. >> >> > > >> > > > >> > > > > > have spent time learning yet another code base and how the tool is >> > > > > > implemented... >> > > > > > >> > > > > > > And as I said, for this particular change it doesn't matter if it's a >> > > > > > > custom format, json, toml or whatever... the bug would still be the >> > > > > > > same. >> > > > > > Ideally not. Part of moving to a structured file format would be >> > > > > > ensuring that the structure of the data is correct. >> > > > > > >> > > > > > > > of the GuC CT layer. That absolutely needs to be fixed. And >> > > > > > > > generally, anything we can do to make the decoding more robust and >> > > > > > > > future proof would be a very good thing. >> > > > > > > > >> > > > > > > > Note that the devcoredump content is highly dependent upon the >> > > > > > > > internal workings of the driver. It is going to change over time. >> > > > > > > > So the more robust the decoder, the better chance it has of not >> > > > > > > > breaking when some new piece of data is added to the dump or an >> > > > > > > > existing item removed or modified. >> > > > > > > > >> > > > > > > > > > that ideally supports binary data and compression natively and >> > > > > > > > > > has a helper library that can be included in the kernel source >> > > > > > > > > > tree. That >> > > > > > > > > oh no, we'd need to define the schema - there are plenty of json >> > > > > > > > > libraries >> > > > > > > > > in multiple languages for users to choose from and that would be >> > > > > > > > > basically >> > > > > > > > > then main benefit of using it. >> > > > > > > > Well, we can certainly define extra formats on top of a base format >> > > > > > > > but it seems like it would be simpler if the base format supported >> > > > > > > > all the data types we need already. Doesn't really matter either >> > > > > > > > way as long as the underlying file format supports all the uses we >> > > > > > > > want of it. >> > > > > > > My point is that we are not going to add a decoder library that all >> > > > > > > userspace consumers have to use. The kernel interface is not a library. >> > > > > > > You are relying on having just one userspace to not break userspace. >> > > > > > That is not at all what I am saying. >> > > > > > >> > > > > > > The benefit of a common format like json, toml etc is exactly that it's >> > > > > > > a format already understood by hundreds of libraries and we can even do >> > > > > > > something like this instead of having to write our own parser: >> > > > > > > >> > > > > > > cat devcoredump | jq '.[] | .foo, .bar' >> > > > > > That is exactly what I am saying. >> > > > > > >> > > > > > The mesa debug tool becomes something like: >> > > > > > #include <libyaml> >> > > > > > >> > > > > > info = yaml.read_file(file_name); >> > > > > > foreach_engine(info.engines, i) >> > > > > > printf( "Got hang on %s\n", info.engines[i].name ); >> > > > > > >> > > > > > The external library handles all the file encoding issues. The tool >> > > > > > just has to put meaning to the fields returned from that library. >> > > > > to reiterate my point that it doesn't fix all the problems: >> > > > > >> > > > > if you move something from info.guc_ct.bla to info.contexts.bla >> > > > > (exactly what happened in the other bug) you may still break stuff, >> > > > > regardless of using a better well-known format. >> > > > But having the structure means that data will not be added to the wrong >> > > > section in the first place. >> > > > >> > > > The problem here was that we had no structure to begin with. Then >> > > > structure started to be added. But a tool was already making incorrect >> > > > assumptions based on the lack of structure. >> > > > >> > > > Sure, when something needs to be moved, that will still cause the same >> > > > kind of issue. But that is much less likely to happen if we are more >> > > > careful about adding new entries within a sensible structure to begin with. >> > > > >> > > > John. >> > > > >> > > > > Lucas De Marchi >> > > > > >> > > > > > John. >> > > > > > >> > > > > > > Lucas De Marchi >> > > > > > > >> > > > > > > > John. >> > > > > > > > >> > > > > > > > > Lucas De Marchi >> > > > > > > > > >> > > > > > > > > > will then remove any and all confusion over interpretation of the >> > > > > > > > > > file forever more. But it would require updating all userland >> > > > > > > > > > tools to use the appropriate helper library. >> > > > > > > > > > >> > > > > > > > > > John. >> > > > > > > > > > >> > > > > > > > > > > Lucas De Marchi >> > ^ permalink raw reply [flat|nested] 22+ messages in thread
* ✓ CI.Build: success for series starting with [v3,1/1] drm/xe/guc: Fix GuC log/ct output via debugfs 2025-01-07 20:22 [PATCH v3 1/1] drm/xe/guc: Fix GuC log/ct output via debugfs Julia Filipchuk ` (3 preceding siblings ...) 2025-01-07 21:10 ` [PATCH v3 1/1] " Lucas De Marchi @ 2025-01-07 21:25 ` Patchwork 2025-01-07 21:28 ` ✓ CI.Hooks: " Patchwork ` (3 subsequent siblings) 8 siblings, 0 replies; 22+ messages in thread From: Patchwork @ 2025-01-07 21:25 UTC (permalink / raw) To: Julia Filipchuk; +Cc: intel-xe == Series Details == Series: series starting with [v3,1/1] drm/xe/guc: Fix GuC log/ct output via debugfs URL : https://patchwork.freedesktop.org/series/143203/ State : success == Summary == lib/modules/6.13.0-rc6-xe+/kernel/arch/x86/events/rapl.ko lib/modules/6.13.0-rc6-xe+/kernel/arch/x86/kvm/ lib/modules/6.13.0-rc6-xe+/kernel/arch/x86/kvm/kvm.ko lib/modules/6.13.0-rc6-xe+/kernel/arch/x86/kvm/kvm-intel.ko lib/modules/6.13.0-rc6-xe+/kernel/arch/x86/kvm/kvm-amd.ko lib/modules/6.13.0-rc6-xe+/kernel/kernel/ lib/modules/6.13.0-rc6-xe+/kernel/kernel/kheaders.ko lib/modules/6.13.0-rc6-xe+/kernel/crypto/ lib/modules/6.13.0-rc6-xe+/kernel/crypto/ecrdsa_generic.ko lib/modules/6.13.0-rc6-xe+/kernel/crypto/xcbc.ko lib/modules/6.13.0-rc6-xe+/kernel/crypto/serpent_generic.ko lib/modules/6.13.0-rc6-xe+/kernel/crypto/aria_generic.ko lib/modules/6.13.0-rc6-xe+/kernel/crypto/crypto_simd.ko lib/modules/6.13.0-rc6-xe+/kernel/crypto/adiantum.ko lib/modules/6.13.0-rc6-xe+/kernel/crypto/tcrypt.ko lib/modules/6.13.0-rc6-xe+/kernel/crypto/crypto_engine.ko lib/modules/6.13.0-rc6-xe+/kernel/crypto/zstd.ko lib/modules/6.13.0-rc6-xe+/kernel/crypto/asymmetric_keys/ lib/modules/6.13.0-rc6-xe+/kernel/crypto/asymmetric_keys/pkcs7_test_key.ko lib/modules/6.13.0-rc6-xe+/kernel/crypto/asymmetric_keys/pkcs8_key_parser.ko lib/modules/6.13.0-rc6-xe+/kernel/crypto/des_generic.ko lib/modules/6.13.0-rc6-xe+/kernel/crypto/xctr.ko lib/modules/6.13.0-rc6-xe+/kernel/crypto/authenc.ko lib/modules/6.13.0-rc6-xe+/kernel/crypto/sm4_generic.ko lib/modules/6.13.0-rc6-xe+/kernel/crypto/keywrap.ko lib/modules/6.13.0-rc6-xe+/kernel/crypto/camellia_generic.ko lib/modules/6.13.0-rc6-xe+/kernel/crypto/sm3.ko lib/modules/6.13.0-rc6-xe+/kernel/crypto/pcrypt.ko lib/modules/6.13.0-rc6-xe+/kernel/crypto/aegis128.ko lib/modules/6.13.0-rc6-xe+/kernel/crypto/af_alg.ko lib/modules/6.13.0-rc6-xe+/kernel/crypto/algif_aead.ko lib/modules/6.13.0-rc6-xe+/kernel/crypto/cmac.ko lib/modules/6.13.0-rc6-xe+/kernel/crypto/sm3_generic.ko lib/modules/6.13.0-rc6-xe+/kernel/crypto/aes_ti.ko lib/modules/6.13.0-rc6-xe+/kernel/crypto/chacha_generic.ko lib/modules/6.13.0-rc6-xe+/kernel/crypto/poly1305_generic.ko lib/modules/6.13.0-rc6-xe+/kernel/crypto/nhpoly1305.ko lib/modules/6.13.0-rc6-xe+/kernel/crypto/crc32_generic.ko lib/modules/6.13.0-rc6-xe+/kernel/crypto/essiv.ko lib/modules/6.13.0-rc6-xe+/kernel/crypto/ccm.ko lib/modules/6.13.0-rc6-xe+/kernel/crypto/wp512.ko lib/modules/6.13.0-rc6-xe+/kernel/crypto/streebog_generic.ko lib/modules/6.13.0-rc6-xe+/kernel/crypto/authencesn.ko lib/modules/6.13.0-rc6-xe+/kernel/crypto/echainiv.ko lib/modules/6.13.0-rc6-xe+/kernel/crypto/lrw.ko lib/modules/6.13.0-rc6-xe+/kernel/crypto/cryptd.ko lib/modules/6.13.0-rc6-xe+/kernel/crypto/crypto_user.ko lib/modules/6.13.0-rc6-xe+/kernel/crypto/algif_hash.ko lib/modules/6.13.0-rc6-xe+/kernel/crypto/vmac.ko lib/modules/6.13.0-rc6-xe+/kernel/crypto/polyval-generic.ko lib/modules/6.13.0-rc6-xe+/kernel/crypto/hctr2.ko lib/modules/6.13.0-rc6-xe+/kernel/crypto/842.ko lib/modules/6.13.0-rc6-xe+/kernel/crypto/pcbc.ko lib/modules/6.13.0-rc6-xe+/kernel/crypto/ansi_cprng.ko lib/modules/6.13.0-rc6-xe+/kernel/crypto/cast6_generic.ko lib/modules/6.13.0-rc6-xe+/kernel/crypto/twofish_common.ko lib/modules/6.13.0-rc6-xe+/kernel/crypto/twofish_generic.ko lib/modules/6.13.0-rc6-xe+/kernel/crypto/lz4hc.ko lib/modules/6.13.0-rc6-xe+/kernel/crypto/blowfish_generic.ko lib/modules/6.13.0-rc6-xe+/kernel/crypto/md4.ko lib/modules/6.13.0-rc6-xe+/kernel/crypto/chacha20poly1305.ko lib/modules/6.13.0-rc6-xe+/kernel/crypto/curve25519-generic.ko lib/modules/6.13.0-rc6-xe+/kernel/crypto/lz4.ko lib/modules/6.13.0-rc6-xe+/kernel/crypto/rmd160.ko lib/modules/6.13.0-rc6-xe+/kernel/crypto/algif_skcipher.ko lib/modules/6.13.0-rc6-xe+/kernel/crypto/cast5_generic.ko lib/modules/6.13.0-rc6-xe+/kernel/crypto/fcrypt.ko lib/modules/6.13.0-rc6-xe+/kernel/crypto/ecdsa_generic.ko lib/modules/6.13.0-rc6-xe+/kernel/crypto/sm4.ko lib/modules/6.13.0-rc6-xe+/kernel/crypto/cast_common.ko lib/modules/6.13.0-rc6-xe+/kernel/crypto/blowfish_common.ko lib/modules/6.13.0-rc6-xe+/kernel/crypto/michael_mic.ko lib/modules/6.13.0-rc6-xe+/kernel/crypto/async_tx/ lib/modules/6.13.0-rc6-xe+/kernel/crypto/async_tx/async_xor.ko lib/modules/6.13.0-rc6-xe+/kernel/crypto/async_tx/async_tx.ko lib/modules/6.13.0-rc6-xe+/kernel/crypto/async_tx/async_memcpy.ko lib/modules/6.13.0-rc6-xe+/kernel/crypto/async_tx/async_pq.ko lib/modules/6.13.0-rc6-xe+/kernel/crypto/async_tx/async_raid6_recov.ko lib/modules/6.13.0-rc6-xe+/kernel/crypto/algif_rng.ko lib/modules/6.13.0-rc6-xe+/kernel/block/ lib/modules/6.13.0-rc6-xe+/kernel/block/bfq.ko lib/modules/6.13.0-rc6-xe+/kernel/block/kyber-iosched.ko lib/modules/6.13.0-rc6-xe+/build lib/modules/6.13.0-rc6-xe+/modules.alias.bin lib/modules/6.13.0-rc6-xe+/modules.builtin lib/modules/6.13.0-rc6-xe+/modules.softdep lib/modules/6.13.0-rc6-xe+/modules.alias lib/modules/6.13.0-rc6-xe+/modules.order lib/modules/6.13.0-rc6-xe+/modules.symbols lib/modules/6.13.0-rc6-xe+/modules.dep.bin + mv kernel-nodebug.tar.gz .. + cd .. + rm -rf archive ++ date +%s + echo -e '\e[0Ksection_end:1736285138:package_x86_64_nodebug\r\e[0K' ^[[0Ksection_end:1736285138:package_x86_64_nodebug ^[[0K + sync + cleanup ++ stat -c %u:%g /kernel + chown -R 1003:1003 /kernel ^ permalink raw reply [flat|nested] 22+ messages in thread
* ✓ CI.Hooks: success for series starting with [v3,1/1] drm/xe/guc: Fix GuC log/ct output via debugfs 2025-01-07 20:22 [PATCH v3 1/1] drm/xe/guc: Fix GuC log/ct output via debugfs Julia Filipchuk ` (4 preceding siblings ...) 2025-01-07 21:25 ` ✓ CI.Build: success for series starting with [v3,1/1] " Patchwork @ 2025-01-07 21:28 ` Patchwork 2025-01-07 21:30 ` ✓ CI.checksparse: " Patchwork ` (2 subsequent siblings) 8 siblings, 0 replies; 22+ messages in thread From: Patchwork @ 2025-01-07 21:28 UTC (permalink / raw) To: Julia Filipchuk; +Cc: intel-xe == Series Details == Series: series starting with [v3,1/1] drm/xe/guc: Fix GuC log/ct output via debugfs URL : https://patchwork.freedesktop.org/series/143203/ State : success == Summary == run-parts: executing /workspace/ci/hooks/00-showenv + export + grep -Ei '(^|\W)CI_' declare -x CI_KERNEL_BUILD_DIR="/workspace/kernel/build64-default" declare -x CI_KERNEL_SRC_DIR="/workspace/kernel" declare -x CI_TOOLS_SRC_DIR="/workspace/ci" declare -x CI_WORKSPACE_DIR="/workspace" run-parts: executing /workspace/ci/hooks/10-build-W1 + SRC_DIR=/workspace/kernel + RESTORE_DISPLAY_CONFIG=0 + '[' -n /workspace/kernel/build64-default ']' + BUILD_DIR=/workspace/kernel/build64-default + cd /workspace/kernel ++ nproc + make -j48 O=/workspace/kernel/build64-default modules_prepare make[1]: Entering directory '/workspace/kernel/build64-default' GEN Makefile mkdir -p /workspace/kernel/build64-default/tools/objtool && make O=/workspace/kernel/build64-default subdir=tools/objtool --no-print-directory -C objtool CALL ../scripts/checksyscalls.sh INSTALL libsubcmd_headers CC /workspace/kernel/build64-default/tools/objtool/libsubcmd/exec-cmd.o CC /workspace/kernel/build64-default/tools/objtool/libsubcmd/help.o CC /workspace/kernel/build64-default/tools/objtool/libsubcmd/pager.o CC /workspace/kernel/build64-default/tools/objtool/libsubcmd/parse-options.o CC /workspace/kernel/build64-default/tools/objtool/libsubcmd/run-command.o CC /workspace/kernel/build64-default/tools/objtool/libsubcmd/sigchain.o CC /workspace/kernel/build64-default/tools/objtool/libsubcmd/subcmd-config.o LD /workspace/kernel/build64-default/tools/objtool/libsubcmd/libsubcmd-in.o AR /workspace/kernel/build64-default/tools/objtool/libsubcmd/libsubcmd.a CC /workspace/kernel/build64-default/tools/objtool/weak.o CC /workspace/kernel/build64-default/tools/objtool/check.o CC /workspace/kernel/build64-default/tools/objtool/special.o CC /workspace/kernel/build64-default/tools/objtool/elf.o CC /workspace/kernel/build64-default/tools/objtool/builtin-check.o CC /workspace/kernel/build64-default/tools/objtool/objtool.o CC /workspace/kernel/build64-default/tools/objtool/orc_gen.o CC /workspace/kernel/build64-default/tools/objtool/orc_dump.o CC /workspace/kernel/build64-default/tools/objtool/libstring.o CC /workspace/kernel/build64-default/tools/objtool/arch/x86/special.o CC /workspace/kernel/build64-default/tools/objtool/libctype.o CC /workspace/kernel/build64-default/tools/objtool/arch/x86/decode.o CC /workspace/kernel/build64-default/tools/objtool/str_error_r.o CC /workspace/kernel/build64-default/tools/objtool/librbtree.o CC /workspace/kernel/build64-default/tools/objtool/arch/x86/orc.o LD /workspace/kernel/build64-default/tools/objtool/arch/x86/objtool-in.o LD /workspace/kernel/build64-default/tools/objtool/objtool-in.o LINK /workspace/kernel/build64-default/tools/objtool/objtool make[1]: Leaving directory '/workspace/kernel/build64-default' ++ nproc + make -j48 O=/workspace/kernel/build64-default W=1 drivers/gpu/drm/xe make[1]: Entering directory '/workspace/kernel/build64-default' make[2]: Nothing to be done for 'drivers/gpu/drm/xe'. make[1]: Leaving directory '/workspace/kernel/build64-default' run-parts: executing /workspace/ci/hooks/11-build-32b +++ realpath /workspace/ci/hooks/11-build-32b ++ dirname /workspace/ci/hooks/11-build-32b + THIS_SCRIPT_DIR=/workspace/ci/hooks + SRC_DIR=/workspace/kernel + TOOLS_SRC_DIR=/workspace/ci + '[' -n /workspace/kernel/build64-default ']' + BUILD_DIR=/workspace/kernel/build64-default + BUILD_DIR=/workspace/kernel/build64-default/build32 + cd /workspace/kernel + mkdir -p /workspace/kernel/build64-default/build32 ++ nproc + make -j48 ARCH=i386 O=/workspace/kernel/build64-default/build32 defconfig make[1]: Entering directory '/workspace/kernel/build64-default/build32' GEN Makefile HOSTCC scripts/basic/fixdep HOSTCC scripts/kconfig/conf.o HOSTCC scripts/kconfig/confdata.o HOSTCC scripts/kconfig/expr.o LEX scripts/kconfig/lexer.lex.c YACC scripts/kconfig/parser.tab.[ch] HOSTCC scripts/kconfig/menu.o HOSTCC scripts/kconfig/preprocess.o HOSTCC scripts/kconfig/symbol.o HOSTCC scripts/kconfig/util.o HOSTCC scripts/kconfig/lexer.lex.o HOSTCC scripts/kconfig/parser.tab.o HOSTLD scripts/kconfig/conf *** Default configuration is based on 'i386_defconfig' # # configuration written to .config # make[1]: Leaving directory '/workspace/kernel/build64-default/build32' + cd /workspace/kernel/build64-default/build32 + /workspace/kernel/scripts/kconfig/merge_config.sh .config /workspace/ci/kernel/fragments/10-xe.fragment Using .config as base Merging /workspace/ci/kernel/fragments/10-xe.fragment Value of CONFIG_DRM_XE is redefined by fragment /workspace/ci/kernel/fragments/10-xe.fragment: Previous value: # CONFIG_DRM_XE is not set New value: CONFIG_DRM_XE=m GEN Makefile WARNING: unmet direct dependencies detected for FB_IOMEM_HELPERS Depends on [n]: HAS_IOMEM [=y] && FB_CORE [=n] Selected by [m]: - DRM_XE_DISPLAY [=y] && HAS_IOMEM [=y] && DRM [=y] && DRM_XE [=m] && DRM_XE [=m]=m [=m] && HAS_IOPORT [=y] # # configuration written to .config # Value requested for CONFIG_HAVE_UID16 not in final .config Requested value: CONFIG_HAVE_UID16=y Actual value: Value requested for CONFIG_UID16 not in final .config Requested value: CONFIG_UID16=y Actual value: Value requested for CONFIG_X86_32 not in final .config Requested value: CONFIG_X86_32=y Actual value: Value requested for CONFIG_OUTPUT_FORMAT not in final .config Requested value: CONFIG_OUTPUT_FORMAT="elf32-i386" Actual value: CONFIG_OUTPUT_FORMAT="elf64-x86-64" Value requested for CONFIG_ARCH_MMAP_RND_BITS_MIN not in final .config Requested value: CONFIG_ARCH_MMAP_RND_BITS_MIN=8 Actual value: CONFIG_ARCH_MMAP_RND_BITS_MIN=28 Value requested for CONFIG_ARCH_MMAP_RND_BITS_MAX not in final .config Requested value: CONFIG_ARCH_MMAP_RND_BITS_MAX=16 Actual value: CONFIG_ARCH_MMAP_RND_BITS_MAX=32 Value requested for CONFIG_PGTABLE_LEVELS not in final .config Requested value: CONFIG_PGTABLE_LEVELS=2 Actual value: CONFIG_PGTABLE_LEVELS=5 Value requested for CONFIG_X86_BIGSMP not in final .config Requested value: # CONFIG_X86_BIGSMP is not set Actual value: Value requested for CONFIG_X86_INTEL_QUARK not in final .config Requested value: # CONFIG_X86_INTEL_QUARK is not set Actual value: Value requested for CONFIG_X86_RDC321X not in final .config Requested value: # CONFIG_X86_RDC321X is not set Actual value: Value requested for CONFIG_X86_32_NON_STANDARD not in final .config Requested value: # CONFIG_X86_32_NON_STANDARD is not set Actual value: Value requested for CONFIG_X86_32_IRIS not in final .config Requested value: # CONFIG_X86_32_IRIS is not set Actual value: Value requested for CONFIG_M486SX not in final .config Requested value: # CONFIG_M486SX is not set Actual value: Value requested for CONFIG_M486 not in final .config Requested value: # CONFIG_M486 is not set Actual value: Value requested for CONFIG_M586 not in final .config Requested value: # CONFIG_M586 is not set Actual value: Value requested for CONFIG_M586TSC not in final .config Requested value: # CONFIG_M586TSC is not set Actual value: Value requested for CONFIG_M586MMX not in final .config Requested value: # CONFIG_M586MMX is not set Actual value: Value requested for CONFIG_M686 not in final .config Requested value: CONFIG_M686=y Actual value: Value requested for CONFIG_MPENTIUMII not in final .config Requested value: # CONFIG_MPENTIUMII is not set Actual value: Value requested for CONFIG_MPENTIUMIII not in final .config Requested value: # CONFIG_MPENTIUMIII is not set Actual value: Value requested for CONFIG_MPENTIUMM not in final .config Requested value: # CONFIG_MPENTIUMM is not set Actual value: Value requested for CONFIG_MPENTIUM4 not in final .config Requested value: # CONFIG_MPENTIUM4 is not set Actual value: Value requested for CONFIG_MK6 not in final .config Requested value: # CONFIG_MK6 is not set Actual value: Value requested for CONFIG_MK7 not in final .config Requested value: # CONFIG_MK7 is not set Actual value: Value requested for CONFIG_MCRUSOE not in final .config Requested value: # CONFIG_MCRUSOE is not set Actual value: Value requested for CONFIG_MEFFICEON not in final .config Requested value: # CONFIG_MEFFICEON is not set Actual value: Value requested for CONFIG_MWINCHIPC6 not in final .config Requested value: # CONFIG_MWINCHIPC6 is not set Actual value: Value requested for CONFIG_MWINCHIP3D not in final .config Requested value: # CONFIG_MWINCHIP3D is not set Actual value: Value requested for CONFIG_MELAN not in final .config Requested value: # CONFIG_MELAN is not set Actual value: Value requested for CONFIG_MGEODEGX1 not in final .config Requested value: # CONFIG_MGEODEGX1 is not set Actual value: Value requested for CONFIG_MGEODE_LX not in final .config Requested value: # CONFIG_MGEODE_LX is not set Actual value: Value requested for CONFIG_MCYRIXIII not in final .config Requested value: # CONFIG_MCYRIXIII is not set Actual value: Value requested for CONFIG_MVIAC3_2 not in final .config Requested value: # CONFIG_MVIAC3_2 is not set Actual value: Value requested for CONFIG_MVIAC7 not in final .config Requested value: # CONFIG_MVIAC7 is not set Actual value: Value requested for CONFIG_X86_GENERIC not in final .config Requested value: # CONFIG_X86_GENERIC is not set Actual value: Value requested for CONFIG_X86_INTERNODE_CACHE_SHIFT not in final .config Requested value: CONFIG_X86_INTERNODE_CACHE_SHIFT=5 Actual value: CONFIG_X86_INTERNODE_CACHE_SHIFT=6 Value requested for CONFIG_X86_L1_CACHE_SHIFT not in final .config Requested value: CONFIG_X86_L1_CACHE_SHIFT=5 Actual value: CONFIG_X86_L1_CACHE_SHIFT=6 Value requested for CONFIG_X86_USE_PPRO_CHECKSUM not in final .config Requested value: CONFIG_X86_USE_PPRO_CHECKSUM=y Actual value: Value requested for CONFIG_X86_MINIMUM_CPU_FAMILY not in final .config Requested value: CONFIG_X86_MINIMUM_CPU_FAMILY=6 Actual value: CONFIG_X86_MINIMUM_CPU_FAMILY=64 Value requested for CONFIG_CPU_SUP_TRANSMETA_32 not in final .config Requested value: CONFIG_CPU_SUP_TRANSMETA_32=y Actual value: Value requested for CONFIG_CPU_SUP_VORTEX_32 not in final .config Requested value: CONFIG_CPU_SUP_VORTEX_32=y Actual value: Value requested for CONFIG_HPET_TIMER not in final .config Requested value: # CONFIG_HPET_TIMER is not set Actual value: CONFIG_HPET_TIMER=y Value requested for CONFIG_NR_CPUS_RANGE_END not in final .config Requested value: CONFIG_NR_CPUS_RANGE_END=8 Actual value: CONFIG_NR_CPUS_RANGE_END=512 Value requested for CONFIG_NR_CPUS_DEFAULT not in final .config Requested value: CONFIG_NR_CPUS_DEFAULT=8 Actual value: CONFIG_NR_CPUS_DEFAULT=64 Value requested for CONFIG_X86_ANCIENT_MCE not in final .config Requested value: # CONFIG_X86_ANCIENT_MCE is not set Actual value: Value requested for CONFIG_X86_LEGACY_VM86 not in final .config Requested value: # CONFIG_X86_LEGACY_VM86 is not set Actual value: Value requested for CONFIG_X86_ESPFIX32 not in final .config Requested value: CONFIG_X86_ESPFIX32=y Actual value: Value requested for CONFIG_TOSHIBA not in final .config Requested value: # CONFIG_TOSHIBA is not set Actual value: Value requested for CONFIG_X86_REBOOTFIXUPS not in final .config Requested value: # CONFIG_X86_REBOOTFIXUPS is not set Actual value: Value requested for CONFIG_MICROCODE_INITRD32 not in final .config Requested value: CONFIG_MICROCODE_INITRD32=y Actual value: Value requested for CONFIG_NOHIGHMEM not in final .config Requested value: # CONFIG_NOHIGHMEM is not set Actual value: Value requested for CONFIG_HIGHMEM4G not in final .config Requested value: CONFIG_HIGHMEM4G=y Actual value: Value requested for CONFIG_HIGHMEM64G not in final .config Requested value: # CONFIG_HIGHMEM64G is not set Actual value: Value requested for CONFIG_VMSPLIT_3G not in final .config Requested value: CONFIG_VMSPLIT_3G=y Actual value: Value requested for CONFIG_VMSPLIT_3G_OPT not in final .config Requested value: # CONFIG_VMSPLIT_3G_OPT is not set Actual value: Value requested for CONFIG_VMSPLIT_2G not in final .config Requested value: # CONFIG_VMSPLIT_2G is not set Actual value: Value requested for CONFIG_VMSPLIT_2G_OPT not in final .config Requested value: # CONFIG_VMSPLIT_2G_OPT is not set Actual value: Value requested for CONFIG_VMSPLIT_1G not in final .config Requested value: # CONFIG_VMSPLIT_1G is not set Actual value: Value requested for CONFIG_PAGE_OFFSET not in final .config Requested value: CONFIG_PAGE_OFFSET=0xC0000000 Actual value: Value requested for CONFIG_HIGHMEM not in final .config Requested value: CONFIG_HIGHMEM=y Actual value: Value requested for CONFIG_X86_PAE not in final .config Requested value: # CONFIG_X86_PAE is not set Actual value: Value requested for CONFIG_ARCH_FLATMEM_ENABLE not in final .config Requested value: CONFIG_ARCH_FLATMEM_ENABLE=y Actual value: Value requested for CONFIG_ARCH_SELECT_MEMORY_MODEL not in final .config Requested value: CONFIG_ARCH_SELECT_MEMORY_MODEL=y Actual value: Value requested for CONFIG_ILLEGAL_POINTER_VALUE not in final .config Requested value: CONFIG_ILLEGAL_POINTER_VALUE=0 Actual value: CONFIG_ILLEGAL_POINTER_VALUE=0xdead000000000000 Value requested for CONFIG_HIGHPTE not in final .config Requested value: # CONFIG_HIGHPTE is not set Actual value: Value requested for CONFIG_COMPAT_VDSO not in final .config Requested value: # CONFIG_COMPAT_VDSO is not set Actual value: Value requested for CONFIG_FUNCTION_PADDING_CFI not in final .config Requested value: CONFIG_FUNCTION_PADDING_CFI=0 Actual value: CONFIG_FUNCTION_PADDING_CFI=11 Value requested for CONFIG_FUNCTION_PADDING_BYTES not in final .config Requested value: CONFIG_FUNCTION_PADDING_BYTES=4 Actual value: CONFIG_FUNCTION_PADDING_BYTES=16 Value requested for CONFIG_APM not in final .config Requested value: # CONFIG_APM is not set Actual value: Value requested for CONFIG_X86_POWERNOW_K6 not in final .config Requested value: # CONFIG_X86_POWERNOW_K6 is not set Actual value: Value requested for CONFIG_X86_POWERNOW_K7 not in final .config Requested value: # CONFIG_X86_POWERNOW_K7 is not set Actual value: Value requested for CONFIG_X86_GX_SUSPMOD not in final .config Requested value: # CONFIG_X86_GX_SUSPMOD is not set Actual value: Value requested for CONFIG_X86_SPEEDSTEP_ICH not in final .config Requested value: # CONFIG_X86_SPEEDSTEP_ICH is not set Actual value: Value requested for CONFIG_X86_SPEEDSTEP_SMI not in final .config Requested value: # CONFIG_X86_SPEEDSTEP_SMI is not set Actual value: Value requested for CONFIG_X86_CPUFREQ_NFORCE2 not in final .config Requested value: # CONFIG_X86_CPUFREQ_NFORCE2 is not set Actual value: Value requested for CONFIG_X86_LONGRUN not in final .config Requested value: # CONFIG_X86_LONGRUN is not set Actual value: Value requested for CONFIG_X86_LONGHAUL not in final .config Requested value: # CONFIG_X86_LONGHAUL is not set Actual value: Value requested for CONFIG_X86_E_POWERSAVER not in final .config Requested value: # CONFIG_X86_E_POWERSAVER is not set Actual value: Value requested for CONFIG_PCI_GOBIOS not in final .config Requested value: # CONFIG_PCI_GOBIOS is not set Actual value: Value requested for CONFIG_PCI_GOMMCONFIG not in final .config Requested value: # CONFIG_PCI_GOMMCONFIG is not set Actual value: Value requested for CONFIG_PCI_GODIRECT not in final .config Requested value: # CONFIG_PCI_GODIRECT is not set Actual value: Value requested for CONFIG_PCI_GOANY not in final .config Requested value: CONFIG_PCI_GOANY=y Actual value: Value requested for CONFIG_PCI_BIOS not in final .config Requested value: CONFIG_PCI_BIOS=y Actual value: Value requested for CONFIG_ISA not in final .config Requested value: # CONFIG_ISA is not set Actual value: Value requested for CONFIG_SCx200 not in final .config Requested value: # CONFIG_SCx200 is not set Actual value: Value requested for CONFIG_OLPC not in final .config Requested value: # CONFIG_OLPC is not set Actual value: Value requested for CONFIG_ALIX not in final .config Requested value: # CONFIG_ALIX is not set Actual value: Value requested for CONFIG_NET5501 not in final .config Requested value: # CONFIG_NET5501 is not set Actual value: Value requested for CONFIG_GEOS not in final .config Requested value: # CONFIG_GEOS is not set Actual value: Value requested for CONFIG_COMPAT_32 not in final .config Requested value: CONFIG_COMPAT_32=y Actual value: Value requested for CONFIG_HAVE_ATOMIC_IOMAP not in final .config Requested value: CONFIG_HAVE_ATOMIC_IOMAP=y Actual value: Value requested for CONFIG_ARCH_32BIT_OFF_T not in final .config Requested value: CONFIG_ARCH_32BIT_OFF_T=y Actual value: Value requested for CONFIG_ARCH_WANT_IPC_PARSE_VERSION not in final .config Requested value: CONFIG_ARCH_WANT_IPC_PARSE_VERSION=y Actual value: Value requested for CONFIG_MODULES_USE_ELF_REL not in final .config Requested value: CONFIG_MODULES_USE_ELF_REL=y Actual value: Value requested for CONFIG_ARCH_MMAP_RND_BITS not in final .config Requested value: CONFIG_ARCH_MMAP_RND_BITS=8 Actual value: CONFIG_ARCH_MMAP_RND_BITS=28 Value requested for CONFIG_CLONE_BACKWARDS not in final .config Requested value: CONFIG_CLONE_BACKWARDS=y Actual value: Value requested for CONFIG_OLD_SIGSUSPEND3 not in final .config Requested value: CONFIG_OLD_SIGSUSPEND3=y Actual value: Value requested for CONFIG_OLD_SIGACTION not in final .config Requested value: CONFIG_OLD_SIGACTION=y Actual value: Value requested for CONFIG_ARCH_SPLIT_ARG64 not in final .config Requested value: CONFIG_ARCH_SPLIT_ARG64=y Actual value: Value requested for CONFIG_FUNCTION_ALIGNMENT not in final .config Requested value: CONFIG_FUNCTION_ALIGNMENT=4 Actual value: CONFIG_FUNCTION_ALIGNMENT=16 Value requested for CONFIG_SELECT_MEMORY_MODEL not in final .config Requested value: CONFIG_SELECT_MEMORY_MODEL=y Actual value: Value requested for CONFIG_FLATMEM_MANUAL not in final .config Requested value: CONFIG_FLATMEM_MANUAL=y Actual value: Value requested for CONFIG_SPARSEMEM_MANUAL not in final .config Requested value: # CONFIG_SPARSEMEM_MANUAL is not set Actual value: Value requested for CONFIG_FLATMEM not in final .config Requested value: CONFIG_FLATMEM=y Actual value: Value requested for CONFIG_SPARSEMEM_STATIC not in final .config Requested value: CONFIG_SPARSEMEM_STATIC=y Actual value: Value requested for CONFIG_BOUNCE not in final .config Requested value: CONFIG_BOUNCE=y Actual value: Value requested for CONFIG_KMAP_LOCAL not in final .config Requested value: CONFIG_KMAP_LOCAL=y Actual value: Value requested for CONFIG_HOTPLUG_PCI_COMPAQ not in final .config Requested value: # CONFIG_HOTPLUG_PCI_COMPAQ is not set Actual value: Value requested for CONFIG_HOTPLUG_PCI_IBM not in final .config Requested value: # CONFIG_HOTPLUG_PCI_IBM is not set Actual value: Value requested for CONFIG_EFI_CAPSULE_QUIRK_QUARK_CSH not in final .config Requested value: CONFIG_EFI_CAPSULE_QUIRK_QUARK_CSH=y Actual value: Value requested for CONFIG_PCH_PHUB not in final .config Requested value: # CONFIG_PCH_PHUB is not set Actual value: Value requested for CONFIG_SCSI_NSP32 not in final .config Requested value: # CONFIG_SCSI_NSP32 is not set Actual value: Value requested for CONFIG_PATA_CS5520 not in final .config Requested value: # CONFIG_PATA_CS5520 is not set Actual value: Value requested for CONFIG_PATA_CS5530 not in final .config Requested value: # CONFIG_PATA_CS5530 is not set Actual value: Value requested for CONFIG_PATA_CS5535 not in final .config Requested value: # CONFIG_PATA_CS5535 is not set Actual value: Value requested for CONFIG_PATA_CS5536 not in final .config Requested value: # CONFIG_PATA_CS5536 is not set Actual value: Value requested for CONFIG_PATA_SC1200 not in final .config Requested value: # CONFIG_PATA_SC1200 is not set Actual value: Value requested for CONFIG_PCH_GBE not in final .config Requested value: # CONFIG_PCH_GBE is not set Actual value: Value requested for CONFIG_INPUT_WISTRON_BTNS not in final .config Requested value: # CONFIG_INPUT_WISTRON_BTNS is not set Actual value: Value requested for CONFIG_SERIAL_TIMBERDALE not in final .config Requested value: # CONFIG_SERIAL_TIMBERDALE is not set Actual value: Value requested for CONFIG_SERIAL_PCH_UART not in final .config Requested value: # CONFIG_SERIAL_PCH_UART is not set Actual value: Value requested for CONFIG_HW_RANDOM_GEODE not in final .config Requested value: CONFIG_HW_RANDOM_GEODE=y Actual value: Value requested for CONFIG_SONYPI not in final .config Requested value: # CONFIG_SONYPI is not set Actual value: Value requested for CONFIG_PC8736x_GPIO not in final .config Requested value: # CONFIG_PC8736x_GPIO is not set Actual value: Value requested for CONFIG_NSC_GPIO not in final .config Requested value: # CONFIG_NSC_GPIO is not set Actual value: Value requested for CONFIG_I2C_EG20T not in final .config Requested value: # CONFIG_I2C_EG20T is not set Actual value: Value requested for CONFIG_SCx200_ACB not in final .config Requested value: # CONFIG_SCx200_ACB is not set Actual value: Value requested for CONFIG_PTP_1588_CLOCK_PCH not in final .config Requested value: # CONFIG_PTP_1588_CLOCK_PCH is not set Actual value: Value requested for CONFIG_SBC8360_WDT not in final .config Requested value: # CONFIG_SBC8360_WDT is not set Actual value: Value requested for CONFIG_SBC7240_WDT not in final .config Requested value: # CONFIG_SBC7240_WDT is not set Actual value: Value requested for CONFIG_MFD_CS5535 not in final .config Requested value: # CONFIG_MFD_CS5535 is not set Actual value: Value requested for CONFIG_AGP_ALI not in final .config Requested value: # CONFIG_AGP_ALI is not set Actual value: Value requested for CONFIG_AGP_ATI not in final .config Requested value: # CONFIG_AGP_ATI is not set Actual value: Value requested for CONFIG_AGP_AMD not in final .config Requested value: # CONFIG_AGP_AMD is not set Actual value: Value requested for CONFIG_AGP_NVIDIA not in final .config Requested value: # CONFIG_AGP_NVIDIA is not set Actual value: Value requested for CONFIG_AGP_SWORKS not in final .config Requested value: # CONFIG_AGP_SWORKS is not set Actual value: Value requested for CONFIG_AGP_EFFICEON not in final .config Requested value: # CONFIG_AGP_EFFICEON is not set Actual value: Value requested for CONFIG_SND_CS5530 not in final .config Requested value: # CONFIG_SND_CS5530 is not set Actual value: Value requested for CONFIG_SND_CS5535AUDIO not in final .config Requested value: # CONFIG_SND_CS5535AUDIO is not set Actual value: Value requested for CONFIG_SND_SIS7019 not in final .config Requested value: # CONFIG_SND_SIS7019 is not set Actual value: Value requested for CONFIG_LEDS_OT200 not in final .config Requested value: # CONFIG_LEDS_OT200 is not set Actual value: Value requested for CONFIG_PCH_DMA not in final .config Requested value: # CONFIG_PCH_DMA is not set Actual value: Value requested for CONFIG_CLKSRC_I8253 not in final .config Requested value: CONFIG_CLKSRC_I8253=y Actual value: Value requested for CONFIG_MAILBOX not in final .config Requested value: # CONFIG_MAILBOX is not set Actual value: CONFIG_MAILBOX=y Value requested for CONFIG_CRYPTO_SERPENT_SSE2_586 not in final .config Requested value: # CONFIG_CRYPTO_SERPENT_SSE2_586 is not set Actual value: Value requested for CONFIG_CRYPTO_TWOFISH_586 not in final .config Requested value: # CONFIG_CRYPTO_TWOFISH_586 is not set Actual value: Value requested for CONFIG_CRYPTO_DEV_GEODE not in final .config Requested value: # CONFIG_CRYPTO_DEV_GEODE is not set Actual value: Value requested for CONFIG_CRYPTO_DEV_HIFN_795X not in final .config Requested value: # CONFIG_CRYPTO_DEV_HIFN_795X is not set Actual value: Value requested for CONFIG_CRYPTO_LIB_POLY1305_RSIZE not in final .config Requested value: CONFIG_CRYPTO_LIB_POLY1305_RSIZE=1 Actual value: CONFIG_CRYPTO_LIB_POLY1305_RSIZE=11 Value requested for CONFIG_AUDIT_GENERIC not in final .config Requested value: CONFIG_AUDIT_GENERIC=y Actual value: Value requested for CONFIG_GENERIC_VDSO_32 not in final .config Requested value: CONFIG_GENERIC_VDSO_32=y Actual value: Value requested for CONFIG_DEBUG_KMAP_LOCAL not in final .config Requested value: # CONFIG_DEBUG_KMAP_LOCAL is not set Actual value: Value requested for CONFIG_DEBUG_HIGHMEM not in final .config Requested value: # CONFIG_DEBUG_HIGHMEM is not set Actual value: Value requested for CONFIG_HAVE_DEBUG_STACKOVERFLOW not in final .config Requested value: CONFIG_HAVE_DEBUG_STACKOVERFLOW=y Actual value: Value requested for CONFIG_DEBUG_STACKOVERFLOW not in final .config Requested value: # CONFIG_DEBUG_STACKOVERFLOW is not set Actual value: Value requested for CONFIG_HAVE_FUNCTION_GRAPH_TRACER not in final .config Requested value: CONFIG_HAVE_FUNCTION_GRAPH_TRACER=y Actual value: Value requested for CONFIG_HAVE_FUNCTION_GRAPH_RETVAL not in final .config Requested value: CONFIG_HAVE_FUNCTION_GRAPH_RETVAL=y Actual value: Value requested for CONFIG_DRM_KUNIT_TEST not in final .config Requested value: CONFIG_DRM_KUNIT_TEST=m Actual value: Value requested for CONFIG_DRM_XE_WERROR not in final .config Requested value: CONFIG_DRM_XE_WERROR=y Actual value: Value requested for CONFIG_DRM_XE_DEBUG not in final .config Requested value: CONFIG_DRM_XE_DEBUG=y Actual value: Value requested for CONFIG_DRM_XE_DEBUG_MEM not in final .config Requested value: CONFIG_DRM_XE_DEBUG_MEM=y Actual value: Value requested for CONFIG_DRM_XE_KUNIT_TEST not in final .config Requested value: CONFIG_DRM_XE_KUNIT_TEST=m Actual value: ++ nproc + make -j48 ARCH=i386 olddefconfig GEN Makefile WARNING: unmet direct dependencies detected for FB_IOMEM_HELPERS Depends on [n]: HAS_IOMEM [=y] && FB_CORE [=n] Selected by [m]: - DRM_XE_DISPLAY [=y] && HAS_IOMEM [=y] && DRM [=y] && DRM_XE [=m] && DRM_XE [=m]=m [=m] && HAS_IOPORT [=y] # # configuration written to .config # ++ nproc + make -j48 ARCH=i386 SYNC include/config/auto.conf.cmd GEN Makefile WARNING: unmet direct dependencies detected for FB_IOMEM_HELPERS Depends on [n]: HAS_IOMEM [=y] && FB_CORE [=n] Selected by [m]: - DRM_XE_DISPLAY [=y] && HAS_IOMEM [=y] && DRM [=y] && DRM_XE [=m] && DRM_XE [=m]=m [=m] && HAS_IOPORT [=y] WARNING: unmet direct dependencies detected for FB_IOMEM_HELPERS Depends on [n]: HAS_IOMEM [=y] && FB_CORE [=n] Selected by [m]: - DRM_XE_DISPLAY [=y] && HAS_IOMEM [=y] && DRM [=y] && DRM_XE [=m] && DRM_XE [=m]=m [=m] && HAS_IOPORT [=y] WARNING: unmet direct dependencies detected for FB_IOMEM_HELPERS Depends on [n]: HAS_IOMEM [=y] && FB_CORE [=n] Selected by [m]: - DRM_XE_DISPLAY [=y] && HAS_IOMEM [=y] && DRM [=y] && DRM_XE [=m] && DRM_XE [=m]=m [=m] && HAS_IOPORT [=y] GEN Makefile WRAP arch/x86/include/generated/uapi/asm/bpf_perf_event.h WRAP arch/x86/include/generated/uapi/asm/errno.h WRAP arch/x86/include/generated/uapi/asm/ioctl.h WRAP arch/x86/include/generated/uapi/asm/fcntl.h WRAP arch/x86/include/generated/uapi/asm/ioctls.h WRAP arch/x86/include/generated/uapi/asm/ipcbuf.h UPD include/generated/uapi/linux/version.h SYSHDR arch/x86/include/generated/uapi/asm/unistd_32.h WRAP arch/x86/include/generated/uapi/asm/param.h SYSHDR arch/x86/include/generated/uapi/asm/unistd_64.h WRAP arch/x86/include/generated/uapi/asm/poll.h SYSHDR arch/x86/include/generated/uapi/asm/unistd_x32.h WRAP arch/x86/include/generated/uapi/asm/resource.h WRAP arch/x86/include/generated/uapi/asm/socket.h SYSTBL arch/x86/include/generated/asm/syscalls_32.h WRAP arch/x86/include/generated/uapi/asm/sockios.h WRAP arch/x86/include/generated/uapi/asm/termbits.h WRAP arch/x86/include/generated/uapi/asm/termios.h WRAP arch/x86/include/generated/uapi/asm/types.h UPD include/generated/compile.h HOSTCC arch/x86/tools/relocs_32.o HOSTCC arch/x86/tools/relocs_64.o HOSTCC arch/x86/tools/relocs_common.o WRAP arch/x86/include/generated/asm/early_ioremap.h WRAP arch/x86/include/generated/asm/mcs_spinlock.h WRAP arch/x86/include/generated/asm/mmzone.h WRAP arch/x86/include/generated/asm/irq_regs.h WRAP arch/x86/include/generated/asm/kmap_size.h WRAP arch/x86/include/generated/asm/local64.h WRAP arch/x86/include/generated/asm/mmiowb.h WRAP arch/x86/include/generated/asm/module.lds.h WRAP arch/x86/include/generated/asm/rwonce.h HOSTCC scripts/kallsyms HOSTCC scripts/sorttable HOSTCC scripts/asn1_compiler HOSTCC scripts/selinux/mdp/mdp HOSTLD arch/x86/tools/relocs UPD include/config/kernel.release UPD include/generated/utsrelease.h CC scripts/mod/empty.o HOSTCC scripts/mod/mk_elfconfig CC scripts/mod/devicetable-offsets.s UPD scripts/mod/devicetable-offsets.h MKELF scripts/mod/elfconfig.h HOSTCC scripts/mod/modpost.o HOSTCC scripts/mod/sumversion.o HOSTCC scripts/mod/file2alias.o HOSTCC scripts/mod/symsearch.o HOSTLD scripts/mod/modpost CC kernel/bounds.s CHKSHA1 /workspace/kernel/include/linux/atomic/atomic-arch-fallback.h CHKSHA1 /workspace/kernel/include/linux/atomic/atomic-long.h CHKSHA1 /workspace/kernel/include/linux/atomic/atomic-instrumented.h UPD include/generated/timeconst.h UPD include/generated/bounds.h CC arch/x86/kernel/asm-offsets.s UPD include/generated/asm-offsets.h CALL /workspace/kernel/scripts/checksyscalls.sh LDS scripts/module.lds CC init/main.o HOSTCC usr/gen_init_cpio CC init/do_mounts.o CC certs/system_keyring.o CC mm/filemap.o UPD init/utsversion-tmp.h CC init/do_mounts_initrd.o CC ipc/util.o CC mm/mempool.o CC ipc/msgutil.o CC init/initramfs.o CC mm/oom_kill.o CC security/commoncap.o CC ipc/msg.o CC init/calibrate.o CC io_uring/io_uring.o CC mm/fadvise.o CC ipc/sem.o CC security/lsm_syscalls.o CC block/bdev.o CC arch/x86/realmode/init.o CC arch/x86/pci/i386.o AS arch/x86/lib/atomic64_cx8_32.o CC arch/x86/power/cpu.o AR arch/x86/crypto/built-in.a CC security/keys/gc.o CC arch/x86/video/video-common.o AR arch/x86/net/built-in.a CC security/integrity/iint.o HOSTCC security/selinux/genheaders CC block/partitions/core.o CC arch/x86/events/amd/core.o AR virt/lib/built-in.a CC arch/x86/events/zhaoxin/core.o CC fs/nfs_common/nfsacl.o CC arch/x86/events/intel/core.o AR arch/x86/entry/vsyscall/built-in.a AR arch/x86/platform/atom/built-in.a CC arch/x86/mm/pat/set_memory.o AR drivers/cache/built-in.a CC net/core/sock.o AR virt/built-in.a CC fs/notify/dnotify/dnotify.o CC lib/math/div64.o CC arch/x86/virt/svm/cmdline.o CC arch/x86/kernel/fpu/init.o AS arch/x86/lib/checksum_32.o CC sound/core/seq/seq.o AR arch/x86/virt/vmx/built-in.a AR arch/x86/platform/ce4100/built-in.a AR drivers/irqchip/built-in.a CC arch/x86/lib/cmdline.o CC block/partitions/msdos.o CC lib/crypto/mpi/generic_mpih-lshift.o CC arch/x86/entry/vdso/vma.o CC arch/x86/platform/efi/memmap.o CC kernel/sched/core.o AR drivers/bus/mhi/built-in.a AR sound/i2c/other/built-in.a AR drivers/bus/built-in.a AR sound/i2c/built-in.a AR sound/drivers/opl3/built-in.a AR sound/drivers/opl4/built-in.a AR drivers/pwm/built-in.a CC fs/notify/inotify/inotify_fsnotify.o CC crypto/asymmetric_keys/asymmetric_type.o AR sound/drivers/mpu401/built-in.a AR drivers/leds/trigger/built-in.a AR sound/drivers/vx/built-in.a AR drivers/leds/blink/built-in.a AR sound/drivers/pcsp/built-in.a AR arch/x86/virt/svm/built-in.a AR drivers/leds/simple/built-in.a AR sound/drivers/built-in.a CC drivers/leds/led-core.o AR arch/x86/virt/built-in.a AS arch/x86/lib/cmpxchg8b_emu.o AR fs/notify/fanotify/built-in.a CC arch/x86/lib/cpu.o CC arch/x86/kernel/cpu/mce/core.o CC arch/x86/kernel/acpi/boot.o CC lib/math/gcd.o GEN security/selinux/flask.h security/selinux/av_permissions.h CC security/selinux/avc.o CC lib/math/lcm.o CC lib/math/int_log.o CC arch/x86/kernel/cpu/mtrr/mtrr.o GEN usr/initramfs_data.cpio COPY usr/initramfs_inc_data AS usr/initramfs_data.o CC lib/math/int_pow.o CC arch/x86/kernel/fpu/bugs.o HOSTCC certs/extract-cert AR usr/built-in.a CC fs/notify/inotify/inotify_user.o CC lib/math/int_sqrt.o CC arch/x86/kernel/fpu/core.o CC arch/x86/lib/delay.o CC lib/math/reciprocal_div.o CC sound/core/seq/seq_lock.o CC arch/x86/kernel/fpu/regset.o CC lib/crypto/mpi/generic_mpih-mul1.o AS arch/x86/realmode/rm/header.o AS arch/x86/realmode/rm/trampoline_32.o AS arch/x86/realmode/rm/stack.o AR arch/x86/video/built-in.a CC arch/x86/kernel/fpu/signal.o CC lib/math/rational.o AS arch/x86/realmode/rm/reboot.o CC lib/crypto/memneq.o AS arch/x86/realmode/rm/wakeup_asm.o CC fs/nfs_common/grace.o CC drivers/leds/led-class.o CC security/integrity/integrity_audit.o CC arch/x86/mm/init.o CC arch/x86/realmode/rm/wakemain.o CERT certs/x509_certificate_list CERT certs/signing_key.x509 AS certs/system_certificates.o CC arch/x86/pci/init.o CC fs/iomap/trace.o CC arch/x86/kernel/cpu/microcode/core.o CC crypto/asymmetric_keys/restrict.o AR certs/built-in.a CC fs/iomap/iter.o AR fs/notify/dnotify/built-in.a CC arch/x86/entry/vdso/extable.o CC drivers/leds/led-triggers.o CC arch/x86/kernel/cpu/cacheinfo.o CC arch/x86/realmode/rm/video-mode.o CC arch/x86/power/hibernate_32.o CC arch/x86/kernel/cpu/mce/severity.o CC security/keys/key.o AS arch/x86/lib/getuser.o CC arch/x86/platform/efi/quirks.o CC block/partitions/efi.o GEN arch/x86/lib/inat-tables.c AR arch/x86/events/zhaoxin/built-in.a CC arch/x86/kernel/cpu/mce/genpool.o CC arch/x86/lib/insn-eval.o AS arch/x86/realmode/rm/copy.o CC sound/core/seq/seq_clientmgr.o AS arch/x86/realmode/rm/bioscall.o CC arch/x86/realmode/rm/regs.o CC arch/x86/events/intel/bts.o AR lib/math/built-in.a CC arch/x86/kernel/cpu/scattered.o CC arch/x86/kernel/apic/apic.o CC arch/x86/realmode/rm/video-vga.o CC arch/x86/kernel/cpu/mtrr/if.o CC arch/x86/pci/pcbios.o CC net/ethernet/eth.o CC fs/iomap/buffered-io.o CC arch/x86/realmode/rm/video-vesa.o CC io_uring/opdef.o CC crypto/asymmetric_keys/signature.o CC lib/crypto/mpi/generic_mpih-mul2.o CC arch/x86/events/amd/lbr.o AR arch/x86/platform/geode/built-in.a CC arch/x86/realmode/rm/video-bios.o CC lib/crypto/mpi/generic_mpih-mul3.o CC crypto/api.o CC arch/x86/kernel/acpi/sleep.o PASYMS arch/x86/realmode/rm/pasyms.h AR fs/notify/inotify/built-in.a CC fs/notify/fsnotify.o CC arch/x86/mm/pat/memtype.o LDS arch/x86/realmode/rm/realmode.lds LD arch/x86/realmode/rm/realmode.elf RELOCS arch/x86/realmode/rm/realmode.relocs OBJCOPY arch/x86/realmode/rm/realmode.bin AS arch/x86/realmode/rmpiggy.o AS arch/x86/power/hibernate_asm_32.o AR arch/x86/realmode/built-in.a CC fs/notify/notification.o CC fs/notify/group.o CC fs/notify/mark.o CC fs/nfs_common/common.o CC kernel/locking/mutex.o AR security/integrity/built-in.a CC arch/x86/kernel/cpu/microcode/intel.o CC kernel/sched/fair.o AR drivers/leds/built-in.a CC arch/x86/events/amd/ibs.o CC arch/x86/power/hibernate.o CC mm/maccess.o CC init/init_task.o CC drivers/pci/msi/pcidev_msi.o CC kernel/locking/semaphore.o LDS arch/x86/entry/vdso/vdso32/vdso32.lds CC drivers/pci/pcie/portdrv.o AS arch/x86/entry/vdso/vdso32/note.o AS arch/x86/entry/vdso/vdso32/system_call.o AS arch/x86/entry/vdso/vdso32/sigreturn.o CC arch/x86/entry/vdso/vdso32/vclock_gettime.o CC crypto/asymmetric_keys/public_key.o CC arch/x86/kernel/fpu/xstate.o CC arch/x86/kernel/cpu/mtrr/generic.o CC arch/x86/kernel/cpu/mtrr/cleanup.o CC ipc/shm.o CC fs/notify/fdinfo.o AR block/partitions/built-in.a CC block/fops.o CC arch/x86/lib/insn.o CC arch/x86/platform/efi/efi.o AR drivers/pci/pwrctrl/built-in.a CC security/selinux/hooks.o AS arch/x86/kernel/acpi/wakeup_32.o CC arch/x86/pci/mmconfig_32.o CC lib/crypto/mpi/generic_mpih-rshift.o CC lib/crypto/mpi/generic_mpih-sub1.o CC security/keys/keyring.o CC arch/x86/kernel/kprobes/core.o CC arch/x86/kernel/cpu/mce/intel.o CC arch/x86/kernel/cpu/mce/amd.o CC lib/zlib_inflate/inffast.o CC arch/x86/kernel/acpi/cstate.o CC arch/x86/platform/efi/efi_32.o AS arch/x86/platform/efi/efi_stub_32.o CC crypto/cipher.o CC lib/zlib_deflate/deflate.o CC block/bio.o CC arch/x86/lib/kaslr.o CC lib/crypto/mpi/generic_mpih-add1.o AR fs/nfs_common/built-in.a CC lib/zlib_inflate/inflate.o CC sound/core/seq/seq_memory.o CC arch/x86/mm/pat/memtype_interval.o CC drivers/pci/msi/api.o AR arch/x86/power/built-in.a CC init/version.o CC arch/x86/kernel/cpu/mtrr/amd.o ASN.1 crypto/asymmetric_keys/x509.asn1.[ch] CC sound/core/sound.o CC io_uring/kbuf.o CC lib/zlib_inflate/infutil.o AR net/802/built-in.a CC arch/x86/kernel/cpu/microcode/amd.o CC arch/x86/events/core.o CC arch/x86/lib/memcpy_32.o CC arch/x86/entry/vdso/vdso32/vgetcpu.o CC lib/zlib_inflate/inftrees.o ASN.1 crypto/asymmetric_keys/x509_akid.asn1.[ch] CC crypto/asymmetric_keys/x509_loader.o AS arch/x86/lib/memmove_32.o CC drivers/pci/pcie/rcec.o CC crypto/compress.o CC arch/x86/lib/misc.o HOSTCC arch/x86/entry/vdso/vdso2c AR fs/notify/built-in.a CC arch/x86/entry/vdso/vdso32-setup.o CC security/min_addr.o CC arch/x86/events/intel/ds.o CC arch/x86/lib/pc-conf-reg.o AR init/built-in.a AR net/ethernet/built-in.a CC arch/x86/kernel/kprobes/opt.o AS arch/x86/lib/putuser.o CC arch/x86/pci/direct.o AS arch/x86/lib/retpoline.o CC arch/x86/pci/mmconfig-shared.o CC arch/x86/pci/fixup.o AR arch/x86/kernel/acpi/built-in.a CC kernel/sched/build_policy.o CC lib/zlib_deflate/deftree.o CC crypto/asymmetric_keys/x509_public_key.o CC lib/crypto/utils.o CC arch/x86/lib/string_32.o CC net/core/request_sock.o CC lib/crypto/mpi/mpicoder.o CC lib/crypto/mpi/mpi-add.o CC arch/x86/lib/strstr_32.o CC lib/crypto/mpi/mpi-bit.o CC kernel/sched/build_utility.o CC lib/zlib_inflate/inflate_syms.o CC arch/x86/lib/usercopy.o CC arch/x86/platform/efi/runtime-map.o CC kernel/locking/rwsem.o CC arch/x86/kernel/apic/apic_common.o CC arch/x86/kernel/cpu/mtrr/cyrix.o VDSO arch/x86/entry/vdso/vdso32.so.dbg CC net/sched/sch_generic.o OBJCOPY arch/x86/entry/vdso/vdso32.so CC arch/x86/events/amd/uncore.o VDSO2C arch/x86/entry/vdso/vdso-image-32.c CC arch/x86/entry/vdso/vdso-image-32.o AR arch/x86/mm/pat/built-in.a CC arch/x86/mm/init_32.o CC drivers/pci/hotplug/pci_hotplug_core.o AR arch/x86/kernel/fpu/built-in.a CC mm/page-writeback.o CC arch/x86/pci/acpi.o CC lib/zlib_deflate/deflate_syms.o CC drivers/pci/pcie/bwctrl.o CC ipc/syscall.o AS arch/x86/entry/entry.o CC drivers/pci/msi/msi.o CC fs/quota/dquot.o CC sound/core/seq/seq_queue.o AS arch/x86/entry/entry_32.o CC net/sched/sch_mq.o CC arch/x86/lib/usercopy_32.o CC fs/iomap/direct-io.o CC security/keys/keyctl.o CC arch/x86/entry/syscall_32.o CC security/keys/permission.o AR lib/zlib_inflate/built-in.a CC drivers/video/console/dummycon.o AR arch/x86/entry/vdso/built-in.a AR drivers/idle/built-in.a CC lib/crypto/mpi/mpi-cmp.o ASN.1 crypto/asymmetric_keys/pkcs7.asn1.[ch] CC crypto/asymmetric_keys/pkcs7_trust.o CC security/keys/process_keys.o CC arch/x86/kernel/cpu/mtrr/centaur.o CC arch/x86/pci/legacy.o AR arch/x86/kernel/cpu/microcode/built-in.a CC arch/x86/kernel/apic/apic_noop.o CC arch/x86/entry/common.o CC arch/x86/kernel/apic/ipi.o AR lib/zlib_deflate/built-in.a AR drivers/char/ipmi/built-in.a CC mm/folio-compat.o AR arch/x86/kernel/kprobes/built-in.a CC block/elevator.o CC ipc/ipc_sysctl.o CC arch/x86/lib/msr-smp.o CC drivers/video/backlight/backlight.o CC lib/lzo/lzo1x_compress.o CC drivers/pci/hotplug/acpi_pcihp.o CC arch/x86/kernel/cpu/mtrr/legacy.o CC arch/x86/events/probe.o CC fs/quota/quota_v2.o CC arch/x86/kernel/cpu/mce/threshold.o CC crypto/asymmetric_keys/pkcs7_verify.o AR arch/x86/platform/efi/built-in.a AR arch/x86/platform/iris/built-in.a CC arch/x86/platform/intel/iosf_mbi.o CC kernel/locking/percpu-rwsem.o CC drivers/pci/pcie/aspm.o CC arch/x86/kernel/apic/vector.o CC arch/x86/lib/cache-smp.o CC arch/x86/kernel/apic/init.o CC lib/crypto/mpi/mpi-sub-ui.o CC arch/x86/kernel/apic/hw_nmi.o CC sound/core/seq/seq_fifo.o CC drivers/video/console/vgacon.o CC net/core/skbuff.o CC arch/x86/mm/fault.o CC lib/lzo/lzo1x_decompress_safe.o CC security/security.o CC net/sched/sch_frag.o AR arch/x86/kernel/cpu/mtrr/built-in.a AR arch/x86/platform/intel-mid/built-in.a CC arch/x86/mm/ioremap.o CC lib/crypto/chacha.o CC mm/readahead.o CC lib/crypto/aes.o CC arch/x86/lib/msr.o CC io_uring/rsrc.o CC arch/x86/pci/irq.o CC ipc/mqueue.o CC security/selinux/selinuxfs.o CC drivers/pci/msi/irqdomain.o AR arch/x86/events/amd/built-in.a CC arch/x86/events/intel/knc.o CC drivers/acpi/acpica/dsargs.o CC crypto/asymmetric_keys/x509.asn1.o CC crypto/asymmetric_keys/x509_akid.asn1.o CC crypto/asymmetric_keys/x509_cert_parser.o AR drivers/acpi/pmic/built-in.a CC drivers/pci/pcie/pme.o AS arch/x86/lib/msr-reg.o CC fs/iomap/fiemap.o CC arch/x86/pci/common.o AR arch/x86/platform/intel-quark/built-in.a CC lib/crypto/arc4.o AS arch/x86/entry/thunk.o AR drivers/pci/hotplug/built-in.a CC lib/crypto/gf128mul.o CC drivers/acpi/dptf/int340x_thermal.o AR arch/x86/entry/built-in.a CC crypto/algapi.o CC security/lsm_audit.o CC security/keys/request_key.o CC arch/x86/pci/early.o CC kernel/locking/spinlock.o AR drivers/video/backlight/built-in.a CC mm/swap.o AR lib/lzo/built-in.a CC arch/x86/lib/msr-reg-export.o AR sound/isa/ad1816a/built-in.a CC lib/crypto/mpi/mpi-div.o AR sound/isa/ad1848/built-in.a AR sound/isa/cs423x/built-in.a AR sound/isa/es1688/built-in.a AR arch/x86/platform/intel/built-in.a AR sound/isa/galaxy/built-in.a AR arch/x86/platform/olpc/built-in.a AR sound/isa/gus/built-in.a AR arch/x86/platform/scx200/built-in.a AR sound/pci/ac97/built-in.a AR sound/isa/msnd/built-in.a AR arch/x86/platform/ts5500/built-in.a CC drivers/acpi/acpica/dscontrol.o AR sound/pci/ali5451/built-in.a CC sound/core/seq/seq_prioq.o AR sound/isa/opti9xx/built-in.a AR arch/x86/platform/uv/built-in.a AR sound/pci/asihpi/built-in.a AR arch/x86/platform/built-in.a AR sound/isa/sb/built-in.a AR sound/pci/au88x0/built-in.a AR sound/pci/aw2/built-in.a AR sound/isa/wavefront/built-in.a CC block/blk-core.o AR sound/isa/wss/built-in.a AR sound/pci/ctxfi/built-in.a AR sound/isa/built-in.a AR sound/pci/ca0106/built-in.a AR sound/pci/cs46xx/built-in.a AR sound/ppc/built-in.a AR sound/pci/cs5535audio/built-in.a CC net/netlink/af_netlink.o AR drivers/pci/controller/dwc/built-in.a CC drivers/pnp/pnpacpi/core.o AR sound/pci/lola/built-in.a AR drivers/pci/controller/mobiveil/built-in.a AR sound/pci/lx6464es/built-in.a AR net/bpf/built-in.a AR drivers/pci/controller/plda/built-in.a AR sound/pci/echoaudio/built-in.a CC kernel/power/qos.o AR drivers/pci/controller/built-in.a AR sound/pci/emu10k1/built-in.a CC arch/x86/kernel/apic/io_apic.o CC ipc/namespace.o CC sound/pci/hda/hda_bind.o CC kernel/printk/printk.o AR drivers/acpi/dptf/built-in.a CC fs/iomap/seek.o AR arch/x86/kernel/cpu/mce/built-in.a CC arch/x86/kernel/cpu/topology_common.o CC crypto/asymmetric_keys/pkcs7.asn1.o CC kernel/locking/osq_lock.o CC crypto/asymmetric_keys/pkcs7_parser.o CC kernel/locking/qspinlock.o AS arch/x86/lib/hweight.o CC arch/x86/lib/iomem.o LDS arch/x86/kernel/vmlinux.lds AR drivers/pci/msi/built-in.a CC arch/x86/events/intel/lbr.o CC net/netlink/genetlink.o CC drivers/acpi/acpica/dsdebug.o CC arch/x86/events/utils.o CC net/ethtool/ioctl.o CC security/selinux/netlink.o CC kernel/locking/rtmutex_api.o CC net/ethtool/common.o CC sound/core/seq/seq_timer.o CC arch/x86/mm/extable.o CC drivers/pnp/core.o CC sound/pci/hda/hda_codec.o AR drivers/pci/pcie/built-in.a AR drivers/video/console/built-in.a AR drivers/pci/switch/built-in.a CC drivers/pci/access.o AR drivers/video/fbdev/core/built-in.a CC arch/x86/kernel/apic/msi.o AR drivers/video/fbdev/omap/built-in.a AR drivers/video/fbdev/omap2/omapfb/dss/built-in.a CC lib/crypto/mpi/mpi-mod.o AR drivers/video/fbdev/omap2/omapfb/displays/built-in.a CC net/sched/sch_api.o AR drivers/video/fbdev/omap2/omapfb/built-in.a AR drivers/video/fbdev/omap2/built-in.a CC fs/quota/quota_tree.o AR drivers/video/fbdev/built-in.a CC drivers/video/aperture.o CC security/selinux/nlmsgtab.o CC crypto/scatterwalk.o CC arch/x86/pci/bus_numa.o CC net/netlink/policy.o CC drivers/acpi/acpica/dsfield.o CC drivers/pnp/pnpacpi/rsparser.o CC arch/x86/kernel/cpu/topology_ext.o CC arch/x86/lib/atomic64_32.o CC block/blk-sysfs.o CC security/keys/request_key_auth.o CC arch/x86/lib/inat.o AR crypto/asymmetric_keys/built-in.a CC kernel/power/main.o CC io_uring/notif.o CC kernel/printk/printk_safe.o CC kernel/power/console.o CC fs/iomap/swapfile.o AR arch/x86/lib/built-in.a AR arch/x86/lib/lib.a CC arch/x86/pci/amd_bus.o CC block/blk-flush.o CC ipc/mq_sysctl.o AR drivers/amba/built-in.a CC fs/proc/task_mmu.o CC lib/crypto/mpi/mpi-mul.o CC arch/x86/kernel/cpu/topology_amd.o CC net/netfilter/core.o CC drivers/acpi/acpica/dsinit.o CC lib/crypto/blake2s.o CC sound/core/seq/seq_system.o CC sound/core/seq/seq_ports.o AR sound/pci/ice1712/built-in.a AR sound/arm/built-in.a CC mm/truncate.o CC drivers/pnp/card.o AR sound/sh/built-in.a CC arch/x86/events/rapl.o CC fs/kernfs/mount.o CC crypto/proc.o CC crypto/aead.o CC arch/x86/mm/mmap.o CC fs/sysfs/file.o CC kernel/locking/qrwlock.o CC drivers/pci/bus.o AR ipc/built-in.a CC fs/devpts/inode.o CC security/keys/user_defined.o CC drivers/video/cmdline.o CC drivers/acpi/x86/apple.o CC drivers/acpi/acpica/dsmethod.o CC sound/core/init.o CC fs/quota/quota.o CC security/selinux/netif.o CC sound/core/memory.o CC arch/x86/kernel/cpu/common.o CC security/selinux/netnode.o AR fs/iomap/built-in.a CC fs/sysfs/dir.o CC drivers/acpi/tables.o CC sound/core/seq/seq_info.o AR drivers/pnp/pnpacpi/built-in.a CC arch/x86/kernel/cpu/rdrand.o CC arch/x86/events/intel/p4.o AR arch/x86/pci/built-in.a CC io_uring/tctx.o CC arch/x86/events/msr.o CC lib/crypto/mpi/mpih-cmp.o CC arch/x86/kernel/apic/probe_32.o CC fs/netfs/buffered_read.o CC block/blk-settings.o CC arch/x86/mm/pgtable.o CC kernel/power/process.o AR drivers/clk/actions/built-in.a AR kernel/locking/built-in.a AR drivers/clk/analogbits/built-in.a CC sound/pci/hda/hda_jack.o AR drivers/clk/bcm/built-in.a AR drivers/clk/imgtec/built-in.a AR drivers/clk/imx/built-in.a CC arch/x86/events/intel/p6.o AR drivers/clk/ingenic/built-in.a AR drivers/clk/mediatek/built-in.a CC fs/proc/inode.o AR drivers/clk/microchip/built-in.a AR drivers/clk/mstar/built-in.a AR drivers/clk/mvebu/built-in.a CC security/device_cgroup.o AR drivers/clk/ralink/built-in.a CC fs/kernfs/inode.o AR drivers/clk/renesas/built-in.a CC drivers/pnp/driver.o AR drivers/clk/socfpga/built-in.a AS arch/x86/kernel/head_32.o CC drivers/acpi/acpica/dsmthdat.o AR drivers/clk/sophgo/built-in.a CC security/keys/proc.o AR drivers/clk/sprd/built-in.a AR drivers/clk/starfive/built-in.a AR drivers/clk/sunxi-ng/built-in.a CC net/ipv4/netfilter/nf_defrag_ipv4.o CC drivers/acpi/x86/cmos_rtc.o AR drivers/clk/ti/built-in.a AR drivers/clk/versatile/built-in.a AR drivers/clk/xilinx/built-in.a AR drivers/clk/built-in.a CC sound/pci/hda/hda_auto_parser.o CC net/netfilter/nf_log.o CC drivers/pci/probe.o CC drivers/pci/host-bridge.o CC drivers/acpi/acpica/dsobject.o AR fs/devpts/built-in.a CC net/sched/sch_blackhole.o CC crypto/geniv.o CC fs/sysfs/symlink.o CC net/sched/cls_api.o CC net/ethtool/netlink.o CC arch/x86/mm/physaddr.o CC sound/core/seq/seq_dummy.o CC drivers/video/nomodeset.o AR arch/x86/kernel/apic/built-in.a CC arch/x86/mm/tlb.o CC mm/vmscan.o CC lib/crypto/mpi/mpih-div.o CC kernel/printk/nbcon.o AR net/netlink/built-in.a CC net/sched/act_api.o CC net/ethtool/bitset.o CC arch/x86/mm/cpu_entry_area.o CC fs/netfs/buffered_write.o CC lib/lz4/lz4_decompress.o CC drivers/acpi/acpica/dsopcode.o CC drivers/pnp/resource.o CC drivers/video/hdmi.o CC block/blk-ioc.o AR kernel/sched/built-in.a AR sound/pci/korg1212/built-in.a AR sound/pci/mixart/built-in.a CC io_uring/filetable.o CC fs/ext4/balloc.o CC lib/crypto/mpi/mpih-mul.o CC io_uring/rw.o CC io_uring/net.o CC drivers/acpi/x86/lpss.o CC security/keys/sysctl.o CC net/ipv4/route.o CC net/sched/sch_fifo.o CC drivers/acpi/acpica/dspkginit.o CC arch/x86/events/intel/pt.o CC net/core/datagram.o CC security/selinux/netport.o CC fs/kernfs/dir.o CC io_uring/poll.o CC fs/proc/root.o CC kernel/irq/irqdesc.o AR sound/core/seq/built-in.a CC fs/quota/kqid.o CC sound/core/control.o CC kernel/rcu/update.o CC fs/sysfs/mount.o CC kernel/power/suspend.o CC kernel/rcu/sync.o CC drivers/pnp/manager.o CC arch/x86/kernel/cpu/match.o AR sound/synth/emux/built-in.a CC crypto/lskcipher.o AR sound/synth/built-in.a CC kernel/power/hibernate.o CC lib/crypto/mpi/mpi-pow.o CC net/ipv4/netfilter/nf_reject_ipv4.o CC arch/x86/events/intel/uncore.o CC kernel/irq/handle.o CC drivers/acpi/acpica/dsutils.o CC sound/pci/hda/hda_sysfs.o CC fs/netfs/direct_read.o CC kernel/printk/printk_ringbuffer.o CC net/netfilter/nf_queue.o CC drivers/pnp/support.o CC security/keys/keyctl_pkey.o CC block/blk-map.o CC arch/x86/mm/maccess.o CC fs/quota/netlink.o AR drivers/video/built-in.a CC kernel/printk/sysctl.o CC drivers/acpi/x86/s2idle.o CC net/netfilter/nf_sockopt.o CC mm/shrinker.o CC arch/x86/kernel/cpu/bugs.o AR sound/pci/nm256/built-in.a CC crypto/skcipher.o CC fs/proc/base.o CC kernel/power/snapshot.o CC drivers/acpi/acpica/dswexec.o CC drivers/pci/remove.o CC lib/crypto/blake2s-generic.o CC arch/x86/mm/pgprot.o CC fs/sysfs/group.o CC net/ethtool/strset.o AR sound/usb/misc/built-in.a CC kernel/irq/manage.o AR sound/usb/usx2y/built-in.a AR sound/firewire/built-in.a CC drivers/acpi/x86/utils.o AR sound/usb/caiaq/built-in.a AR sound/usb/6fire/built-in.a CC block/blk-merge.o AR sound/usb/hiface/built-in.a CC crypto/seqiv.o AR sound/usb/bcd2000/built-in.a AR sound/usb/built-in.a CC drivers/pnp/interface.o AR sound/sparc/built-in.a CC lib/crypto/mpi/mpiutil.o AR lib/lz4/built-in.a CC block/blk-timeout.o CC net/ipv4/inetpeer.o CC security/selinux/status.o AR security/keys/built-in.a CC net/ipv4/netfilter/ip_tables.o CC sound/pci/hda/hda_controller.o AR kernel/printk/built-in.a CC arch/x86/mm/pgtable_32.o CC fs/kernfs/file.o CC arch/x86/kernel/head32.o CC fs/ext4/bitmap.o CC drivers/acpi/acpica/dswload.o CC lib/crypto/sha1.o CC net/xfrm/xfrm_policy.o CC drivers/acpi/x86/blacklist.o CC fs/netfs/direct_write.o CC arch/x86/events/intel/uncore_nhmex.o AR fs/quota/built-in.a CC net/ipv4/netfilter/iptable_filter.o CC arch/x86/kernel/ebda.o CC sound/core/misc.o CC crypto/echainiv.o CC drivers/pci/pci.o CC drivers/dma/dw/core.o CC drivers/pci/pci-driver.o AR fs/sysfs/built-in.a CC drivers/acpi/osi.o CC kernel/power/swap.o CC io_uring/eventfd.o CC drivers/acpi/osl.o CC security/selinux/ss/ebitmap.o AR lib/crypto/mpi/built-in.a CC fs/kernfs/symlink.o CC drivers/pnp/quirks.o CC net/unix/af_unix.o CC net/core/stream.o CC net/netfilter/utils.o CC drivers/acpi/acpica/dswload2.o CC lib/crypto/sha256.o AR drivers/soc/apple/built-in.a AR drivers/soc/aspeed/built-in.a AR drivers/soc/bcm/built-in.a CC drivers/pnp/system.o CC arch/x86/kernel/platform-quirks.o AR drivers/soc/fsl/built-in.a CC mm/shmem.o AR drivers/soc/fujitsu/built-in.a AR drivers/acpi/x86/built-in.a AR drivers/soc/hisilicon/built-in.a CC drivers/dma/hsu/hsu.o AR drivers/dma/idxd/built-in.a AR drivers/soc/imx/built-in.a CC kernel/irq/spurious.o AR drivers/soc/ixp4xx/built-in.a AR drivers/soc/loongson/built-in.a AR drivers/soc/mediatek/built-in.a AR drivers/soc/microchip/built-in.a AR drivers/soc/nuvoton/built-in.a AR drivers/soc/pxa/built-in.a AR drivers/soc/amlogic/built-in.a AR drivers/soc/qcom/built-in.a CC arch/x86/mm/iomap_32.o AR drivers/soc/renesas/built-in.a AR drivers/soc/rockchip/built-in.a AR drivers/soc/sunxi/built-in.a AR drivers/soc/ti/built-in.a AR drivers/soc/versatile/built-in.a CC net/core/scm.o AR drivers/soc/xilinx/built-in.a CC net/sched/cls_cgroup.o AR drivers/soc/built-in.a CC net/sched/ematch.o CC crypto/ahash.o CC fs/jbd2/transaction.o CC fs/ext4/block_validity.o CC fs/ramfs/inode.o CC net/ethtool/linkinfo.o CC crypto/shash.o CC drivers/acpi/acpica/dswscope.o CC sound/core/device.o CC fs/jbd2/commit.o CC arch/x86/kernel/cpu/aperfmperf.o CC fs/netfs/iterator.o CC crypto/akcipher.o CC drivers/acpi/utils.o CC mm/util.o CC net/xfrm/xfrm_state.o CC fs/jbd2/recovery.o AR lib/crypto/built-in.a CC lib/zstd/zstd_decompress_module.o CC io_uring/uring_cmd.o CC io_uring/openclose.o AR fs/kernfs/built-in.a CC net/unix/garbage.o CC kernel/irq/resend.o CC drivers/dma/dw/dw.o CC net/core/gen_stats.o AR drivers/pnp/built-in.a AR sound/pci/oxygen/built-in.a CC arch/x86/mm/hugetlbpage.o CC arch/x86/mm/dump_pagetables.o CC drivers/acpi/reboot.o CC drivers/acpi/acpica/dswstate.o CC block/blk-lib.o CC sound/pci/hda/hda_proc.o CC arch/x86/events/intel/uncore_snb.o CC kernel/rcu/srcutree.o AR drivers/dma/hsu/built-in.a CC sound/core/info.o CC net/ipv4/netfilter/iptable_mangle.o CC arch/x86/mm/highmem_32.o CC lib/zstd/decompress/huf_decompress.o CC block/blk-mq.o CC fs/ramfs/file-mmu.o CC fs/proc/generic.o AR kernel/livepatch/built-in.a CC fs/netfs/locking.o CC sound/core/isadma.o CC kernel/dma/mapping.o CC security/selinux/ss/hashtab.o CC net/core/gen_estimator.o CC arch/x86/kernel/cpu/cpuid-deps.o CC kernel/irq/chip.o CC fs/ext4/dir.o CC net/netfilter/nfnetlink.o CC kernel/power/user.o CC drivers/acpi/acpica/evevent.o CC mm/mmzone.o CC net/ethtool/linkmodes.o CC net/ethtool/rss.o CC net/ipv6/netfilter/ip6_tables.o CC net/packet/af_packet.o AR net/sched/built-in.a CC net/ipv6/netfilter/ip6table_filter.o CC drivers/dma/dw/idma32.o CC crypto/sig.o CC drivers/dma/dw/acpi.o CC kernel/rcu/tree.o CC net/ipv6/netfilter/ip6table_mangle.o CC net/ipv6/netfilter/nf_defrag_ipv6_hooks.o CC net/ipv4/netfilter/ipt_REJECT.o CC security/selinux/ss/symtab.o CC arch/x86/kernel/cpu/umwait.o CC kernel/entry/common.o CC fs/hugetlbfs/inode.o CC drivers/pci/search.o CC fs/fat/cache.o AR arch/x86/mm/built-in.a CC io_uring/sqpoll.o CC fs/isofs/namei.o CC drivers/acpi/acpica/evgpe.o AR fs/ramfs/built-in.a CC kernel/entry/syscall_user_dispatch.o CC kernel/module/main.o CC security/selinux/ss/sidtab.o CC fs/netfs/main.o CC io_uring/xattr.o CC drivers/virtio/virtio.o CC fs/jbd2/checkpoint.o CC sound/core/vmaster.o AR sound/pci/pcxhr/built-in.a CC fs/isofs/inode.o CC arch/x86/events/intel/uncore_snbep.o CC sound/pci/hda/hda_hwdep.o CC net/ethtool/linkstate.o CC kernel/power/poweroff.o CC net/ipv6/netfilter/nf_conntrack_reasm.o CC fs/proc/array.o CC kernel/irq/dummychip.o CC net/ethtool/debug.o CC kernel/irq/devres.o AR drivers/dma/dw/built-in.a CC drivers/acpi/acpica/evgpeblk.o AR drivers/dma/amd/built-in.a AR drivers/dma/mediatek/built-in.a CC net/core/net_namespace.o AR drivers/dma/qcom/built-in.a AR drivers/dma/stm32/built-in.a AR drivers/dma/ti/built-in.a CC fs/ext4/ext4_jbd2.o AR drivers/dma/xilinx/built-in.a CC drivers/dma/dmaengine.o CC crypto/kpp.o CC lib/zstd/decompress/zstd_ddict.o AR kernel/power/built-in.a CC kernel/time/time.o MKCAP arch/x86/kernel/cpu/capflags.c CC net/unix/sysctl_net_unix.o CC net/ipv4/protocol.o CC sound/pci/hda/hda_intel.o CC lib/zstd/decompress/zstd_decompress.o CC fs/ext4/extents.o ASN.1 crypto/rsapubkey.asn1.[ch] CC drivers/dma/virt-dma.o CC fs/jbd2/revoke.o CC net/netfilter/nfnetlink_log.o CC sound/core/ctljack.o CC mm/vmstat.o CC io_uring/nop.o CC io_uring/fs.o CC fs/fat/dir.o CC drivers/acpi/acpica/evgpeinit.o CC [M] net/ipv4/netfilter/iptable_nat.o CC kernel/irq/autoprobe.o CC drivers/pci/rom.o CC drivers/virtio/virtio_ring.o AR kernel/entry/built-in.a CC fs/fat/fatent.o CC net/ipv6/netfilter/nf_reject_ipv6.o CC drivers/virtio/virtio_anchor.o CC net/core/secure_seq.o CC fs/isofs/dir.o CC net/ethtool/wol.o CC sound/core/jack.o CC drivers/acpi/acpica/evgpeutil.o CC security/selinux/ss/avtab.o CC fs/netfs/misc.o CC net/ipv6/af_inet6.o ASN.1 crypto/rsaprivkey.asn1.[ch] CC crypto/rsa.o CC fs/proc/fd.o CC fs/proc/proc_tty.o CC drivers/acpi/nvs.o CC drivers/tty/vt/vt_ioctl.o CC kernel/irq/irqdomain.o AR fs/hugetlbfs/built-in.a CC mm/backing-dev.o CC drivers/tty/hvc/hvc_console.o CC net/ipv4/ip_input.o AR net/unix/built-in.a CC crypto/rsa_helper.o CC lib/zstd/decompress/zstd_decompress_block.o CC fs/jbd2/journal.o CC drivers/pci/setup-res.o CC drivers/pci/irq.o CC lib/xz/xz_dec_syms.o CC kernel/time/timer.o CC kernel/dma/direct.o CC drivers/acpi/acpica/evglock.o CC drivers/char/hw_random/core.o CC drivers/dma/acpi-dma.o CC drivers/char/agp/backend.o CC io_uring/splice.o CC fs/ext4/extents_status.o CC fs/isofs/util.o CC net/xfrm/xfrm_hash.o CC sound/core/hwdep.o CC drivers/char/mem.o CC drivers/tty/serial/8250/8250_core.o CC lib/xz/xz_dec_stream.o CC crypto/rsa-pkcs1pad.o AR net/ipv4/netfilter/built-in.a CC drivers/tty/serial/8250/8250_platform.o CC security/selinux/ss/policydb.o CC drivers/acpi/acpica/evhandler.o CC kernel/futex/core.o CC drivers/tty/vt/vc_screen.o AR sound/pci/hda/built-in.a CC kernel/module/strict_rwx.o CC net/ethtool/features.o AR sound/pci/riptide/built-in.a CC lib/xz/xz_dec_lzma2.o AR sound/pci/rme9652/built-in.a CC net/core/flow_dissector.o AR sound/pci/trident/built-in.a CC net/netfilter/nf_conntrack_core.o AR sound/pci/ymfpci/built-in.a AR sound/pci/vx222/built-in.a AR sound/pci/built-in.a CC lib/dim/dim.o CC kernel/dma/ops_helpers.o CC fs/proc/cmdline.o CC block/blk-mq-tag.o CC net/ipv6/netfilter/ip6t_ipv6header.o AR drivers/tty/hvc/built-in.a CC kernel/irq/proc.o CC fs/netfs/objects.o CC net/xfrm/xfrm_input.o CC drivers/pci/vpd.o CC fs/fat/file.o CC fs/ext4/file.o CC fs/isofs/rock.o CC arch/x86/events/intel/uncore_discovery.o CC net/core/sysctl_net_core.o CC drivers/acpi/acpica/evmisc.o CC drivers/char/hw_random/intel-rng.o AR drivers/dma/built-in.a CC net/core/dev.o CC drivers/char/agp/generic.o CC net/core/dev_addr_lists.o CC net/xfrm/xfrm_output.o CC fs/isofs/export.o CC io_uring/sync.o CC sound/core/timer.o CC mm/mm_init.o CC lib/dim/net_dim.o CC lib/zstd/zstd_common_module.o CC crypto/rsassa-pkcs1.o CC drivers/virtio/virtio_pci_modern_dev.o CC kernel/module/kmod.o AR net/packet/built-in.a CC drivers/char/agp/isoch.o CC fs/ext4/fsmap.o CC fs/proc/consoles.o CC fs/ext4/fsync.o CC drivers/acpi/acpica/evregion.o CC lib/xz/xz_dec_bcj.o CC kernel/dma/remap.o CC drivers/tty/serial/8250/8250_pnp.o CC arch/x86/kernel/cpu/powerflags.o CC kernel/futex/syscalls.o CC net/ipv4/ip_fragment.o CC drivers/tty/vt/selection.o CC kernel/cgroup/cgroup.o CC kernel/irq/migration.o CC net/netfilter/nf_conntrack_standalone.o CC drivers/char/hw_random/amd-rng.o CC net/ethtool/privflags.o CC drivers/pci/setup-bus.o CC drivers/pci/vc.o CC fs/isofs/joliet.o CC block/blk-stat.o CC drivers/acpi/acpica/evrgnini.o CC fs/netfs/read_collect.o CC fs/fat/inode.o AR lib/xz/built-in.a CC drivers/acpi/acpica/evsci.o CC fs/proc/cpuinfo.o CC crypto/acompress.o CC io_uring/msg_ring.o CC arch/x86/events/intel/cstate.o CC security/selinux/ss/services.o CC kernel/time/hrtimer.o CC drivers/acpi/wakeup.o AR kernel/dma/built-in.a CC net/ipv6/netfilter/ip6t_REJECT.o CC net/ipv4/ip_forward.o CC kernel/irq/cpuhotplug.o CC drivers/char/agp/amd64-agp.o CC drivers/virtio/virtio_pci_legacy_dev.o CC kernel/module/tree_lookup.o CC kernel/cgroup/rstat.o CC drivers/tty/serial/8250/8250_rsa.o CC lib/zstd/common/debug.o CC lib/zstd/common/entropy_common.o CC drivers/tty/vt/keyboard.o CC lib/dim/rdma_dim.o CC net/xfrm/xfrm_sysctl.o AR sound/spi/built-in.a CC drivers/acpi/acpica/evxface.o CC fs/isofs/compress.o CC drivers/char/hw_random/geode-rng.o CC drivers/char/hw_random/via-rng.o CC kernel/rcu/rcu_segcblist.o CC kernel/futex/pi.o CC lib/zstd/common/error_private.o CC mm/percpu.o CC lib/zstd/common/fse_decompress.o CC fs/proc/devices.o CC lib/zstd/common/zstd_common.o CC fs/ext4/hash.o CC arch/x86/kernel/cpu/topology.o CC drivers/tty/serial/8250/8250_port.o CC kernel/time/sleep_timeout.o CC sound/core/hrtimer.o AR fs/jbd2/built-in.a CC fs/fat/misc.o CC net/netfilter/nf_conntrack_expect.o CC block/blk-mq-sysfs.o AR lib/dim/built-in.a CC drivers/acpi/acpica/evxfevnt.o CC kernel/module/kallsyms.o CC kernel/trace/trace_clock.o CC net/ethtool/rings.o CC drivers/virtio/virtio_pci_modern.o CC net/xfrm/xfrm_replay.o CC kernel/bpf/core.o CC crypto/scompress.o CC kernel/irq/pm.o AR arch/x86/events/intel/built-in.a CC kernel/events/core.o CC net/xfrm/xfrm_device.o AR arch/x86/events/built-in.a AR sound/parisc/built-in.a AR drivers/tty/ipwireless/built-in.a CC drivers/char/agp/intel-agp.o CC block/blk-mq-cpumap.o CC io_uring/advise.o CC crypto/algboss.o CC drivers/virtio/virtio_pci_common.o AR kernel/rcu/built-in.a CC drivers/char/agp/intel-gtt.o CC drivers/char/random.o AR lib/zstd/built-in.a CC lib/fonts/fonts.o CC drivers/acpi/acpica/evxfgpe.o CC drivers/acpi/acpica/evxfregn.o CC sound/core/pcm.o CC fs/netfs/read_pgpriv2.o AR drivers/char/hw_random/built-in.a CC fs/netfs/read_retry.o CC drivers/pci/mmap.o CC kernel/trace/ring_buffer.o CC kernel/fork.o CC net/xfrm/xfrm_nat_keepalive.o CC fs/proc/interrupts.o CC kernel/futex/requeue.o AR fs/isofs/built-in.a AR sound/pcmcia/vx/built-in.a AR net/ipv6/netfilter/built-in.a AR sound/pcmcia/pdaudiocf/built-in.a CC arch/x86/kernel/cpu/proc.o CC net/ipv6/anycast.o CC arch/x86/kernel/process_32.o AR sound/pcmcia/built-in.a CC crypto/testmgr.o CC block/blk-mq-sched.o CC mm/slab_common.o CC net/ipv4/ip_options.o CC fs/ext4/ialloc.o CC lib/fonts/font_8x16.o CC security/selinux/ss/conditional.o CC kernel/futex/waitwake.o CC io_uring/epoll.o CC block/ioctl.o CC kernel/time/timekeeping.o CC fs/fat/nfs.o CC kernel/module/procfs.o CC drivers/acpi/acpica/exconcat.o CC drivers/tty/vt/vt.o CC arch/x86/kernel/signal.o CC kernel/irq/msi.o CC drivers/virtio/virtio_pci_legacy.o CC drivers/virtio/virtio_pci_admin_legacy_io.o CC fs/proc/loadavg.o CC drivers/tty/tty_io.o AR lib/fonts/built-in.a CC lib/argv_split.o CC drivers/pci/devres.o CC drivers/tty/serial/8250/8250_dma.o CC io_uring/statx.o CC net/ethtool/channels.o CC mm/compaction.o CC crypto/cmac.o CC drivers/acpi/sleep.o CC kernel/cgroup/namespace.o CC arch/x86/kernel/cpu/feat_ctl.o AR drivers/char/agp/built-in.a CC security/selinux/ss/mls.o CC net/ipv4/ip_output.o CC sound/core/pcm_native.o CC drivers/acpi/acpica/exconfig.o CC net/netfilter/nf_conntrack_helper.o CC drivers/tty/serial/8250/8250_dwlib.o CC lib/bug.o CC kernel/module/sysfs.o CC fs/netfs/write_collect.o CC drivers/tty/serial/8250/8250_pcilib.o AR kernel/futex/built-in.a CC fs/proc/meminfo.o CC net/core/dst.o COPY drivers/tty/vt/defkeymap.c CC net/ipv6/ip6_output.o CC fs/fat/namei_vfat.o CC drivers/char/misc.o CC net/xfrm/xfrm_algo.o CC lib/buildid.o CC security/selinux/ss/context.o CC arch/x86/kernel/cpu/intel.o CC drivers/virtio/virtio_input.o CC crypto/hmac.o CC arch/x86/kernel/signal_32.o CC kernel/irq/affinity.o CC drivers/acpi/acpica/exconvrt.o CC kernel/events/ring_buffer.o CC block/genhd.o CC kernel/events/callchain.o CC drivers/pci/proc.o CC drivers/pci/pci-sysfs.o CC drivers/pci/slot.o CC net/netfilter/nf_conntrack_proto.o CC io_uring/timeout.o CC net/core/netevent.o CC kernel/exec_domain.o CC security/selinux/netlabel.o CC fs/proc/stat.o CC kernel/cgroup/cgroup-v1.o CC drivers/tty/serial/8250/8250_early.o AR kernel/module/built-in.a CC drivers/tty/serial/serial_core.o CC kernel/irq/matrix.o CC drivers/char/virtio_console.o CC net/ethtool/coalesce.o CC drivers/acpi/acpica/excreate.o AR net/dsa/built-in.a CC drivers/tty/vt/consolemap.o AR drivers/iommu/amd/built-in.a CC kernel/time/ntp.o AR drivers/iommu/intel/built-in.a CC arch/x86/kernel/cpu/tsx.o AR drivers/iommu/arm/arm-smmu/built-in.a AR drivers/iommu/arm/arm-smmu-v3/built-in.a AR drivers/iommu/arm/built-in.a CC drivers/char/hpet.o AR drivers/iommu/iommufd/built-in.a AR drivers/iommu/riscv/built-in.a CC lib/clz_tab.o CC drivers/iommu/iommu.o CC crypto/crypto_null.o CC lib/cmdline.o CC drivers/virtio/virtio_dma_buf.o CC net/core/neighbour.o CC lib/cpumask.o CC drivers/tty/serial/8250/8250_exar.o CC fs/netfs/write_issue.o CC block/ioprio.o CC drivers/acpi/acpica/exdebug.o CC mm/show_mem.o CC drivers/acpi/acpica/exdump.o CC fs/proc/uptime.o CC drivers/iommu/iommu-traces.o CC net/xfrm/xfrm_user.o CC kernel/trace/trace.o CC net/ipv6/ip6_input.o CC fs/fat/namei_msdos.o CC drivers/acpi/device_sysfs.o CC arch/x86/kernel/cpu/intel_epb.o CC fs/ext4/indirect.o CC drivers/tty/serial/8250/8250_lpss.o CC drivers/acpi/acpica/exfield.o CC io_uring/fdinfo.o CC arch/x86/kernel/traps.o AR kernel/bpf/built-in.a CC block/badblocks.o CC drivers/char/nvram.o CC net/netfilter/nf_conntrack_proto_generic.o CC drivers/iommu/iommu-sysfs.o CC crypto/md5.o AR drivers/virtio/built-in.a CC sound/core/pcm_lib.o CC fs/ext4/inline.o CC lib/ctype.o AR sound/mips/built-in.a CC kernel/cgroup/freezer.o CC drivers/pci/pci-acpi.o CC sound/core/pcm_misc.o CC kernel/time/clocksource.o CC lib/dec_and_lock.o CC arch/x86/kernel/cpu/amd.o CC net/ethtool/pause.o CC net/netfilter/nf_conntrack_proto_tcp.o CC drivers/acpi/acpica/exfldio.o CC fs/proc/util.o HOSTCC drivers/tty/vt/conmakehash AR security/selinux/built-in.a AR security/built-in.a CC kernel/events/hw_breakpoint.o CC drivers/iommu/dma-iommu.o AR drivers/gpu/host1x/built-in.a CC kernel/trace/trace_output.o CC net/ipv4/ip_sockglue.o CC lib/decompress.o CC drivers/tty/serial/8250/8250_mid.o AR kernel/irq/built-in.a CC mm/interval_tree.o AR drivers/gpu/vga/built-in.a CC kernel/cgroup/legacy_freezer.o CC lib/decompress_bunzip2.o CC net/netfilter/nf_conntrack_proto_udp.o CC drivers/tty/vt/defkeymap.o AR drivers/gpu/drm/tests/built-in.a AR drivers/gpu/drm/arm/built-in.a AR drivers/gpu/drm/clients/built-in.a CC arch/x86/kernel/idt.o CC drivers/gpu/drm/display/drm_display_helper_mod.o CC net/ethtool/eee.o CC drivers/gpu/drm/display/drm_dp_dual_mode_helper.o CC crypto/sha256_generic.o CC arch/x86/kernel/irq.o CC drivers/iommu/iova.o CONMK drivers/tty/vt/consolemap_deftbl.c CC net/ipv6/addrconf.o CC drivers/tty/vt/consolemap_deftbl.o AR sound/soc/built-in.a CC kernel/time/jiffies.o AR drivers/tty/vt/built-in.a CC net/ethtool/tsinfo.o CC fs/nfs/client.o AR fs/netfs/built-in.a CC drivers/pci/iomap.o AR fs/fat/built-in.a CC io_uring/cancel.o CC drivers/acpi/acpica/exmisc.o AR drivers/char/built-in.a CC drivers/gpu/drm/ttm/ttm_tt.o CC kernel/events/uprobes.o CC fs/proc/version.o CC drivers/gpu/drm/display/drm_dp_helper.o CC block/blk-rq-qos.o CC kernel/cgroup/pids.o CC fs/nfs/dir.o CC net/netfilter/nf_conntrack_proto_icmp.o CC drivers/acpi/acpica/exmutex.o CC drivers/tty/serial/serial_base_bus.o CC kernel/time/timer_list.o CC io_uring/waitid.o CC arch/x86/kernel/cpu/hygon.o CC crypto/sha512_generic.o CC kernel/trace/trace_seq.o CC drivers/connector/cn_queue.o CC sound/core/pcm_memory.o CC fs/proc/softirqs.o CC lib/decompress_inflate.o CC drivers/tty/serial/8250/8250_pci.o CC mm/list_lru.o CC drivers/connector/connector.o CC drivers/tty/serial/serial_ctrl.o CC net/ipv4/inet_hashtables.o CC kernel/time/timeconv.o CC drivers/pci/quirks.o CC arch/x86/kernel/cpu/centaur.o CC drivers/pci/pci-label.o CC drivers/acpi/acpica/exnames.o CC drivers/base/power/sysfs.o CC arch/x86/kernel/cpu/transmeta.o CC kernel/cgroup/rdma.o CC drivers/base/firmware_loader/builtin/main.o CC drivers/base/regmap/regmap.o CC drivers/gpu/drm/ttm/ttm_bo.o AR drivers/base/test/built-in.a CC drivers/acpi/device_pm.o CC drivers/tty/serial/serial_port.o CC net/ethtool/cabletest.o CC kernel/trace/trace_stat.o CC block/disk-events.o AR drivers/gpu/drm/renesas/rcar-du/built-in.a CC lib/decompress_unlz4.o AR drivers/gpu/drm/renesas/rz-du/built-in.a AR drivers/gpu/drm/renesas/built-in.a CC drivers/gpu/drm/i915/i915_config.o CC drivers/connector/cn_proc.o CC fs/exportfs/expfs.o AR drivers/iommu/built-in.a CC drivers/gpu/drm/ttm/ttm_bo_util.o CC kernel/trace/trace_printk.o CC fs/proc/namespaces.o CC fs/ext4/inode.o CC kernel/time/timecounter.o CC arch/x86/kernel/cpu/zhaoxin.o CC drivers/base/power/generic_ops.o CC kernel/time/alarmtimer.o CC drivers/acpi/acpica/exoparg1.o CC drivers/base/regmap/regcache.o CC crypto/sha3_generic.o AR drivers/base/firmware_loader/builtin/built-in.a CC sound/core/memalloc.o CC kernel/panic.o CC drivers/base/firmware_loader/main.o CC drivers/gpu/drm/i915/i915_driver.o CC mm/workingset.o CC drivers/gpu/drm/ttm/ttm_bo_vm.o CC io_uring/register.o AR net/xfrm/built-in.a CC arch/x86/kernel/cpu/vortex.o CC net/netfilter/nf_conntrack_extend.o CC fs/proc/self.o CC lib/decompress_unlzma.o CC kernel/trace/pid_list.o CC kernel/cgroup/cpuset.o CC kernel/cgroup/misc.o CC kernel/trace/trace_sched_switch.o CC kernel/trace/trace_nop.o CC drivers/tty/serial/earlycon.o CC drivers/base/component.o CC drivers/base/power/common.o CC drivers/acpi/proc.o CC drivers/pci/vgaarb.o CC drivers/acpi/acpica/exoparg2.o CC drivers/block/loop.o CC net/core/rtnetlink.o AR fs/exportfs/built-in.a CC crypto/ecb.o CC drivers/gpu/drm/ttm/ttm_module.o CC arch/x86/kernel/cpu/perfctr-watchdog.o CC drivers/acpi/acpica/exoparg3.o CC net/sunrpc/auth_gss/auth_gss.o CC block/blk-ia-ranges.o AR net/wireless/tests/built-in.a CC net/wireless/core.o CC crypto/cbc.o CC net/ethtool/tunnels.o CC net/netfilter/nf_conntrack_acct.o CC drivers/tty/serial/8250/8250_pericom.o CC fs/proc/thread_self.o AR sound/atmel/built-in.a CC drivers/gpu/drm/display/drm_dp_mst_topology.o CC drivers/gpu/drm/display/drm_dsc_helper.o CC net/netfilter/nf_conntrack_seqadj.o CC crypto/ctr.o CC arch/x86/kernel/irq_32.o CC drivers/gpu/drm/i915/i915_drm_client.o CC mm/debug.o CC sound/core/pcm_timer.o CC arch/x86/kernel/dumpstack_32.o CC drivers/block/virtio_blk.o CC kernel/cgroup/debug.o AR drivers/connector/built-in.a CC fs/proc/proc_sysctl.o CC drivers/base/power/qos.o CC drivers/acpi/acpica/exoparg6.o AR drivers/base/firmware_loader/built-in.a CC fs/lockd/clntlock.o CC drivers/gpu/drm/ttm/ttm_execbuf_util.o CC lib/decompress_unlzo.o AR net/mac80211/tests/built-in.a CC net/mac80211/main.o CC kernel/time/posix-timers.o CC fs/nls/nls_base.o CC lib/decompress_unxz.o CC fs/lockd/clntproc.o AR fs/unicode/built-in.a CC net/sunrpc/auth_gss/gss_generic_token.o CC fs/nls/nls_cp437.o CC arch/x86/kernel/cpu/vmware.o CC drivers/base/regmap/regcache-rbtree.o CC crypto/gcm.o CC drivers/acpi/acpica/exprep.o CC net/ipv4/inet_timewait_sock.o CC block/early-lookup.o CC net/netfilter/nf_conntrack_proto_icmpv6.o AR drivers/tty/serial/8250/built-in.a CC net/ipv6/addrlabel.o AR drivers/tty/serial/built-in.a CC net/ipv6/route.o CC drivers/tty/n_tty.o CC sound/core/seq_device.o CC drivers/base/regmap/regcache-flat.o AR kernel/events/built-in.a CC net/ipv6/ip6_fib.o CC net/ipv6/ipv6_sockglue.o AR drivers/pci/built-in.a CC net/ipv6/ndisc.o CC kernel/trace/blktrace.o CC fs/nls/nls_ascii.o CC crypto/ccm.o CC drivers/base/regmap/regcache-maple.o CC net/ipv6/udp.o CC lib/decompress_unzstd.o CC drivers/gpu/drm/ttm/ttm_range_manager.o CC mm/gup.o CC net/core/utils.o CC drivers/acpi/acpica/exregion.o CC block/bounce.o CC io_uring/truncate.o CC fs/ext4/ioctl.o CC arch/x86/kernel/cpu/hypervisor.o CC drivers/base/core.o CC net/ethtool/fec.o CC fs/lockd/clntxdr.o CC fs/nls/nls_iso8859-1.o CC drivers/gpu/drm/i915/i915_getparam.o CC kernel/cpu.o CC fs/nfs/file.o CC kernel/time/posix-cpu-timers.o AR drivers/gpu/drm/omapdrm/built-in.a CC fs/proc/proc_net.o AR drivers/block/built-in.a CC net/ethtool/eeprom.o AR sound/core/built-in.a CC arch/x86/kernel/cpu/mshyperv.o CC drivers/base/power/runtime.o CC sound/hda/hda_bus_type.o AR sound/x86/built-in.a CC net/ethtool/stats.o CC drivers/acpi/acpica/exresnte.o CC sound/hda/hdac_bus.o CC lib/dump_stack.o AR kernel/cgroup/built-in.a CC net/wireless/sysfs.o CC drivers/base/bus.o CC drivers/tty/tty_ioctl.o CC drivers/gpu/drm/ttm/ttm_resource.o CC net/netlabel/netlabel_user.o CC drivers/base/regmap/regmap-debugfs.o CC fs/nls/nls_utf8.o CC drivers/base/power/wakeirq.o CC drivers/acpi/acpica/exresolv.o CC net/ipv4/inet_connection_sock.o CC crypto/aes_generic.o CC io_uring/memmap.o CC net/wireless/radiotap.o CC fs/autofs/init.o CC net/netlabel/netlabel_kapi.o CC net/sunrpc/auth_gss/gss_mech_switch.o CC net/netfilter/nf_conntrack_netlink.o CC block/bsg.o AR fs/nls/built-in.a CC fs/autofs/inode.o CC lib/earlycpio.o CC crypto/crc32c_generic.o CC mm/mmap_lock.o CC lib/extable.o CC fs/proc/kcore.o CC arch/x86/kernel/time.o CC net/mac80211/status.o CC drivers/acpi/acpica/exresop.o CC sound/hda/hdac_device.o CC drivers/gpu/drm/i915/i915_ioctl.o CC net/core/link_watch.o CC fs/lockd/host.o CC fs/lockd/svc.o CC arch/x86/kernel/cpu/debugfs.o AR drivers/base/regmap/built-in.a CC drivers/tty/tty_ldisc.o CC net/sunrpc/clnt.o CC drivers/base/power/main.o CC drivers/misc/eeprom/eeprom_93cx6.o CC kernel/time/posix-clock.o CC kernel/trace/trace_events.o CC drivers/gpu/drm/ttm/ttm_pool.o CC kernel/time/itimer.o CC kernel/trace/trace_export.o CC net/ethtool/phc_vclocks.o CC crypto/authenc.o CC lib/flex_proportions.o CC drivers/gpu/drm/display/drm_hdcp_helper.o CC io_uring/io-wq.o AR sound/xen/built-in.a CC drivers/acpi/acpica/exserial.o CC net/ipv6/udplite.o CC fs/autofs/root.o CC kernel/trace/trace_event_perf.o CC block/blk-cgroup.o CC drivers/gpu/drm/i915/i915_irq.o CC net/core/filter.o AR drivers/misc/eeprom/built-in.a AR drivers/misc/cb710/built-in.a AR drivers/misc/lis3lv02d/built-in.a AR drivers/gpu/drm/tilcdc/built-in.a AR drivers/misc/cardreader/built-in.a CC lib/idr.o CC arch/x86/kernel/cpu/bus_lock.o AR drivers/misc/keba/built-in.a AR drivers/misc/built-in.a AR sound/virtio/built-in.a CC arch/x86/kernel/ioport.o CC drivers/base/dd.o CC drivers/tty/tty_buffer.o CC drivers/gpu/drm/display/drm_hdmi_helper.o CC kernel/trace/trace_events_filter.o CC drivers/acpi/acpica/exstore.o CC mm/highmem.o CC fs/proc/vmcore.o CC net/ipv4/tcp.o CC net/mac80211/driver-ops.o CC sound/hda/hdac_sysfs.o CC io_uring/futex.o CC net/netfilter/nf_conntrack_ftp.o CC net/netlabel/netlabel_domainhash.o CC block/blk-ioprio.o CC net/ipv6/raw.o CC net/sunrpc/auth_gss/svcauth_gss.o CC fs/nfs/getroot.o CC net/ipv4/tcp_input.o CC drivers/gpu/drm/i915/i915_mitigations.o CC net/wireless/util.o CC drivers/base/power/wakeup.o CC drivers/acpi/acpica/exstoren.o CC lib/iomem_copy.o CC drivers/gpu/drm/ttm/ttm_device.o CC kernel/time/clockevents.o CC fs/ext4/mballoc.o CC net/ethtool/mm.o CC net/netfilter/nf_conntrack_irc.o CC fs/autofs/symlink.o CC fs/lockd/svclock.o CC drivers/gpu/drm/virtio/virtgpu_drv.o CC lib/irq_regs.o CC crypto/authencesn.o AR drivers/gpu/drm/imx/built-in.a CC drivers/gpu/drm/display/drm_scdc_helper.o CC io_uring/napi.o CC kernel/time/tick-common.o CC drivers/tty/tty_port.o CC mm/memory.o CC drivers/acpi/bus.o CC lib/is_single_threaded.o CC drivers/acpi/acpica/exstorob.o CC arch/x86/kernel/cpu/capflags.o CC lib/klist.o AR arch/x86/kernel/cpu/built-in.a CC arch/x86/kernel/dumpstack.o CC fs/nfs/inode.o CC net/wireless/reg.o CC net/core/sock_diag.o CC net/netfilter/nf_conntrack_sip.o CC sound/hda/hdac_regmap.o CC kernel/trace/trace_events_trigger.o CC fs/autofs/waitq.o CC fs/proc/kmsg.o AR drivers/mfd/built-in.a CC drivers/gpu/drm/ttm/ttm_sys_manager.o CC net/sunrpc/xprt.o CC net/ethtool/module.o CC lib/kobject.o CC lib/kobject_uevent.o CC drivers/acpi/acpica/exsystem.o CC net/ethtool/cmis_fw_update.o CC block/blk-iolatency.o CC net/sunrpc/auth_gss/gss_rpc_upcall.o CC drivers/gpu/drm/i915/i915_module.o CC drivers/gpu/drm/virtio/virtgpu_kms.o CC fs/ext4/migrate.o CC fs/ext4/mmp.o AR drivers/gpu/drm/display/built-in.a CC drivers/base/power/wakeup_stats.o CC drivers/tty/tty_mutex.o CC net/netlabel/netlabel_addrlist.o CC net/ipv4/tcp_output.o CC sound/hda/hdac_controller.o CC drivers/gpu/drm/ttm/ttm_agp_backend.o CC drivers/acpi/acpica/extrace.o CC drivers/gpu/drm/i915/i915_params.o CC fs/proc/page.o CC crypto/lzo.o CC kernel/trace/trace_eprobe.o CC arch/x86/kernel/nmi.o CC net/sunrpc/socklib.o CC fs/autofs/expire.o CC kernel/time/tick-broadcast.o CC fs/lockd/svcshare.o CC block/blk-iocost.o CC fs/9p/vfs_super.o AR fs/hostfs/built-in.a CC fs/9p/vfs_inode.o CC net/wireless/scan.o CC drivers/base/syscore.o CC fs/ext4/move_extent.o CC drivers/base/power/trace.o CC drivers/acpi/acpica/exutils.o AR io_uring/built-in.a CC net/netfilter/nf_nat_core.o CC net/rfkill/core.o CC drivers/gpu/drm/virtio/virtgpu_gem.o CC drivers/tty/tty_ldsem.o CC net/ipv6/icmp.o AR drivers/gpu/drm/ttm/built-in.a CC net/ipv6/mcast.o CC crypto/lzo-rle.o CC fs/nfs/super.o CC drivers/gpu/drm/i915/i915_pci.o CC lib/logic_pio.o CC net/core/dev_ioctl.o CC net/ethtool/cmis_cdb.o AR drivers/nfc/built-in.a CC net/mac80211/sta_info.o CC net/netlabel/netlabel_mgmt.o CC net/sunrpc/auth_gss/gss_rpc_xdr.o CC drivers/acpi/acpica/hwacpi.o AR fs/proc/built-in.a CC net/sunrpc/auth_gss/trace.o CC arch/x86/kernel/ldt.o CC block/mq-deadline.o CC sound/hda/hdac_stream.o CC kernel/time/tick-broadcast-hrtimer.o CC net/netfilter/nf_nat_proto.o CC drivers/gpu/drm/virtio/virtgpu_vram.o CC fs/lockd/svcproc.o CC fs/autofs/dev-ioctl.o CC net/rfkill/input.o CC arch/x86/kernel/setup.o AR drivers/base/power/built-in.a CC drivers/acpi/glue.o CC drivers/acpi/acpica/hwesleep.o CC net/ipv6/reassembly.o CC drivers/tty/tty_baudrate.o CC crypto/rng.o CC kernel/time/tick-oneshot.o CC lib/maple_tree.o CC drivers/base/driver.o CC fs/ext4/namei.o CC fs/lockd/svcsubs.o CC fs/lockd/mon.o CC fs/lockd/trace.o CC kernel/trace/trace_kprobe.o CC fs/9p/vfs_inode_dotl.o CC fs/9p/vfs_addr.o CC block/kyber-iosched.o CC drivers/acpi/acpica/hwgpe.o CC drivers/gpu/drm/i915/i915_scatterlist.o CC drivers/gpu/drm/virtio/virtgpu_display.o CC kernel/time/tick-sched.o AR net/rfkill/built-in.a CC drivers/acpi/acpica/hwregs.o CC drivers/base/class.o CC fs/nfs/io.o CC sound/hda/array.o CC drivers/tty/tty_jobctrl.o AR fs/autofs/built-in.a CC net/ethtool/pse-pd.o CC drivers/acpi/scan.o CC net/sunrpc/auth_gss/gss_krb5_mech.o CC net/ipv4/tcp_timer.o CC net/netlabel/netlabel_unlabeled.o CC kernel/exit.o AR drivers/gpu/drm/i2c/built-in.a CC sound/sound_core.o CC crypto/drbg.o CC net/sunrpc/auth_gss/gss_krb5_seal.o CC lib/memcat_p.o CC net/sunrpc/xprtsock.o CC fs/9p/vfs_file.o CC fs/ext4/page-io.o CC arch/x86/kernel/x86_init.o CC drivers/acpi/acpica/hwsleep.o CC block/blk-mq-pci.o CC drivers/base/platform.o CC fs/lockd/xdr.o CC net/netlabel/netlabel_cipso_v4.o CC crypto/jitterentropy.o CC net/netfilter/nf_nat_helper.o CC drivers/gpu/drm/i915/i915_switcheroo.o CC sound/last.o CC drivers/gpu/drm/virtio/virtgpu_vq.o CC sound/hda/hdmi_chmap.o CC fs/ext4/readpage.o CC crypto/jitterentropy-kcapi.o CC net/mac80211/wep.o CC net/sunrpc/auth_gss/gss_krb5_unseal.o CC mm/mincore.o CC drivers/tty/n_null.o CC drivers/acpi/acpica/hwvalid.o CC kernel/softirq.o AR drivers/gpu/drm/panel/built-in.a CC drivers/acpi/mipi-disco-img.o CC net/sunrpc/sched.o CC fs/nfs/direct.o CC block/blk-mq-virtio.o CC kernel/time/timer_migration.o CC arch/x86/kernel/i8259.o CC net/sunrpc/auth_gss/gss_krb5_wrap.o CC fs/debugfs/inode.o CC drivers/acpi/acpica/hwxface.o CC fs/tracefs/inode.o CC fs/9p/vfs_dir.o CC crypto/ghash-generic.o CC [M] fs/efivarfs/inode.o CC net/mac80211/aead_api.o CC net/ethtool/plca.o CC mm/mlock.o CC drivers/tty/pty.o CC fs/9p/vfs_dentry.o CC fs/open.o CC net/ethtool/phy.o CC drivers/gpu/drm/i915/i915_sysfs.o AR drivers/gpu/drm/bridge/analogix/built-in.a CC net/mac80211/wpa.o AR drivers/gpu/drm/bridge/cadence/built-in.a AR drivers/gpu/drm/bridge/imx/built-in.a AR drivers/gpu/drm/bridge/synopsys/built-in.a CC kernel/trace/error_report-traces.o AR drivers/gpu/drm/bridge/built-in.a CC net/netlabel/netlabel_calipso.o CC net/ipv6/tcp_ipv6.o AR drivers/dax/hmem/built-in.a AR drivers/dax/built-in.a CC fs/tracefs/event_inode.o CC drivers/base/cpu.o CC drivers/dma-buf/dma-buf.o CC net/ipv4/tcp_ipv4.o CC drivers/acpi/acpica/hwxfsleep.o CC drivers/gpu/drm/i915/i915_utils.o CC block/blk-mq-debugfs.o CC net/9p/mod.o CC crypto/hash_info.o CC arch/x86/kernel/irqinit.o CC arch/x86/kernel/jump_label.o CC net/dns_resolver/dns_key.o CC sound/hda/trace.o CC crypto/rsapubkey.asn1.o CC net/handshake/alert.o CC crypto/rsaprivkey.asn1.o CC fs/lockd/clnt4xdr.o CC fs/lockd/xdr4.o CC fs/lockd/svc4proc.o AR crypto/built-in.a CC net/devres.o CC net/9p/client.o CC [M] fs/efivarfs/file.o CC drivers/base/firmware.o CC drivers/gpu/drm/virtio/virtgpu_fence.o CC drivers/base/init.o CC net/netfilter/nf_nat_masquerade.o CC drivers/acpi/acpica/hwpci.o CC fs/9p/v9fs.o AR drivers/gpu/drm/hisilicon/built-in.a CC kernel/time/vsyscall.o AR drivers/cxl/core/built-in.a AR drivers/cxl/built-in.a CC net/9p/error.o CC fs/debugfs/file.o CC drivers/acpi/resource.o CC drivers/tty/tty_audit.o CC net/sunrpc/auth_gss/gss_krb5_crypto.o CC drivers/acpi/acpica/nsaccess.o CC fs/lockd/procfs.o CC kernel/trace/power-traces.o CC drivers/macintosh/mac_hid.o CC net/dns_resolver/dns_query.o CC net/mac80211/scan.o CC drivers/dma-buf/dma-fence.o CC drivers/acpi/acpi_processor.o AR net/ethtool/built-in.a CC mm/mmap.o CC fs/9p/fid.o CC net/wireless/nl80211.o CC [M] fs/efivarfs/super.o AR fs/tracefs/built-in.a CC sound/hda/hdac_component.o CC net/handshake/genl.o CC block/blk-pm.o CC block/holder.o CC drivers/base/map.o CC lib/nmi_backtrace.o CC arch/x86/kernel/irq_work.o CC drivers/gpu/drm/i915/intel_clock_gating.o AR net/netlabel/built-in.a CC kernel/time/timekeeping_debug.o CC drivers/acpi/acpica/nsalloc.o CC drivers/tty/sysrq.o CC net/handshake/netlink.o CC fs/read_write.o CC mm/mmu_gather.o CC drivers/gpu/drm/virtio/virtgpu_object.o CC kernel/trace/rpm-traces.o AR drivers/scsi/pcmcia/built-in.a AR drivers/gpu/drm/mxsfb/built-in.a CC drivers/scsi/scsi.o CC fs/nfs/pagelist.o AR drivers/gpu/drm/tiny/built-in.a CC fs/ext4/resize.o CC drivers/scsi/hosts.o AR drivers/macintosh/built-in.a CC drivers/dma-buf/dma-fence-array.o CC kernel/trace/trace_dynevent.o CC fs/ext4/super.o CC net/9p/protocol.o CC net/sunrpc/auth_gss/gss_krb5_keys.o AR fs/lockd/built-in.a CC net/wireless/mlme.o CC drivers/base/devres.o CC kernel/trace/trace_probe.o CC [M] fs/efivarfs/vars.o AR net/dns_resolver/built-in.a CC drivers/gpu/drm/i915/intel_cpu_info.o CC drivers/acpi/acpica/nsarguments.o CC drivers/gpu/drm/i915/intel_device_info.o CC fs/9p/xattr.o CC net/core/tso.o CC net/9p/trans_common.o CC sound/hda/hdac_i915.o AR block/built-in.a AR drivers/gpu/drm/xlnx/built-in.a AR drivers/nvme/common/built-in.a CC drivers/gpu/drm/i915/intel_memory_region.o AR drivers/nvme/host/built-in.a CC net/netfilter/nf_nat_ftp.o AR drivers/nvme/target/built-in.a AR drivers/nvme/built-in.a CC net/9p/trans_fd.o CC net/netfilter/nf_nat_irc.o CC kernel/time/namespace.o CC net/core/sock_reuseport.o AR fs/debugfs/built-in.a CC arch/x86/kernel/probe_roms.o CC kernel/resource.o CC drivers/dma-buf/dma-fence-chain.o CC drivers/acpi/acpica/nsconvert.o CC drivers/acpi/acpica/nsdump.o CC drivers/gpu/drm/virtio/virtgpu_debugfs.o CC sound/hda/intel-dsp-config.o CC net/ipv4/tcp_minisocks.o CC kernel/trace/trace_uprobe.o CC lib/objpool.o CC drivers/gpu/drm/i915/intel_pcode.o CC net/core/fib_notifier.o AR drivers/tty/built-in.a CC net/mac80211/offchannel.o CC net/ipv6/ping.o CC fs/ext4/symlink.o CC fs/file_table.o CC kernel/sysctl.o LD [M] fs/efivarfs/efivarfs.o CC kernel/capability.o CC drivers/base/attribute_container.o CC sound/hda/intel-nhlt.o AR drivers/gpu/drm/gud/built-in.a CC drivers/scsi/scsi_ioctl.o CC net/handshake/request.o CC drivers/acpi/processor_core.o CC drivers/acpi/acpica/nseval.o AR fs/9p/built-in.a CC net/socket.o CC fs/ext4/sysfs.o CC net/sunrpc/auth.o CC drivers/dma-buf/dma-fence-unwrap.o AR kernel/time/built-in.a CC net/wireless/ibss.o CC drivers/ata/libata-core.o CC mm/mprotect.o CC net/wireless/sme.o CC arch/x86/kernel/sys_ia32.o AR net/sunrpc/auth_gss/built-in.a CC drivers/ata/libata-scsi.o CC fs/super.o CC drivers/gpu/drm/virtio/virtgpu_plane.o CC drivers/acpi/acpica/nsinit.o CC drivers/base/transport_class.o CC net/ipv4/tcp_cong.o CC net/9p/trans_virtio.o CC fs/char_dev.o CC drivers/dma-buf/dma-resv.o CC kernel/ptrace.o CC sound/hda/intel-sdw-acpi.o CC mm/mremap.o CC net/netfilter/nf_nat_sip.o CC net/netfilter/x_tables.o CC fs/ext4/xattr.o CC arch/x86/kernel/ksysfs.o CC net/wireless/chan.o CC drivers/ata/libata-eh.o CC fs/stat.o CC net/mac80211/ht.o AR drivers/net/phy/mediatek/built-in.a AR drivers/net/phy/qcom/built-in.a CC drivers/net/phy/mdio-boardinfo.o CC drivers/gpu/drm/i915/intel_region_ttm.o CC net/core/xdp.o AR drivers/net/pse-pd/built-in.a CC arch/x86/kernel/bootflag.o CC lib/plist.o AR drivers/gpu/drm/solomon/built-in.a CC drivers/gpu/drm/virtio/virtgpu_ioctl.o CC drivers/base/topology.o CC drivers/acpi/acpica/nsload.o CC drivers/scsi/scsicam.o CC drivers/acpi/processor_pdc.o CC net/netfilter/xt_tcpudp.o CC mm/msync.o CC lib/radix-tree.o CC net/ipv6/exthdrs.o AR sound/hda/built-in.a AR sound/built-in.a CC net/ipv6/datagram.o CC fs/nfs/read.o CC drivers/acpi/acpica/nsnames.o CC net/mac80211/agg-tx.o CC net/mac80211/agg-rx.o CC net/wireless/ethtool.o CC net/wireless/mesh.o CC kernel/trace/rethook.o CC drivers/acpi/acpica/nsobject.o CC drivers/dma-buf/sync_file.o CC drivers/base/container.o CC net/handshake/tlshd.o CC kernel/user.o CC arch/x86/kernel/e820.o CC drivers/ata/libata-transport.o CC drivers/scsi/scsi_error.o CC drivers/net/phy/stubs.o CC [M] drivers/gpu/drm/scheduler/sched_main.o CC fs/ext4/xattr_hurd.o CC net/sysctl_net.o CC drivers/gpu/drm/i915/intel_runtime_pm.o CC drivers/acpi/acpica/nsparse.o CC [M] drivers/gpu/drm/scheduler/sched_fence.o CC drivers/base/property.o CC drivers/gpu/drm/virtio/virtgpu_prime.o AR net/9p/built-in.a CC mm/page_vma_mapped.o CC net/handshake/trace.o CC drivers/firewire/init_ohci1394_dma.o CC mm/pagewalk.o CC net/ipv6/ip6_flowlabel.o CC drivers/gpu/drm/i915/intel_sbi.o CC net/ipv4/tcp_metrics.o CC lib/ratelimit.o AR kernel/trace/built-in.a CC kernel/signal.o AR drivers/dma-buf/built-in.a CC drivers/ata/libata-trace.o CC drivers/acpi/acpica/nspredef.o CC fs/nfs/symlink.o CC drivers/acpi/ec.o CC net/mac80211/vht.o CC lib/rbtree.o CC net/core/flow_offload.o CC arch/x86/kernel/pci-dma.o CC drivers/gpu/drm/virtio/virtgpu_trace_points.o CC net/mac80211/he.o CC drivers/cdrom/cdrom.o CC fs/exec.o CC net/netfilter/xt_CONNSECMARK.o CC drivers/acpi/acpica/nsprepkg.o CC drivers/net/phy/mdio_devres.o AR drivers/firewire/built-in.a CC fs/nfs/unlink.o CC fs/ext4/xattr_trusted.o CC net/wireless/ap.o CC drivers/gpu/drm/i915/intel_step.o HOSTCC drivers/gpu/drm/xe/xe_gen_wa_oob CC kernel/sys.o CC lib/seq_buf.o CC drivers/scsi/scsi_lib.o CC [M] drivers/gpu/drm/scheduler/sched_entity.o GEN xe_wa_oob.c xe_wa_oob.h CC [M] drivers/gpu/drm/xe/xe_bb.o CC [M] drivers/gpu/drm/xe/xe_bo.o CC drivers/acpi/acpica/nsrepair.o CC net/core/gro.o CC mm/pgtable-generic.o CC net/sunrpc/auth_null.o CC drivers/acpi/dock.o CC kernel/umh.o CC net/netfilter/xt_NFLOG.o CC drivers/gpu/drm/virtio/virtgpu_submit.o CC arch/x86/kernel/quirks.o CC drivers/base/cacheinfo.o CC net/wireless/trace.o CC drivers/net/phy/phy.o CC drivers/acpi/acpica/nsrepair2.o CC net/ipv4/tcp_fastopen.o CC lib/siphash.o CC net/ipv6/inet6_connection_sock.o CC net/mac80211/s1g.o CC net/mac80211/ibss.o CC drivers/gpu/drm/drm_atomic.o CC net/mac80211/iface.o AR net/handshake/built-in.a CC drivers/ata/libata-sata.o CC kernel/workqueue.o AR drivers/auxdisplay/built-in.a CC drivers/scsi/constants.o LD [M] drivers/gpu/drm/scheduler/gpu-sched.o CC net/ipv4/tcp_rate.o CC drivers/acpi/pci_root.o CC net/sunrpc/auth_tls.o CC fs/pipe.o CC drivers/gpu/drm/i915/intel_uncore.o CC mm/rmap.o CC net/sunrpc/auth_unix.o CC fs/ext4/xattr_user.o CC drivers/gpu/drm/i915/intel_uncore_trace.o CC drivers/acpi/acpica/nssearch.o CC net/ipv6/udp_offload.o CC drivers/base/swnode.o CC kernel/pid.o CC drivers/acpi/pci_link.o CC kernel/task_work.o CC net/sunrpc/svc.o CC lib/string.o CC net/core/netdev-genl.o CC net/netfilter/xt_SECMARK.o CC arch/x86/kernel/kdebugfs.o CC fs/ext4/fast_commit.o CC drivers/pcmcia/cs.o CC drivers/usb/common/common.o CC lib/timerqueue.o AR drivers/gpu/drm/virtio/built-in.a CC fs/nfs/write.o CC drivers/acpi/acpica/nsutils.o CC lib/union_find.o CC lib/vsprintf.o CC drivers/gpu/drm/i915/intel_wakeref.o CC drivers/net/phy/phy-c45.o CC drivers/net/mdio/acpi_mdio.o AR drivers/cdrom/built-in.a CC net/ipv6/seg6.o CC arch/x86/kernel/alternative.o CC drivers/net/mdio/fwnode_mdio.o CC mm/vmalloc.o CC lib/win_minmax.o CC net/sunrpc/svcsock.o CC drivers/base/auxiliary.o CC drivers/acpi/acpica/nswalk.o CC drivers/scsi/scsi_lib_dma.o CC drivers/gpu/drm/drm_atomic_uapi.o CC drivers/usb/core/usb.o AR drivers/usb/phy/built-in.a CC fs/nfs/namespace.o CC net/wireless/ocb.o CC drivers/ata/libata-sff.o CC [M] drivers/gpu/drm/xe/xe_bo_evict.o CC drivers/usb/core/hub.o CC net/ipv6/fib6_notifier.o CC drivers/ata/libata-pmp.o CC drivers/ata/libata-acpi.o CC kernel/extable.o CC drivers/acpi/pci_irq.o CC drivers/acpi/acpica/nsxfeval.o CC drivers/usb/common/debug.o CC net/netfilter/xt_TCPMSS.o CC net/ipv4/tcp_recovery.o CC drivers/net/phy/phy-core.o CC mm/vma.o CC net/mac80211/link.o CC drivers/scsi/scsi_scan.o AR drivers/usb/common/built-in.a CC drivers/acpi/acpica/nsxfname.o CC drivers/pcmcia/socket_sysfs.o CC kernel/params.o CC drivers/base/devtmpfs.o CC net/core/netdev-genl-gen.o CC net/ipv6/rpl.o CC drivers/net/phy/phy_device.o CC drivers/usb/core/hcd.o CC fs/nfs/mount_clnt.o AR drivers/net/mdio/built-in.a CC [M] drivers/gpu/drm/xe/xe_devcoredump.o CC drivers/usb/mon/mon_main.o CC drivers/acpi/acpica/nsxfobj.o CC drivers/input/serio/serio.o CC drivers/acpi/acpi_apd.o CC drivers/usb/mon/mon_stat.o CC drivers/gpu/drm/i915/vlv_sideband.o CC lib/xarray.o CC arch/x86/kernel/i8253.o CC drivers/pcmcia/cardbus.o CC net/ipv4/tcp_ulp.o CC net/sunrpc/svcauth.o CC net/wireless/pmsr.o CC fs/ext4/orphan.o CC drivers/net/phy/linkmode.o CC drivers/gpu/drm/drm_auth.o CC drivers/acpi/acpica/psargs.o CC fs/nfs/nfstrace.o CC net/core/gso.o CC drivers/acpi/acpi_platform.o CC drivers/base/module.o CC drivers/acpi/acpica/psloop.o CC drivers/usb/host/pci-quirks.o CC drivers/pcmcia/ds.o CC fs/namei.o CC net/ipv4/tcp_offload.o CC drivers/base/auxiliary_sysfs.o CC drivers/input/serio/i8042.o GEN drivers/scsi/scsi_devinfo_tbl.c CC drivers/scsi/scsi_devinfo.o CC drivers/usb/mon/mon_text.o CC net/core/net-sysfs.o CC net/netfilter/xt_conntrack.o CC net/ipv6/ioam6.o CC arch/x86/kernel/hw_breakpoint.o CC [M] drivers/gpu/drm/xe/xe_device.o CC net/sunrpc/svcauth_unix.o CC drivers/usb/host/ehci-hcd.o CC drivers/gpu/drm/i915/vlv_suspend.o CC drivers/acpi/acpi_pnp.o CC net/ipv4/tcp_plb.o CC drivers/acpi/acpica/psobject.o CC net/ipv6/sysctl_net_ipv6.o CC drivers/usb/class/usblp.o CC drivers/input/keyboard/atkbd.o CC drivers/usb/storage/scsiglue.o CC drivers/base/devcoredump.o AR drivers/usb/misc/built-in.a CC drivers/usb/early/ehci-dbgp.o AR drivers/net/pcs/built-in.a CC drivers/usb/mon/mon_bin.o CC drivers/ata/libata-pata-timings.o CC kernel/kthread.o AR drivers/net/ethernet/3com/built-in.a CC drivers/net/ethernet/8390/ne2k-pci.o CC drivers/usb/storage/protocol.o CC drivers/net/phy/phy_link_topology.o CC net/ipv6/xfrm6_policy.o CC drivers/acpi/acpica/psopcode.o CC mm/process_vm_access.o CC drivers/usb/core/urb.o CC drivers/pcmcia/pcmcia_resource.o CC [M] drivers/gpu/drm/xe/xe_device_sysfs.o CC [M] drivers/gpu/drm/xe/xe_dma_buf.o CC drivers/scsi/scsi_sysctl.o CC drivers/input/serio/serport.o CC drivers/acpi/power.o CC drivers/usb/host/ehci-pci.o CC arch/x86/kernel/tsc.o CC lib/lockref.o CC drivers/rtc/lib.o CC drivers/acpi/acpica/psopinfo.o CC drivers/base/platform-msi.o CC fs/fcntl.o CC net/mac80211/rate.o CC mm/page_alloc.o CC lib/bcd.o CC net/netfilter/xt_policy.o AR drivers/net/ethernet/adaptec/built-in.a CC drivers/net/ethernet/8390/8390.o CC drivers/gpu/drm/i915/soc/intel_dram.o AR drivers/usb/class/built-in.a CC lib/sort.o CC fs/nfs/export.o CC drivers/ata/ahci.o CC arch/x86/kernel/tsc_msr.o CC mm/page_frag_cache.o CC drivers/usb/storage/transport.o CC lib/parser.o AR drivers/usb/early/built-in.a CC mm/init-mm.o CC fs/ext4/acl.o AR drivers/input/keyboard/built-in.a CC drivers/input/mouse/psmouse-base.o AR drivers/input/joystick/built-in.a CC drivers/usb/host/ohci-hcd.o CC drivers/input/mouse/synaptics.o CC drivers/acpi/acpica/psparse.o CC drivers/input/mouse/focaltech.o CC net/ipv4/datagram.o CC net/core/hotdata.o CC drivers/scsi/scsi_proc.o CC net/core/netdev_rx_queue.o CC drivers/net/phy/mdio_bus.o AR drivers/usb/mon/built-in.a CC net/netfilter/xt_state.o CC drivers/base/physical_location.o CC drivers/net/phy/mdio_device.o CC drivers/input/serio/libps2.o CC drivers/input/mouse/alps.o CC drivers/rtc/class.o CC net/core/net-procfs.o CC kernel/sys_ni.o CC [M] drivers/gpu/drm/xe/xe_drm_client.o CC net/mac80211/michael.o CC mm/memblock.o CC drivers/usb/core/message.o CC drivers/base/trace.o CC lib/debug_locks.o CC net/ipv6/xfrm6_state.o CC drivers/pcmcia/cistpl.o CC drivers/acpi/acpica/psscope.o AR drivers/net/wireless/admtek/built-in.a AR drivers/net/wireless/ath/built-in.a AR drivers/net/wireless/atmel/built-in.a AR drivers/net/wireless/broadcom/built-in.a AR drivers/net/wireless/intel/built-in.a CC lib/random32.o AR drivers/net/wireless/intersil/built-in.a CC arch/x86/kernel/io_delay.o AR drivers/net/wireless/marvell/built-in.a AR drivers/net/wireless/mediatek/built-in.a CC kernel/nsproxy.o AR drivers/net/wireless/microchip/built-in.a CC drivers/rtc/interface.o AR drivers/net/wireless/purelifi/built-in.a CC drivers/pcmcia/pcmcia_cis.o AR drivers/net/wireless/quantenna/built-in.a AR drivers/net/wireless/ralink/built-in.a CC drivers/i2c/algos/i2c-algo-bit.o AR drivers/net/wireless/realtek/built-in.a AR drivers/net/wireless/rsi/built-in.a AR drivers/net/wireless/silabs/built-in.a AR drivers/net/wireless/st/built-in.a CC drivers/i2c/busses/i2c-i801.o AR drivers/net/wireless/ti/built-in.a AR drivers/net/wireless/zydas/built-in.a CC [M] drivers/gpu/drm/xe/xe_exec.o AR drivers/net/wireless/virtual/built-in.a AR drivers/net/wireless/built-in.a CC net/mac80211/tkip.o AR drivers/i2c/muxes/built-in.a CC net/mac80211/aes_cmac.o CC fs/ext4/xattr_security.o CC drivers/gpu/drm/i915/soc/intel_gmch.o AR drivers/input/serio/built-in.a CC drivers/ata/libahci.o CC drivers/scsi/scsi_debugfs.o CC drivers/acpi/acpica/pstree.o CC lib/bust_spinlocks.o CC arch/x86/kernel/rtc.o CC net/core/netpoll.o AR drivers/net/ethernet/8390/built-in.a AR drivers/net/ethernet/agere/built-in.a CC drivers/usb/storage/usb.o AR drivers/net/ethernet/alacritech/built-in.a AR drivers/net/ethernet/alteon/built-in.a AR drivers/net/ethernet/amazon/built-in.a AR drivers/input/tablet/built-in.a CC [M] drivers/gpu/drm/xe/xe_execlist.o AR drivers/net/ethernet/amd/built-in.a CC net/ipv6/xfrm6_input.o AR drivers/net/ethernet/aquantia/built-in.a CC net/ipv6/xfrm6_output.o AR drivers/net/ethernet/arc/built-in.a CC drivers/input/mouse/byd.o AR drivers/net/ethernet/asix/built-in.a AR drivers/net/ethernet/atheros/built-in.a AR drivers/net/ethernet/cadence/built-in.a AR drivers/i3c/built-in.a CC drivers/usb/core/driver.o CC drivers/net/ethernet/broadcom/bnx2.o AR drivers/net/ethernet/brocade/built-in.a CC net/sunrpc/addr.o AR drivers/net/ethernet/cavium/common/built-in.a AR drivers/base/built-in.a AR drivers/net/ethernet/cavium/thunder/built-in.a AR drivers/net/ethernet/cavium/liquidio/built-in.a AR drivers/net/ethernet/chelsio/built-in.a GEN net/wireless/shipped-certs.c AR drivers/net/ethernet/cavium/octeon/built-in.a CC [M] drivers/gpu/drm/xe/xe_exec_queue.o AR drivers/net/ethernet/cavium/built-in.a CC drivers/acpi/acpica/psutils.o CC drivers/usb/storage/initializers.o AR drivers/media/i2c/built-in.a CC net/ipv4/raw.o AR drivers/media/tuners/built-in.a CC [M] net/netfilter/nf_log_syslog.o AR drivers/media/rc/keymaps/built-in.a AR drivers/media/rc/built-in.a AR drivers/media/common/b2c2/built-in.a AR drivers/media/common/saa7146/built-in.a AR drivers/media/common/siano/built-in.a AR drivers/media/common/v4l2-tpg/built-in.a AR drivers/input/touchscreen/built-in.a CC drivers/usb/storage/sierra_ms.o AR drivers/media/common/videobuf2/built-in.a AR drivers/media/common/built-in.a CC drivers/i2c/i2c-boardinfo.o AR drivers/media/platform/allegro-dvt/built-in.a AR drivers/media/platform/amlogic/meson-ge2d/built-in.a AR drivers/media/platform/amlogic/built-in.a AR drivers/media/platform/amphion/built-in.a AR drivers/media/platform/aspeed/built-in.a AR drivers/media/pci/ttpci/built-in.a AR drivers/media/platform/atmel/built-in.a AR drivers/media/platform/broadcom/built-in.a AR drivers/media/pci/b2c2/built-in.a AR drivers/media/platform/cadence/built-in.a AR drivers/media/pci/pluto2/built-in.a AR drivers/media/pci/dm1105/built-in.a AR drivers/media/platform/chips-media/coda/built-in.a AR drivers/media/pci/pt1/built-in.a AR drivers/media/platform/chips-media/wave5/built-in.a CC drivers/net/ethernet/broadcom/tg3.o AR drivers/media/platform/chips-media/built-in.a AR drivers/media/pci/pt3/built-in.a CC drivers/net/phy/swphy.o AR drivers/media/pci/mantis/built-in.a AR drivers/media/platform/imagination/built-in.a AR drivers/media/pci/ngene/built-in.a AR drivers/media/platform/intel/built-in.a AR drivers/media/pci/ddbridge/built-in.a AR drivers/media/platform/marvell/built-in.a AR drivers/media/pci/saa7146/built-in.a AR drivers/media/platform/mediatek/jpeg/built-in.a AR drivers/media/pci/smipcie/built-in.a AR drivers/media/platform/mediatek/mdp/built-in.a AR drivers/media/pci/netup_unidvb/built-in.a CC lib/kasprintf.o AR drivers/media/platform/mediatek/vcodec/common/built-in.a AR drivers/media/pci/intel/ipu3/built-in.a AR drivers/media/pci/intel/ivsc/built-in.a CC drivers/pcmcia/rsrc_mgr.o CC arch/x86/kernel/resource.o AR drivers/media/platform/mediatek/vcodec/encoder/built-in.a AR drivers/media/pci/intel/built-in.a AR drivers/media/pci/built-in.a AR drivers/media/platform/mediatek/vcodec/decoder/built-in.a CC drivers/acpi/acpica/pswalk.o AR drivers/media/platform/mediatek/vcodec/built-in.a AR drivers/i2c/algos/built-in.a CC drivers/net/phy/fixed_phy.o AR drivers/media/platform/mediatek/vpu/built-in.a CC fs/nfs/sysfs.o AR fs/ext4/built-in.a CC drivers/scsi/scsi_trace.o AR drivers/input/misc/built-in.a AR drivers/media/platform/mediatek/mdp3/built-in.a CC fs/nfs/fs_context.o CC net/ipv6/xfrm6_protocol.o AR drivers/media/platform/mediatek/built-in.a CC drivers/rtc/nvmem.o CC drivers/rtc/dev.o CC drivers/acpi/acpica/psxface.o CC kernel/notifier.o AR drivers/media/platform/microchip/built-in.a AR drivers/media/platform/nuvoton/built-in.a AR drivers/media/platform/nxp/dw100/built-in.a AR drivers/media/platform/nvidia/tegra-vde/built-in.a AR drivers/media/platform/nvidia/built-in.a AR drivers/media/platform/nxp/imx-jpeg/built-in.a CC net/ipv4/udp.o AR drivers/media/platform/nxp/imx8-isi/built-in.a AR drivers/media/platform/nxp/built-in.a CC drivers/acpi/event.o AR drivers/pps/clients/built-in.a AR drivers/media/platform/qcom/camss/built-in.a AR drivers/pps/generators/built-in.a AR drivers/media/platform/qcom/venus/built-in.a CC drivers/pps/pps.o AR drivers/media/platform/qcom/built-in.a CC drivers/input/mouse/logips2pp.o AR drivers/media/platform/raspberrypi/pisp_be/built-in.a AR drivers/media/platform/raspberrypi/rp1-cfe/built-in.a AR drivers/media/platform/raspberrypi/built-in.a AS arch/x86/kernel/irqflags.o AR drivers/media/platform/renesas/rcar-vin/built-in.a CC arch/x86/kernel/static_call.o AR drivers/media/platform/renesas/rzg2l-cru/built-in.a CC kernel/ksysfs.o CC lib/bitmap.o AR drivers/media/platform/renesas/vsp1/built-in.a AR drivers/media/platform/renesas/built-in.a CC drivers/gpu/drm/i915/soc/intel_pch.o AR drivers/media/platform/rockchip/rga/built-in.a AR drivers/media/platform/rockchip/rkisp1/built-in.a CC mm/slub.o CC drivers/usb/storage/option_ms.o AR drivers/media/platform/rockchip/built-in.a CC drivers/gpu/drm/drm_blend.o AR drivers/media/platform/samsung/exynos-gsc/built-in.a AR drivers/media/platform/samsung/exynos4-is/built-in.a AR drivers/media/platform/samsung/s3c-camif/built-in.a AR drivers/media/platform/samsung/s5p-g2d/built-in.a CC drivers/usb/storage/usual-tables.o AR drivers/media/platform/samsung/s5p-jpeg/built-in.a CC drivers/ptp/ptp_clock.o AR drivers/media/platform/samsung/s5p-mfc/built-in.a AR drivers/media/platform/samsung/built-in.a CC net/core/fib_rules.o AR drivers/i2c/busses/built-in.a CC drivers/usb/host/ohci-pci.o CC drivers/ata/ata_piix.o AR drivers/media/platform/st/sti/bdisp/built-in.a AR drivers/media/platform/st/sti/c8sectpfe/built-in.a CC [M] net/netfilter/xt_mark.o AR drivers/media/platform/st/sti/delta/built-in.a AR drivers/media/platform/st/sti/hva/built-in.a CC drivers/acpi/acpica/rsaddr.o AR drivers/media/platform/st/stm32/built-in.a AR drivers/media/platform/st/built-in.a AR drivers/media/platform/sunxi/sun4i-csi/built-in.a CC drivers/i2c/i2c-core-base.o AR drivers/media/platform/sunxi/sun6i-csi/built-in.a AR drivers/media/platform/sunxi/sun6i-mipi-csi2/built-in.a AR drivers/media/platform/sunxi/sun8i-a83t-mipi-csi2/built-in.a AR drivers/media/platform/sunxi/sun8i-di/built-in.a CC drivers/usb/host/uhci-hcd.o AR drivers/media/platform/sunxi/sun8i-rotate/built-in.a AR drivers/media/platform/sunxi/built-in.a AR drivers/media/platform/ti/am437x/built-in.a CC drivers/gpu/drm/drm_bridge.o CC drivers/pcmcia/rsrc_nonstatic.o AR drivers/media/platform/ti/cal/built-in.a CC net/sunrpc/rpcb_clnt.o AR drivers/media/platform/ti/vpe/built-in.a AR drivers/media/platform/ti/davinci/built-in.a AR drivers/media/platform/ti/j721e-csi2rx/built-in.a AR drivers/media/platform/ti/omap/built-in.a CC arch/x86/kernel/process.o CC drivers/usb/core/config.o AR drivers/media/platform/ti/omap3isp/built-in.a AR drivers/media/platform/ti/built-in.a AR drivers/media/platform/verisilicon/built-in.a AR drivers/media/platform/via/built-in.a AR drivers/media/platform/xilinx/built-in.a CC net/sunrpc/timer.o AR drivers/media/platform/built-in.a CC drivers/rtc/proc.o CC net/sunrpc/xdr.o AR drivers/media/usb/b2c2/built-in.a AR drivers/media/usb/dvb-usb/built-in.a CC drivers/pps/kapi.o AR drivers/media/usb/dvb-usb-v2/built-in.a AR drivers/media/usb/s2255/built-in.a CC drivers/acpi/acpica/rscalc.o AR drivers/media/usb/siano/built-in.a CC drivers/scsi/scsi_logging.o AR drivers/media/usb/ttusb-budget/built-in.a CC [M] net/netfilter/xt_nat.o AR drivers/media/usb/ttusb-dec/built-in.a CC drivers/input/mouse/lifebook.o AR drivers/media/usb/built-in.a CC drivers/i2c/i2c-core-smbus.o AR drivers/media/mmc/siano/built-in.a AR drivers/media/mmc/built-in.a AR drivers/media/firewire/built-in.a AR drivers/media/spi/built-in.a CC drivers/acpi/acpica/rscreate.o AR drivers/media/test-drivers/built-in.a AR drivers/media/built-in.a CC drivers/power/supply/power_supply_core.o CC drivers/rtc/sysfs.o CC drivers/usb/host/xhci.o CC drivers/ata/pata_amd.o AR drivers/usb/storage/built-in.a CC drivers/ptp/ptp_chardev.o CC net/sunrpc/sunrpc_syms.o CC kernel/cred.o CC fs/ioctl.o CC lib/scatterlist.o CC mm/madvise.o CC drivers/pps/sysfs.o CC drivers/net/phy/realtek.o CC net/ipv4/udplite.o CC net/ipv6/netfilter.o CC [M] drivers/gpu/drm/xe/xe_force_wake.o CC drivers/usb/core/file.o CC drivers/hwmon/hwmon.o CC net/mac80211/aes_gmac.o CC drivers/usb/core/buffer.o CC drivers/usb/core/sysfs.o CC drivers/acpi/acpica/rsdumpinfo.o CC drivers/ata/pata_oldpiix.o CC drivers/gpu/drm/i915/soc/intel_rom.o CC drivers/scsi/scsi_pm.o CC drivers/input/mouse/trackpoint.o CC net/core/net-traces.o AR drivers/pps/built-in.a CC drivers/gpu/drm/drm_cache.o CC kernel/reboot.o CC drivers/pcmcia/yenta_socket.o CC drivers/i2c/i2c-core-acpi.o CC drivers/rtc/rtc-mc146818-lib.o CC drivers/scsi/scsi_bsg.o CC drivers/usb/core/endpoint.o CC drivers/acpi/acpica/rsinfo.o CC drivers/power/supply/power_supply_sysfs.o CC net/ipv6/proc.o CC net/ipv6/syncookies.o CC lib/list_sort.o CC net/ipv4/udp_offload.o CC drivers/ptp/ptp_sysfs.o CC kernel/async.o AR drivers/thermal/broadcom/built-in.a CC [M] net/netfilter/xt_LOG.o AR drivers/thermal/renesas/built-in.a AR drivers/thermal/samsung/built-in.a CC drivers/thermal/intel/intel_tcc.o CC lib/uuid.o AR drivers/thermal/st/built-in.a AR drivers/net/usb/built-in.a CC mm/page_io.o CC drivers/acpi/acpica/rsio.o CC net/core/selftests.o CC [M] drivers/gpu/drm/xe/xe_ggtt.o CC drivers/thermal/intel/therm_throt.o CC drivers/input/input.o CC net/sunrpc/cache.o CC drivers/ata/pata_sch.o CC fs/nfs/nfsroot.o CC arch/x86/kernel/ptrace.o CC drivers/input/mouse/cypress_ps2.o CC drivers/input/mouse/psmouse-smbus.o CC lib/iov_iter.o CC drivers/rtc/rtc-cmos.o CC drivers/power/supply/power_supply_leds.o CC net/ipv6/calipso.o CC net/core/ptp_classifier.o CC arch/x86/kernel/tls.o CC net/ipv6/ah6.o CC drivers/usb/core/devio.o CC net/mac80211/fils_aead.o CC drivers/power/supply/power_supply_hwmon.o CC drivers/gpu/drm/i915/i915_memcpy.o CC drivers/scsi/scsi_common.o CC drivers/acpi/acpica/rsirq.o AR drivers/net/phy/built-in.a CC drivers/usb/core/notify.o AR drivers/watchdog/built-in.a CC net/wireless/shipped-certs.o CC drivers/md/md.o CC drivers/gpu/drm/i915/i915_mm.o CC kernel/range.o CC drivers/i2c/i2c-smbus.o AR drivers/hwmon/built-in.a CC kernel/smpboot.o CC drivers/ptp/ptp_vclock.o CC arch/x86/kernel/step.o CC net/core/netprio_cgroup.o AR drivers/net/ethernet/cisco/built-in.a CC drivers/gpu/drm/drm_color_mgmt.o CC drivers/acpi/acpica/rslist.o CC lib/clz_ctz.o CC drivers/usb/core/generic.o CC [M] drivers/gpu/drm/xe/xe_gpu_scheduler.o CC kernel/ucount.o CC drivers/scsi/scsi_transport_spi.o AR drivers/power/supply/built-in.a AR drivers/power/built-in.a CC kernel/regset.o AR drivers/pcmcia/built-in.a CC drivers/usb/core/quirks.o CC drivers/ata/pata_mpiix.o CC drivers/gpu/drm/i915/i915_sw_fence.o CC drivers/usb/core/devices.o CC drivers/md/md-bitmap.o CC [M] drivers/thermal/intel/x86_pkg_temp_thermal.o AR drivers/input/mouse/built-in.a CC fs/readdir.o CC drivers/acpi/evged.o CC drivers/acpi/acpica/rsmemory.o CC kernel/ksyms_common.o CC net/core/netclassid_cgroup.o CC drivers/ptp/ptp_kvm_x86.o CC [M] net/netfilter/xt_MASQUERADE.o CC drivers/ptp/ptp_kvm_common.o CC lib/bsearch.o CC [M] drivers/gpu/drm/xe/xe_gsc.o AR drivers/thermal/qcom/built-in.a CC net/sunrpc/rpc_pipe.o AR drivers/rtc/built-in.a CC drivers/scsi/virtio_scsi.o CC fs/nfs/sysctl.o CC drivers/md/md-autodetect.o CC fs/nfs/nfs3super.o CC arch/x86/kernel/i8237.o CC net/mac80211/cfg.o AR drivers/i2c/built-in.a CC drivers/md/dm.o CC lib/find_bit.o CC net/ipv4/arp.o CC drivers/net/mii.o CC drivers/acpi/acpica/rsmisc.o CC drivers/scsi/sd.o CC net/ipv4/icmp.o CC arch/x86/kernel/stacktrace.o CC [M] net/netfilter/xt_addrtype.o CC mm/swap_state.o CC [M] drivers/gpu/drm/xe/xe_gsc_debugfs.o CC net/sunrpc/sysfs.o CC drivers/input/input-compat.o CC drivers/input/input-mt.o CC drivers/gpu/drm/i915/i915_sw_fence_work.o CC drivers/ata/ata_generic.o AR drivers/thermal/tegra/built-in.a CC net/ipv4/devinet.o CC fs/nfs/nfs3client.o CC net/mac80211/ethtool.o CC drivers/scsi/sr.o CC drivers/input/input-poller.o AR drivers/thermal/intel/built-in.a AR drivers/thermal/mediatek/built-in.a CC drivers/net/loopback.o CC drivers/thermal/thermal_core.o CC kernel/groups.o CC net/ipv6/esp6.o CC drivers/usb/host/xhci-mem.o CC drivers/usb/host/xhci-ext-caps.o CC arch/x86/kernel/reboot.o CC drivers/acpi/acpica/rsserial.o CC drivers/acpi/acpica/rsutils.o AR drivers/ptp/built-in.a CC drivers/acpi/acpica/rsxface.o CC drivers/gpu/drm/i915/i915_syncmap.o CC drivers/gpu/drm/drm_connector.o CC arch/x86/kernel/msr.o CC drivers/acpi/sysfs.o CC drivers/net/netconsole.o CC drivers/usb/core/phy.o CC net/ipv4/af_inet.o CC fs/nfs/nfs3proc.o CC drivers/cpufreq/cpufreq.o CC drivers/net/virtio_net.o CC drivers/acpi/property.o CC drivers/usb/core/port.o CC drivers/input/ff-core.o CC [M] drivers/gpu/drm/xe/xe_gsc_proxy.o CC drivers/gpu/drm/drm_crtc.o CC drivers/md/dm-table.o CC drivers/md/dm-target.o CC lib/llist.o CC drivers/acpi/acpica/tbdata.o AR drivers/net/ethernet/cortina/built-in.a CC kernel/kcmp.o AR drivers/ata/built-in.a CC drivers/cpufreq/freq_table.o CC drivers/gpu/drm/i915/i915_user_extensions.o CC net/ipv4/igmp.o AR net/wireless/built-in.a CC lib/lwq.o CC drivers/thermal/thermal_sysfs.o CC net/core/dst_cache.o CC drivers/input/touchscreen.o CC mm/swapfile.o CC lib/memweight.o CC drivers/gpu/drm/drm_displayid.o CC arch/x86/kernel/cpuid.o CC fs/select.o CC drivers/cpuidle/governors/menu.o CC lib/kfifo.o AR net/netfilter/built-in.a CC lib/percpu-refcount.o CC net/core/gro_cells.o AR drivers/mmc/built-in.a CC drivers/gpu/drm/i915/i915_debugfs.o CC drivers/gpu/drm/i915/i915_debugfs_params.o CC net/ipv6/sit.o CC drivers/acpi/acpica/tbfadt.o CC drivers/scsi/sr_ioctl.o CC net/ipv4/fib_frontend.o CC drivers/cpuidle/governors/haltpoll.o CC drivers/acpi/debugfs.o CC fs/dcache.o CC net/ipv6/addrconf_core.o CC drivers/cpufreq/cpufreq_performance.o CC mm/swap_slots.o CC net/sunrpc/svc_xprt.o CC kernel/freezer.o CC drivers/usb/core/hcd-pci.o CC drivers/usb/core/usb-acpi.o CC drivers/input/ff-memless.o CC net/sunrpc/xprtmultipath.o CC [M] drivers/gpu/drm/xe/xe_gsc_submit.o AR drivers/ufs/built-in.a CC net/ipv6/exthdrs_core.o CC kernel/profile.o CC drivers/thermal/thermal_trip.o CC lib/rhashtable.o CC net/ipv4/fib_semantics.o CC drivers/acpi/acpica/tbfind.o CC drivers/gpu/drm/i915/i915_pmu.o CC arch/x86/kernel/early-quirks.o CC lib/base64.o CC drivers/net/net_failover.o CC mm/dmapool.o CC drivers/acpi/acpica/tbinstal.o CC drivers/thermal/thermal_helpers.o CC drivers/md/dm-linear.o CC fs/nfs/nfs3xdr.o CC fs/inode.o CC net/sunrpc/stats.o CC [M] drivers/gpu/drm/xe/xe_gt.o CC drivers/gpu/drm/i915/gt/gen2_engine_cs.o AR drivers/net/ethernet/dec/tulip/built-in.a AR drivers/net/ethernet/dec/built-in.a CC drivers/usb/host/xhci-ring.o CC drivers/scsi/sr_vendor.o CC drivers/usb/host/xhci-hub.o CC arch/x86/kernel/smp.o CC arch/x86/kernel/smpboot.o CC net/ipv4/fib_trie.o CC net/mac80211/rx.o CC net/core/failover.o AR drivers/cpuidle/governors/built-in.a CC drivers/acpi/acpica/tbprint.o CC drivers/cpuidle/cpuidle.o CC fs/nfs/nfs3acl.o AR drivers/firmware/arm_ffa/built-in.a AR drivers/firmware/arm_scmi/built-in.a AR drivers/firmware/broadcom/built-in.a CC kernel/stacktrace.o AR drivers/firmware/cirrus/built-in.a CC drivers/input/sparse-keymap.o AR drivers/firmware/meson/built-in.a AR drivers/firmware/microchip/built-in.a AR drivers/usb/core/built-in.a CC kernel/dma.o CC drivers/thermal/thermal_thresholds.o CC kernel/smp.o CC drivers/cpufreq/cpufreq_userspace.o CC drivers/firmware/efi/libstub/efi-stub-helper.o CC drivers/firmware/efi/efi-bgrt.o CC drivers/input/vivaldi-fmap.o CC drivers/acpi/acpi_lpat.o CC net/ipv4/fib_notifier.o CC net/mac80211/spectmgmt.o CC drivers/firmware/efi/libstub/gop.o CC drivers/acpi/acpi_pcc.o CC fs/nfs/nfs4proc.o CC drivers/acpi/acpica/tbutils.o CC drivers/cpufreq/cpufreq_ondemand.o AR drivers/crypto/stm32/built-in.a CC lib/once.o AR drivers/crypto/xilinx/built-in.a AR drivers/crypto/hisilicon/built-in.a AR drivers/crypto/intel/keembay/built-in.a AR drivers/crypto/intel/ixp4xx/built-in.a AR drivers/crypto/intel/built-in.a AR drivers/crypto/starfive/built-in.a AR drivers/crypto/built-in.a CC drivers/gpu/drm/drm_drv.o CC drivers/scsi/sg.o CC drivers/thermal/thermal_hwmon.o CC [M] drivers/gpu/drm/xe/xe_gt_ccs_mode.o CC kernel/uid16.o CC drivers/firmware/efi/efi.o CC fs/nfs/nfs4xdr.o CC arch/x86/kernel/tsc_sync.o CC drivers/input/input-leds.o CC drivers/acpi/ac.o CC net/ipv6/ip6_checksum.o CC drivers/gpu/drm/drm_dumb_buffers.o CC drivers/acpi/acpica/tbxface.o CC drivers/gpu/drm/drm_edid.o CC lib/refcount.o CC drivers/md/dm-stripe.o CC drivers/usb/host/xhci-dbg.o CC drivers/gpu/drm/i915/gt/gen6_engine_cs.o CC kernel/kallsyms.o CC fs/attr.o AR net/core/built-in.a CC drivers/clocksource/acpi_pm.o AR drivers/net/ethernet/dlink/built-in.a CC net/mac80211/tx.o CC drivers/cpuidle/driver.o CC drivers/clocksource/i8253.o CC net/mac80211/key.o CC lib/rcuref.o CC mm/hugetlb.o CC drivers/firmware/efi/libstub/secureboot.o CC drivers/acpi/acpica/tbxfload.o CC drivers/thermal/gov_step_wise.o CC drivers/cpufreq/cpufreq_governor.o CC drivers/gpu/drm/drm_eld.o AR drivers/net/ethernet/emulex/built-in.a AR drivers/net/ethernet/engleder/built-in.a AR drivers/net/ethernet/ezchip/built-in.a AR drivers/net/ethernet/fujitsu/built-in.a AR drivers/net/ethernet/fungible/built-in.a CC drivers/usb/host/xhci-trace.o CC lib/usercopy.o AR drivers/net/ethernet/google/built-in.a CC net/ipv4/inet_fragment.o CC drivers/hid/usbhid/hid-core.o AR drivers/firmware/imx/built-in.a CC drivers/hid/usbhid/hiddev.o CC [M] drivers/gpu/drm/xe/xe_gt_clock.o CC drivers/hid/usbhid/hid-pidff.o CC arch/x86/kernel/setup_percpu.o CC drivers/input/evdev.o AR drivers/net/ethernet/hisilicon/built-in.a CC drivers/hid/hid-core.o CC drivers/cpuidle/governor.o CC drivers/cpufreq/cpufreq_governor_attr_set.o CC drivers/md/dm-ioctl.o CC lib/errseq.o CC drivers/cpuidle/sysfs.o CC fs/nfs/nfs4state.o CC drivers/acpi/acpica/tbxfroot.o AR drivers/net/ethernet/huawei/built-in.a CC drivers/hid/hid-input.o CC lib/bucket_locks.o CC drivers/usb/host/xhci-debugfs.o CC drivers/firmware/efi/libstub/tpm.o CC drivers/gpu/drm/i915/gt/gen6_ppgtt.o CC drivers/thermal/gov_user_space.o AR drivers/clocksource/built-in.a AR drivers/platform/x86/amd/built-in.a AR drivers/platform/x86/intel/built-in.a AR drivers/platform/surface/built-in.a CC drivers/platform/x86/wmi.o CC drivers/md/dm-io.o CC net/ipv6/ip6_icmp.o CC drivers/firmware/efi/vars.o CC drivers/cpuidle/poll_state.o AR drivers/firmware/psci/built-in.a CC drivers/acpi/acpica/utaddress.o CC drivers/cpufreq/acpi-cpufreq.o CC net/ipv6/output_core.o CC net/mac80211/util.o CC drivers/usb/host/xhci-pci.o CC drivers/firmware/efi/libstub/file.o CC arch/x86/kernel/mpparse.o CC drivers/platform/x86/wmi-bmof.o CC drivers/scsi/scsi_sysfs.o CC drivers/firmware/efi/reboot.o CC lib/generic-radix-tree.o CC net/ipv4/ping.o CC drivers/md/dm-kcopyd.o CC [M] drivers/gpu/drm/xe/xe_gt_freq.o AR drivers/thermal/built-in.a CC drivers/gpu/drm/i915/gt/gen7_renderclear.o CC drivers/cpuidle/cpuidle-haltpoll.o CC kernel/acct.o CC fs/bad_inode.o CC drivers/firmware/efi/libstub/mem.o CC net/sunrpc/sysctl.o CC drivers/acpi/acpica/utalloc.o AR drivers/firmware/qcom/built-in.a CC drivers/gpu/drm/drm_encoder.o CC mm/mmu_notifier.o AR drivers/firmware/smccc/built-in.a CC net/ipv4/ip_tunnel_core.o CC drivers/hid/hid-quirks.o AR drivers/input/built-in.a CC fs/file.o CC drivers/cpufreq/amd-pstate.o CC drivers/md/dm-sysfs.o CC lib/bitmap-str.o CC net/mac80211/parse.o AR drivers/cpuidle/built-in.a CC drivers/net/ethernet/intel/e1000/e1000_main.o CC drivers/net/ethernet/intel/e1000e/82571.o CC drivers/acpi/acpica/utascii.o CC drivers/net/ethernet/intel/e1000/e1000_hw.o AR drivers/net/ethernet/broadcom/built-in.a CC drivers/platform/x86/eeepc-laptop.o CC drivers/mailbox/mailbox.o CC drivers/gpu/drm/i915/gt/gen8_engine_cs.o CC drivers/hid/hid-debug.o CC arch/x86/kernel/trace_clock.o AR drivers/hid/usbhid/built-in.a CC drivers/net/ethernet/intel/e1000e/ich8lan.o CC fs/nfs/nfs4renewd.o CC net/ipv4/gre_offload.o CC drivers/firmware/efi/libstub/random.o CC [M] drivers/gpu/drm/xe/xe_gt_idle.o CC fs/filesystems.o AR drivers/firmware/tegra/built-in.a CC lib/string_helpers.o CC drivers/net/ethernet/intel/e1000e/80003es2lan.o CC drivers/platform/x86/p2sb.o CC arch/x86/kernel/trace.o CC drivers/acpi/acpica/utbuffer.o CC drivers/net/ethernet/intel/e1000/e1000_ethtool.o CC drivers/acpi/button.o CC kernel/vmcore_info.o CC mm/migrate.o CC net/ipv6/protocol.o AR drivers/scsi/built-in.a CC fs/nfs/nfs4super.o CC fs/nfs/nfs4file.o CC net/ipv6/ip6_offload.o CC drivers/mailbox/pcc.o CC fs/nfs/delegation.o CC net/ipv6/tcpv6_offload.o AR net/sunrpc/built-in.a CC net/ipv6/exthdrs_offload.o CC drivers/gpu/drm/drm_file.o CC drivers/acpi/acpica/utcksum.o CC drivers/md/dm-stats.o CC drivers/net/ethernet/intel/e100.o CC drivers/firmware/efi/libstub/randomalloc.o AR drivers/usb/host/built-in.a AR drivers/usb/built-in.a AR drivers/firmware/xilinx/built-in.a CC kernel/elfcorehdr.o CC arch/x86/kernel/rethook.o CC lib/hexdump.o CC drivers/net/ethernet/intel/e1000e/mac.o CC fs/namespace.o CC [M] drivers/gpu/drm/xe/xe_gt_mcr.o CC drivers/firmware/efi/memattr.o CC drivers/hid/hidraw.o CC drivers/cpufreq/amd-pstate-trace.o CC drivers/acpi/acpica/utcopy.o AR drivers/platform/x86/built-in.a AR drivers/platform/built-in.a CC drivers/gpu/drm/drm_fourcc.o CC fs/nfs/nfs4idmap.o CC net/mac80211/wme.o CC drivers/net/ethernet/intel/e1000/e1000_param.o CC arch/x86/kernel/vmcore_info_32.o CC fs/seq_file.o CC lib/kstrtox.o AR drivers/mailbox/built-in.a CC drivers/acpi/acpica/utexcep.o CC drivers/md/dm-rq.o CC [M] drivers/gpu/drm/xe/xe_gt_pagefault.o CC net/ipv6/inet6_hashtables.o CC drivers/gpu/drm/i915/gt/gen8_ppgtt.o CC mm/page_counter.o CC lib/iomap.o CC net/ipv4/metrics.o CC drivers/cpufreq/intel_pstate.o CC drivers/firmware/efi/libstub/pci.o CC drivers/firmware/dmi_scan.o CC kernel/crash_reserve.o CC mm/hugetlb_cgroup.o CC drivers/firmware/efi/tpm.o CC net/ipv4/netlink.o CC net/ipv4/nexthop.o CC drivers/acpi/acpica/utdebug.o CC drivers/gpu/drm/i915/gt/intel_breadcrumbs.o CC drivers/firmware/efi/libstub/skip_spaces.o AR drivers/perf/built-in.a CC drivers/firmware/dmi-id.o CC drivers/hid/hid-generic.o CC drivers/gpu/drm/drm_framebuffer.o CC kernel/kexec_core.o CC arch/x86/kernel/machine_kexec_32.o CC net/ipv4/udp_tunnel_stub.o CC fs/xattr.o CC drivers/gpu/drm/drm_gem.o CC mm/early_ioremap.o CC drivers/acpi/acpica/utdecode.o CC drivers/net/ethernet/intel/e1000e/manage.o CC drivers/acpi/fan_core.o CC drivers/gpu/drm/drm_ioctl.o CC drivers/md/dm-io-rewind.o CC lib/iomap_copy.o CC lib/devres.o CC drivers/acpi/fan_attr.o CC net/mac80211/chan.o CC kernel/crash_core.o CC drivers/firmware/efi/memmap.o CC drivers/firmware/efi/libstub/lib-cmdline.o CC net/ipv4/ip_tunnel.o CC drivers/acpi/fan_hwmon.o AS arch/x86/kernel/relocate_kernel_32.o CC lib/check_signature.o CC mm/secretmem.o CC [M] drivers/gpu/drm/xe/xe_gt_sysfs.o CC net/ipv6/mcast_snoop.o CC net/mac80211/trace.o CC drivers/acpi/acpica/utdelete.o CC drivers/firmware/efi/libstub/lib-ctype.o CC drivers/gpu/drm/i915/gt/intel_context.o CC drivers/hid/hid-a4tech.o CC drivers/firmware/efi/libstub/alignedmem.o CC drivers/md/dm-builtin.o CC drivers/acpi/acpi_video.o CC drivers/net/ethernet/intel/e1000e/nvm.o CC arch/x86/kernel/crash_dump_32.o CC drivers/gpu/drm/drm_lease.o CC net/ipv4/sysctl_net_ipv4.o CC drivers/firmware/efi/capsule.o CC kernel/kexec.o AR drivers/hwtracing/intel_th/built-in.a CC drivers/acpi/acpica/uterror.o CC kernel/utsname.o CC fs/nfs/callback.o CC drivers/gpu/drm/drm_managed.o CC drivers/hid/hid-apple.o CC lib/interval_tree.o CC net/mac80211/mlme.o CC arch/x86/kernel/crash.o CC fs/libfs.o CC drivers/gpu/drm/i915/gt/intel_context_sseu.o CC fs/nfs/callback_xdr.o CC net/ipv4/proc.o CC drivers/net/ethernet/intel/e1000e/phy.o CC drivers/firmware/memmap.o CC drivers/hid/hid-belkin.o CC drivers/firmware/efi/esrt.o AR drivers/net/ethernet/i825xx/built-in.a CC [M] drivers/gpu/drm/xe/xe_gt_throttle.o CC lib/assoc_array.o CC drivers/firmware/efi/libstub/relocate.o AR drivers/net/ethernet/intel/e1000/built-in.a AR drivers/android/built-in.a CC drivers/gpu/drm/i915/gt/intel_engine_cs.o CC drivers/firmware/efi/runtime-wrappers.o CC fs/nfs/callback_proc.o CC lib/bitrev.o CC drivers/acpi/acpica/uteval.o CC fs/fs-writeback.o CC drivers/hid/hid-cherry.o CC net/ipv4/fib_rules.o CC fs/pnode.o CC arch/x86/kernel/module.o CC drivers/firmware/efi/capsule-loader.o CC [M] drivers/gpu/drm/xe/xe_gt_tlb_invalidation.o CC mm/hmm.o CC fs/splice.o CC net/mac80211/tdls.o CC drivers/md/dm-raid1.o CC drivers/gpu/drm/i915/gt/intel_engine_heartbeat.o CC drivers/acpi/acpica/utglobal.o CC fs/nfs/nfs4namespace.o CC kernel/pid_namespace.o AR drivers/nvmem/layouts/built-in.a CC drivers/nvmem/core.o CC drivers/gpu/drm/drm_mm.o CC fs/nfs/nfs4getroot.o AR drivers/net/ethernet/microsoft/built-in.a AR net/ipv6/built-in.a CC kernel/stop_machine.o CC fs/sync.o CC drivers/firmware/efi/libstub/printk.o CC drivers/net/ethernet/intel/e1000e/param.o CC drivers/firmware/efi/earlycon.o CC mm/memfd.o CC lib/crc-ccitt.o CC drivers/gpu/drm/i915/gt/intel_engine_pm.o AR drivers/cpufreq/built-in.a CC drivers/gpu/drm/drm_mode_config.o CC kernel/audit.o CC drivers/acpi/acpica/uthex.o CC drivers/acpi/video_detect.o CC drivers/hid/hid-chicony.o CC fs/utimes.o CC drivers/gpu/drm/drm_mode_object.o CC drivers/gpu/drm/drm_modes.o CC mm/ptdump.o CC drivers/acpi/processor_driver.o CC drivers/md/dm-log.o CC fs/nfs/nfs4client.o CC arch/x86/kernel/doublefault_32.o CC [M] drivers/gpu/drm/xe/xe_gt_topology.o CC lib/crc16.o CC drivers/acpi/acpica/utids.o CC drivers/hid/hid-cypress.o CC drivers/firmware/efi/libstub/vsprintf.o CC net/mac80211/ocb.o AR drivers/net/ethernet/litex/built-in.a CC drivers/gpu/drm/drm_modeset_lock.o HOSTCC lib/gen_crc32table CC drivers/gpu/drm/i915/gt/intel_engine_user.o CC [M] drivers/gpu/drm/xe/xe_guc.o CC arch/x86/kernel/early_printk.o CC drivers/firmware/efi/libstub/x86-stub.o CC arch/x86/kernel/hpet.o AR drivers/net/ethernet/marvell/octeon_ep/built-in.a CC fs/nfs/nfs4session.o AR drivers/net/ethernet/marvell/octeon_ep_vf/built-in.a CC lib/xxhash.o CC drivers/acpi/acpica/utinit.o AR drivers/net/ethernet/marvell/octeontx2/built-in.a CC [M] drivers/gpu/drm/xe/xe_guc_ads.o CC drivers/net/ethernet/intel/e1000e/ethtool.o AR drivers/firmware/efi/built-in.a AR drivers/net/ethernet/marvell/prestera/built-in.a CC net/ipv4/ipmr.o CC fs/nfs/dns_resolve.o CC drivers/net/ethernet/marvell/sky2.o CC [M] drivers/gpu/drm/xe/xe_guc_capture.o CC drivers/md/dm-region-hash.o AR drivers/net/ethernet/mellanox/built-in.a AR drivers/net/ethernet/meta/built-in.a CC drivers/hid/hid-ezkey.o CC drivers/gpu/drm/i915/gt/intel_execlists_submission.o CC drivers/gpu/drm/drm_plane.o CC lib/genalloc.o CC arch/x86/kernel/amd_nb.o CC net/ipv4/ipmr_base.o CC drivers/md/dm-zero.o CC mm/execmem.o CC [M] drivers/gpu/drm/xe/xe_guc_ct.o CC [M] drivers/gpu/drm/xe/xe_guc_db_mgr.o AR drivers/nvmem/built-in.a CC drivers/gpu/drm/i915/gt/intel_ggtt.o CC drivers/gpu/drm/i915/gt/intel_ggtt_fencing.o CC drivers/acpi/processor_thermal.o CC fs/nfs/nfs4trace.o CC drivers/acpi/acpica/utlock.o CC drivers/net/ethernet/intel/e1000e/netdev.o CC arch/x86/kernel/kvm.o CC drivers/hid/hid-gyration.o AR drivers/net/ethernet/micrel/built-in.a CC drivers/gpu/drm/drm_prime.o CC drivers/gpu/drm/i915/gt/intel_gt.o CC kernel/auditfilter.o CC kernel/auditsc.o CC drivers/firmware/efi/libstub/smbios.o CC drivers/acpi/processor_idle.o CC net/ipv4/syncookies.o CC lib/percpu_counter.o CC drivers/acpi/acpica/utmath.o CC net/ipv4/tunnel4.o CC drivers/acpi/acpica/utmisc.o CC arch/x86/kernel/kvmclock.o CC fs/d_path.o AR drivers/net/ethernet/microchip/built-in.a CC fs/nfs/nfs4sysctl.o CC net/mac80211/airtime.o CC net/ipv4/ipconfig.o CC arch/x86/kernel/paravirt.o CC [M] drivers/gpu/drm/xe/xe_guc_hwconfig.o AR mm/built-in.a CC drivers/net/ethernet/intel/e1000e/ptp.o CC lib/audit.o AR drivers/net/ethernet/mscc/built-in.a CC fs/stack.o CC lib/syscall.o CC net/ipv4/netfilter.o AR drivers/md/built-in.a CC kernel/audit_watch.o STUBCPY drivers/firmware/efi/libstub/alignedmem.stub.o STUBCPY drivers/firmware/efi/libstub/efi-stub-helper.stub.o CC drivers/gpu/drm/i915/gt/intel_gt_buffer_pool.o STUBCPY drivers/firmware/efi/libstub/file.stub.o STUBCPY drivers/firmware/efi/libstub/gop.stub.o CC drivers/acpi/processor_throttling.o CC arch/x86/kernel/pvclock.o STUBCPY drivers/firmware/efi/libstub/lib-cmdline.stub.o STUBCPY drivers/firmware/efi/libstub/lib-ctype.stub.o STUBCPY drivers/firmware/efi/libstub/mem.stub.o STUBCPY drivers/firmware/efi/libstub/pci.stub.o STUBCPY drivers/firmware/efi/libstub/printk.stub.o STUBCPY drivers/firmware/efi/libstub/random.stub.o STUBCPY drivers/firmware/efi/libstub/randomalloc.stub.o CC net/mac80211/eht.o STUBCPY drivers/firmware/efi/libstub/relocate.stub.o CC drivers/acpi/acpica/utmutex.o CC net/ipv4/tcp_cubic.o STUBCPY drivers/firmware/efi/libstub/secureboot.stub.o CC drivers/hid/hid-ite.o STUBCPY drivers/firmware/efi/libstub/skip_spaces.stub.o STUBCPY drivers/firmware/efi/libstub/smbios.stub.o CC fs/fs_struct.o STUBCPY drivers/firmware/efi/libstub/tpm.stub.o STUBCPY drivers/firmware/efi/libstub/vsprintf.stub.o STUBCPY drivers/firmware/efi/libstub/x86-stub.stub.o CC net/mac80211/led.o AR drivers/firmware/efi/libstub/lib.a AR drivers/firmware/built-in.a CC drivers/acpi/processor_perflib.o CC lib/errname.o AR drivers/net/ethernet/myricom/built-in.a CC drivers/acpi/acpica/utnonansi.o CC arch/x86/kernel/pcspeaker.o CC drivers/hid/hid-kensington.o CC fs/statfs.o CC net/mac80211/pm.o CC drivers/acpi/container.o CC kernel/audit_fsnotify.o CC arch/x86/kernel/check.o CC drivers/gpu/drm/drm_print.o CC lib/nlattr.o CC [M] drivers/gpu/drm/xe/xe_guc_id_mgr.o AR drivers/net/ethernet/natsemi/built-in.a CC drivers/gpu/drm/i915/gt/intel_gt_ccs_mode.o CC arch/x86/kernel/uprobes.o CC net/ipv4/tcp_sigpool.o CC drivers/acpi/acpica/utobject.o CC drivers/acpi/thermal_lib.o CC [M] drivers/gpu/drm/xe/xe_guc_klv_helpers.o CC kernel/audit_tree.o CC arch/x86/kernel/perf_regs.o CC net/mac80211/rc80211_minstrel_ht.o CC lib/cpu_rmap.o CC drivers/acpi/acpica/utosi.o CC drivers/gpu/drm/drm_property.o CC fs/fs_pin.o CC fs/nsfs.o CC drivers/acpi/acpica/utownerid.o CC kernel/kprobes.o CC arch/x86/kernel/tracepoint.o CC net/ipv4/cipso_ipv4.o CC drivers/hid/hid-lg.o CC arch/x86/kernel/itmt.o CC kernel/seccomp.o CC lib/dynamic_queue_limits.o CC fs/fs_types.o CC [M] drivers/gpu/drm/xe/xe_guc_log.o CC drivers/gpu/drm/i915/gt/intel_gt_clock_utils.o CC net/ipv4/xfrm4_policy.o AR drivers/net/ethernet/neterion/built-in.a CC arch/x86/kernel/umip.o AR drivers/net/ethernet/netronome/built-in.a AR drivers/net/ethernet/ni/built-in.a CC net/mac80211/wbrf.o CC drivers/net/ethernet/nvidia/forcedeth.o AR drivers/net/ethernet/oki-semi/built-in.a CC kernel/relay.o CC lib/glob.o CC drivers/hid/hid-lgff.o AR drivers/net/ethernet/packetengines/built-in.a CC drivers/gpu/drm/drm_rect.o CC kernel/utsname_sysctl.o CC arch/x86/kernel/unwind_frame.o CC [M] drivers/gpu/drm/xe/xe_guc_pc.o CC drivers/gpu/drm/i915/gt/intel_gt_debugfs.o CC drivers/acpi/acpica/utpredef.o AR drivers/net/ethernet/qlogic/built-in.a CC drivers/acpi/thermal.o CC kernel/delayacct.o CC fs/fs_context.o CC drivers/gpu/drm/drm_syncobj.o CC lib/strncpy_from_user.o CC net/ipv4/xfrm4_state.o CC drivers/acpi/acpica/utresdecode.o CC drivers/hid/hid-lg4ff.o AR drivers/net/ethernet/qualcomm/emac/built-in.a AR drivers/net/ethernet/qualcomm/built-in.a CC lib/strnlen_user.o CC fs/fs_parser.o CC kernel/taskstats.o CC drivers/gpu/drm/drm_sysfs.o CC drivers/acpi/nhlt.o CC drivers/hid/hid-lg-g15.o CC drivers/gpu/drm/drm_trace_points.o CC drivers/acpi/acpica/utresrc.o CC drivers/acpi/acpica/utstate.o CC [M] drivers/gpu/drm/xe/xe_guc_submit.o CC kernel/tsacct.o CC drivers/net/ethernet/realtek/8139too.o CC drivers/acpi/acpi_memhotplug.o CC net/ipv4/xfrm4_input.o CC drivers/acpi/acpica/utstring.o CC lib/net_utils.o CC fs/fsopen.o CC drivers/hid/hid-microsoft.o CC lib/sg_pool.o CC drivers/acpi/ioapic.o AR drivers/net/ethernet/renesas/built-in.a AR drivers/net/ethernet/marvell/built-in.a AR drivers/net/ethernet/rdc/built-in.a CC kernel/tracepoint.o CC net/ipv4/xfrm4_output.o CC kernel/irq_work.o AR drivers/net/ethernet/rocker/built-in.a CC drivers/acpi/acpica/utstrsuppt.o CC fs/init.o AR arch/x86/kernel/built-in.a CC drivers/gpu/drm/i915/gt/intel_gt_engines_debugfs.o CC drivers/net/ethernet/realtek/r8169_main.o CC drivers/hid/hid-monterey.o AR arch/x86/built-in.a CC [M] drivers/gpu/drm/xe/xe_heci_gsc.o CC drivers/hid/hid-ntrig.o CC [M] drivers/gpu/drm/xe/xe_hw_engine.o CC net/ipv4/xfrm4_protocol.o AR drivers/net/ethernet/samsung/built-in.a CC fs/kernel_read_file.o CC drivers/hid/hid-pl.o CC lib/stackdepot.o CC lib/asn1_decoder.o CC [M] drivers/gpu/drm/xe/xe_hw_engine_class_sysfs.o CC [M] drivers/gpu/drm/xe/xe_hw_engine_group.o CC fs/mnt_idmapping.o CC fs/remap_range.o CC drivers/gpu/drm/drm_vblank.o CC kernel/static_call.o CC drivers/net/ethernet/realtek/r8169_firmware.o CC drivers/acpi/acpica/utstrtoul64.o AR fs/nfs/built-in.a AR drivers/net/ethernet/seeq/built-in.a AR drivers/net/ethernet/silan/built-in.a CC drivers/gpu/drm/drm_vblank_work.o CC drivers/net/ethernet/realtek/r8169_phy_config.o CC kernel/padata.o CC drivers/acpi/battery.o CC drivers/acpi/bgrt.o CC drivers/acpi/spcr.o CC drivers/gpu/drm/i915/gt/intel_gt_irq.o CC drivers/acpi/acpica/utxface.o GEN lib/oid_registry_data.c CC drivers/acpi/acpica/utxfinit.o CC lib/ucs2_string.o AR drivers/net/ethernet/sis/built-in.a CC [M] drivers/gpu/drm/xe/xe_hw_fence.o AR drivers/net/ethernet/sfc/built-in.a CC drivers/gpu/drm/drm_vma_manager.o CC kernel/jump_label.o CC fs/pidfs.o CC drivers/gpu/drm/i915/gt/intel_gt_mcr.o CC drivers/acpi/acpica/utxferror.o CC fs/buffer.o CC lib/sbitmap.o CC kernel/context_tracking.o CC [M] drivers/gpu/drm/xe/xe_huc.o AR drivers/net/ethernet/smsc/built-in.a CC kernel/iomem.o CC drivers/hid/hid-petalynx.o CC fs/mpage.o CC drivers/gpu/drm/drm_writeback.o CC kernel/rseq.o CC [M] drivers/gpu/drm/xe/xe_irq.o CC drivers/acpi/acpica/utxfmutex.o CC drivers/gpu/drm/i915/gt/intel_gt_pm.o CC [M] drivers/gpu/drm/xe/xe_lrc.o AR drivers/net/ethernet/socionext/built-in.a CC fs/proc_namespace.o CC lib/group_cpus.o CC [M] drivers/gpu/drm/xe/xe_migrate.o CC drivers/hid/hid-redragon.o CC drivers/gpu/drm/i915/gt/intel_gt_pm_debugfs.o CC [M] drivers/gpu/drm/xe/xe_mmio.o CC lib/fw_table.o AR drivers/net/ethernet/stmicro/built-in.a AR drivers/net/ethernet/sun/built-in.a AR drivers/net/ethernet/tehuti/built-in.a CC fs/direct-io.o CC drivers/gpu/drm/i915/gt/intel_gt_pm_irq.o CC [M] drivers/gpu/drm/xe/xe_mocs.o CC drivers/hid/hid-samsung.o CC drivers/gpu/drm/drm_panel.o CC fs/eventpoll.o AR drivers/net/ethernet/ti/built-in.a CC [M] drivers/gpu/drm/xe/xe_module.o CC drivers/hid/hid-sony.o CC drivers/gpu/drm/drm_pci.o AR net/ipv4/built-in.a AR lib/lib.a CC drivers/gpu/drm/i915/gt/intel_gt_requests.o AR drivers/acpi/acpica/built-in.a AR drivers/net/ethernet/vertexcom/built-in.a CC drivers/gpu/drm/drm_debugfs.o CC fs/anon_inodes.o AR drivers/net/ethernet/via/built-in.a CC [M] drivers/gpu/drm/xe/xe_oa.o GEN lib/crc32table.h CC lib/oid_registry.o CC drivers/hid/hid-sunplus.o CC drivers/gpu/drm/i915/gt/intel_gt_sysfs.o CC drivers/hid/hid-topseed.o CC drivers/gpu/drm/drm_debugfs_crc.o CC fs/signalfd.o AR drivers/acpi/built-in.a AR drivers/net/ethernet/wangxun/built-in.a CC drivers/gpu/drm/drm_panel_orientation_quirks.o CC drivers/gpu/drm/i915/gt/intel_gt_sysfs_pm.o CC [M] drivers/gpu/drm/xe/xe_observation.o CC lib/crc32.o CC fs/timerfd.o CC drivers/gpu/drm/drm_buddy.o AR drivers/net/ethernet/wiznet/built-in.a AR drivers/net/ethernet/xilinx/built-in.a CC drivers/gpu/drm/i915/gt/intel_gtt.o CC [M] drivers/gpu/drm/xe/xe_pat.o CC [M] drivers/gpu/drm/xe/xe_pci.o CC drivers/gpu/drm/i915/gt/intel_llc.o CC drivers/gpu/drm/i915/gt/intel_lrc.o CC fs/eventfd.o CC fs/aio.o CC [M] drivers/gpu/drm/xe/xe_pcode.o AR kernel/built-in.a AR drivers/net/ethernet/intel/e1000e/built-in.a AR drivers/net/ethernet/intel/built-in.a CC drivers/gpu/drm/drm_gem_shmem_helper.o CC [M] drivers/gpu/drm/xe/xe_pm.o AR drivers/net/ethernet/xircom/built-in.a AR drivers/net/ethernet/synopsys/built-in.a CC drivers/gpu/drm/i915/gt/intel_migrate.o CC drivers/gpu/drm/drm_atomic_helper.o CC fs/locks.o AR drivers/net/ethernet/pensando/built-in.a CC [M] drivers/gpu/drm/xe/xe_preempt_fence.o CC drivers/gpu/drm/drm_atomic_state_helper.o CC drivers/gpu/drm/i915/gt/intel_mocs.o CC drivers/gpu/drm/drm_crtc_helper.o CC [M] drivers/gpu/drm/xe/xe_pt.o CC fs/binfmt_misc.o CC drivers/gpu/drm/i915/gt/intel_ppgtt.o CC [M] drivers/gpu/drm/xe/xe_pt_walk.o CC drivers/gpu/drm/drm_damage_helper.o AR lib/built-in.a AR drivers/net/ethernet/nvidia/built-in.a CC fs/binfmt_script.o CC drivers/gpu/drm/i915/gt/intel_rc6.o CC [M] drivers/gpu/drm/xe/xe_query.o CC drivers/gpu/drm/drm_flip_work.o CC fs/binfmt_elf.o CC drivers/gpu/drm/i915/gt/intel_region_lmem.o CC drivers/gpu/drm/drm_format_helper.o CC drivers/gpu/drm/i915/gt/intel_renderstate.o CC drivers/gpu/drm/drm_gem_atomic_helper.o CC fs/mbcache.o CC [M] drivers/gpu/drm/xe/xe_range_fence.o CC drivers/gpu/drm/i915/gt/intel_reset.o CC fs/posix_acl.o CC drivers/gpu/drm/drm_gem_framebuffer_helper.o AR drivers/hid/built-in.a CC [M] drivers/gpu/drm/xe/xe_reg_sr.o CC fs/coredump.o CC drivers/gpu/drm/i915/gt/intel_ring.o CC fs/drop_caches.o CC drivers/gpu/drm/drm_kms_helper_common.o CC drivers/gpu/drm/i915/gt/intel_ring_submission.o CC fs/sysctls.o CC [M] drivers/gpu/drm/xe/xe_reg_whitelist.o CC drivers/gpu/drm/drm_modeset_helper.o CC [M] drivers/gpu/drm/xe/xe_rtp.o CC fs/fhandle.o CC [M] drivers/gpu/drm/xe/xe_ring_ops.o CC drivers/gpu/drm/drm_plane_helper.o CC drivers/gpu/drm/i915/gt/intel_rps.o CC [M] drivers/gpu/drm/xe/xe_sa.o CC drivers/gpu/drm/i915/gt/intel_sa_media.o CC drivers/gpu/drm/drm_probe_helper.o CC drivers/gpu/drm/i915/gt/intel_sseu.o AR net/mac80211/built-in.a AR net/built-in.a CC [M] drivers/gpu/drm/xe/xe_sched_job.o CC drivers/gpu/drm/drm_self_refresh_helper.o CC [M] drivers/gpu/drm/xe/xe_step.o CC drivers/gpu/drm/drm_simple_kms_helper.o CC drivers/gpu/drm/i915/gt/intel_sseu_debugfs.o CC drivers/gpu/drm/i915/gt/intel_timeline.o CC drivers/gpu/drm/bridge/panel.o CC drivers/gpu/drm/i915/gt/intel_tlb.o CC [M] drivers/gpu/drm/xe/xe_sync.o CC drivers/gpu/drm/drm_mipi_dsi.o CC drivers/gpu/drm/i915/gt/intel_wopcm.o CC [M] drivers/gpu/drm/drm_exec.o CC [M] drivers/gpu/drm/drm_gpuvm.o CC [M] drivers/gpu/drm/xe/xe_tile.o AR drivers/net/ethernet/realtek/built-in.a CC drivers/gpu/drm/i915/gt/intel_workarounds.o AR drivers/net/ethernet/built-in.a CC [M] drivers/gpu/drm/drm_suballoc.o CC [M] drivers/gpu/drm/xe/xe_tile_sysfs.o CC drivers/gpu/drm/i915/gt/shmem_utils.o CC drivers/gpu/drm/i915/gt/sysfs_engines.o AR drivers/net/built-in.a CC [M] drivers/gpu/drm/drm_gem_ttm_helper.o CC [M] drivers/gpu/drm/xe/xe_trace.o CC drivers/gpu/drm/i915/gt/intel_ggtt_gmch.o CC drivers/gpu/drm/i915/gt/gen6_renderstate.o CC [M] drivers/gpu/drm/xe/xe_trace_bo.o CC drivers/gpu/drm/i915/gt/gen7_renderstate.o CC [M] drivers/gpu/drm/xe/xe_trace_guc.o CC drivers/gpu/drm/i915/gt/gen8_renderstate.o CC drivers/gpu/drm/i915/gt/gen9_renderstate.o CC [M] drivers/gpu/drm/xe/xe_trace_lrc.o CC drivers/gpu/drm/i915/gem/i915_gem_busy.o CC drivers/gpu/drm/i915/gem/i915_gem_clflush.o CC [M] drivers/gpu/drm/xe/xe_ttm_sys_mgr.o CC [M] drivers/gpu/drm/xe/xe_ttm_stolen_mgr.o CC drivers/gpu/drm/i915/gem/i915_gem_context.o CC [M] drivers/gpu/drm/xe/xe_ttm_vram_mgr.o CC drivers/gpu/drm/i915/gem/i915_gem_create.o CC [M] drivers/gpu/drm/xe/xe_tuning.o CC [M] drivers/gpu/drm/xe/xe_uc.o CC drivers/gpu/drm/i915/gem/i915_gem_dmabuf.o CC [M] drivers/gpu/drm/xe/xe_uc_fw.o CC drivers/gpu/drm/i915/gem/i915_gem_domain.o CC [M] drivers/gpu/drm/xe/xe_vm.o CC drivers/gpu/drm/i915/gem/i915_gem_execbuffer.o CC [M] drivers/gpu/drm/xe/xe_vram.o CC [M] drivers/gpu/drm/xe/xe_vram_freq.o LD [M] drivers/gpu/drm/drm_suballoc_helper.o CC drivers/gpu/drm/i915/gem/i915_gem_internal.o CC drivers/gpu/drm/i915/gem/i915_gem_lmem.o CC [M] drivers/gpu/drm/xe/xe_vsec.o CC drivers/gpu/drm/i915/gem/i915_gem_mman.o CC [M] drivers/gpu/drm/xe/xe_wait_user_fence.o CC drivers/gpu/drm/i915/gem/i915_gem_object.o CC [M] drivers/gpu/drm/xe/xe_wa.o CC [M] drivers/gpu/drm/xe/xe_wopcm.o LD [M] drivers/gpu/drm/drm_ttm_helper.o CC drivers/gpu/drm/i915/gem/i915_gem_pages.o CC [M] drivers/gpu/drm/xe/xe_hmm.o CC drivers/gpu/drm/i915/gem/i915_gem_phys.o CC drivers/gpu/drm/i915/gem/i915_gem_pm.o CC [M] drivers/gpu/drm/xe/xe_hwmon.o CC [M] drivers/gpu/drm/xe/xe_gt_sriov_vf.o CC drivers/gpu/drm/i915/gem/i915_gem_region.o CC drivers/gpu/drm/i915/gem/i915_gem_shmem.o CC drivers/gpu/drm/i915/gem/i915_gem_shrinker.o CC [M] drivers/gpu/drm/xe/xe_guc_relay.o AR fs/built-in.a CC drivers/gpu/drm/i915/gem/i915_gem_stolen.o CC [M] drivers/gpu/drm/xe/xe_memirq.o CC drivers/gpu/drm/i915/gem/i915_gem_throttle.o CC [M] drivers/gpu/drm/xe/xe_sriov.o CC drivers/gpu/drm/i915/gem/i915_gem_tiling.o CC [M] drivers/gpu/drm/xe/xe_sriov_vf.o CC [M] drivers/gpu/drm/xe/display/ext/i915_irq.o CC drivers/gpu/drm/i915/gem/i915_gem_ttm.o CC [M] drivers/gpu/drm/xe/display/ext/i915_utils.o CC [M] drivers/gpu/drm/xe/display/intel_bo.o CC drivers/gpu/drm/i915/gem/i915_gem_ttm_move.o CC drivers/gpu/drm/i915/gem/i915_gem_ttm_pm.o CC [M] drivers/gpu/drm/xe/display/intel_fb_bo.o CC drivers/gpu/drm/i915/gem/i915_gem_userptr.o CC drivers/gpu/drm/i915/gem/i915_gem_wait.o CC [M] drivers/gpu/drm/xe/display/intel_fbdev_fb.o CC drivers/gpu/drm/i915/gem/i915_gemfs.o CC drivers/gpu/drm/i915/i915_active.o CC [M] drivers/gpu/drm/xe/display/xe_display.o CC [M] drivers/gpu/drm/xe/display/xe_display_misc.o CC [M] drivers/gpu/drm/xe/display/xe_display_rps.o CC [M] drivers/gpu/drm/xe/display/xe_display_wa.o CC [M] drivers/gpu/drm/xe/display/xe_dsb_buffer.o CC drivers/gpu/drm/i915/i915_cmd_parser.o CC drivers/gpu/drm/i915/i915_deps.o CC [M] drivers/gpu/drm/xe/display/xe_fb_pin.o CC [M] drivers/gpu/drm/xe/display/xe_hdcp_gsc.o CC drivers/gpu/drm/i915/i915_gem.o CC [M] drivers/gpu/drm/xe/display/xe_plane_initial.o CC drivers/gpu/drm/i915/i915_gem_evict.o CC drivers/gpu/drm/i915/i915_gem_gtt.o CC drivers/gpu/drm/i915/i915_gem_ww.o CC drivers/gpu/drm/i915/i915_query.o CC [M] drivers/gpu/drm/xe/display/xe_tdf.o CC drivers/gpu/drm/i915/i915_request.o CC [M] drivers/gpu/drm/xe/i915-soc/intel_dram.o CC [M] drivers/gpu/drm/xe/i915-soc/intel_pch.o CC [M] drivers/gpu/drm/xe/i915-soc/intel_rom.o CC drivers/gpu/drm/i915/i915_scheduler.o CC [M] drivers/gpu/drm/xe/i915-display/icl_dsi.o CC drivers/gpu/drm/i915/i915_trace_points.o CC [M] drivers/gpu/drm/xe/i915-display/intel_alpm.o CC [M] drivers/gpu/drm/xe/i915-display/intel_atomic.o CC [M] drivers/gpu/drm/xe/i915-display/intel_atomic_plane.o CC [M] drivers/gpu/drm/xe/i915-display/intel_audio.o CC drivers/gpu/drm/i915/i915_ttm_buddy_manager.o CC drivers/gpu/drm/i915/i915_vma.o CC drivers/gpu/drm/i915/i915_vma_resource.o CC drivers/gpu/drm/i915/gt/uc/intel_gsc_fw.o CC drivers/gpu/drm/i915/gt/uc/intel_gsc_proxy.o CC drivers/gpu/drm/i915/gt/uc/intel_gsc_uc.o CC [M] drivers/gpu/drm/xe/i915-display/intel_backlight.o CC drivers/gpu/drm/i915/gt/uc/intel_gsc_uc_debugfs.o CC [M] drivers/gpu/drm/xe/i915-display/intel_bios.o CC [M] drivers/gpu/drm/xe/i915-display/intel_bw.o CC [M] drivers/gpu/drm/xe/i915-display/intel_cdclk.o CC drivers/gpu/drm/i915/gt/uc/intel_gsc_uc_heci_cmd_submit.o CC [M] drivers/gpu/drm/xe/i915-display/intel_color.o CC drivers/gpu/drm/i915/gt/uc/intel_guc.o CC drivers/gpu/drm/i915/gt/uc/intel_guc_ads.o CC drivers/gpu/drm/i915/gt/uc/intel_guc_capture.o CC drivers/gpu/drm/i915/gt/uc/intel_guc_ct.o CC drivers/gpu/drm/i915/gt/uc/intel_guc_debugfs.o CC [M] drivers/gpu/drm/xe/i915-display/intel_combo_phy.o CC drivers/gpu/drm/i915/gt/uc/intel_guc_fw.o CC [M] drivers/gpu/drm/xe/i915-display/intel_connector.o CC [M] drivers/gpu/drm/xe/i915-display/intel_crtc.o CC drivers/gpu/drm/i915/gt/uc/intel_guc_hwconfig.o CC drivers/gpu/drm/i915/gt/uc/intel_guc_log.o CC [M] drivers/gpu/drm/xe/i915-display/intel_crtc_state_dump.o CC drivers/gpu/drm/i915/gt/uc/intel_guc_log_debugfs.o CC [M] drivers/gpu/drm/xe/i915-display/intel_cursor.o CC [M] drivers/gpu/drm/xe/i915-display/intel_cx0_phy.o CC [M] drivers/gpu/drm/xe/i915-display/intel_ddi.o CC drivers/gpu/drm/i915/gt/uc/intel_guc_rc.o CC drivers/gpu/drm/i915/gt/uc/intel_guc_slpc.o CC [M] drivers/gpu/drm/xe/i915-display/intel_ddi_buf_trans.o CC [M] drivers/gpu/drm/xe/i915-display/intel_display.o CC drivers/gpu/drm/i915/gt/uc/intel_guc_submission.o CC [M] drivers/gpu/drm/xe/i915-display/intel_display_conversion.o CC [M] drivers/gpu/drm/xe/i915-display/intel_display_device.o CC drivers/gpu/drm/i915/gt/uc/intel_huc.o CC [M] drivers/gpu/drm/xe/i915-display/intel_display_driver.o CC drivers/gpu/drm/i915/gt/uc/intel_huc_debugfs.o CC drivers/gpu/drm/i915/gt/uc/intel_huc_fw.o CC drivers/gpu/drm/i915/gt/uc/intel_uc.o CC drivers/gpu/drm/i915/gt/uc/intel_uc_debugfs.o CC drivers/gpu/drm/i915/gt/uc/intel_uc_fw.o CC drivers/gpu/drm/i915/gt/intel_gsc.o CC [M] drivers/gpu/drm/xe/i915-display/intel_display_irq.o CC drivers/gpu/drm/i915/i915_hwmon.o CC drivers/gpu/drm/i915/display/hsw_ips.o CC [M] drivers/gpu/drm/xe/i915-display/intel_display_params.o CC drivers/gpu/drm/i915/display/i9xx_plane.o CC [M] drivers/gpu/drm/xe/i915-display/intel_display_power.o CC drivers/gpu/drm/i915/display/i9xx_display_sr.o CC [M] drivers/gpu/drm/xe/i915-display/intel_display_power_map.o CC drivers/gpu/drm/i915/display/i9xx_wm.o CC [M] drivers/gpu/drm/xe/i915-display/intel_display_power_well.o CC drivers/gpu/drm/i915/display/intel_alpm.o CC drivers/gpu/drm/i915/display/intel_atomic.o CC [M] drivers/gpu/drm/xe/i915-display/intel_display_trace.o CC drivers/gpu/drm/i915/display/intel_atomic_plane.o CC drivers/gpu/drm/i915/display/intel_audio.o CC [M] drivers/gpu/drm/xe/i915-display/intel_display_wa.o CC drivers/gpu/drm/i915/display/intel_bios.o CC drivers/gpu/drm/i915/display/intel_bo.o CC drivers/gpu/drm/i915/display/intel_bw.o CC [M] drivers/gpu/drm/xe/i915-display/intel_dkl_phy.o CC [M] drivers/gpu/drm/xe/i915-display/intel_dmc.o CC drivers/gpu/drm/i915/display/intel_cdclk.o CC [M] drivers/gpu/drm/xe/i915-display/intel_dp.o CC drivers/gpu/drm/i915/display/intel_color.o CC [M] drivers/gpu/drm/xe/i915-display/intel_dp_aux.o CC [M] drivers/gpu/drm/xe/i915-display/intel_dp_aux_backlight.o CC drivers/gpu/drm/i915/display/intel_combo_phy.o CC [M] drivers/gpu/drm/xe/i915-display/intel_dp_hdcp.o CC drivers/gpu/drm/i915/display/intel_connector.o CC [M] drivers/gpu/drm/xe/i915-display/intel_dp_link_training.o CC drivers/gpu/drm/i915/display/intel_crtc.o CC drivers/gpu/drm/i915/display/intel_crtc_state_dump.o CC [M] drivers/gpu/drm/xe/i915-display/intel_dp_mst.o CC drivers/gpu/drm/i915/display/intel_cursor.o CC drivers/gpu/drm/i915/display/intel_display.o CC [M] drivers/gpu/drm/xe/i915-display/intel_dp_test.o CC [M] drivers/gpu/drm/xe/i915-display/intel_dpll.o CC drivers/gpu/drm/i915/display/intel_display_conversion.o CC drivers/gpu/drm/i915/display/intel_display_driver.o CC drivers/gpu/drm/i915/display/intel_display_irq.o CC [M] drivers/gpu/drm/xe/i915-display/intel_dpll_mgr.o CC drivers/gpu/drm/i915/display/intel_display_params.o CC [M] drivers/gpu/drm/xe/i915-display/intel_dpt_common.o CC [M] drivers/gpu/drm/xe/i915-display/intel_drrs.o CC drivers/gpu/drm/i915/display/intel_display_power.o CC drivers/gpu/drm/i915/display/intel_display_power_map.o CC drivers/gpu/drm/i915/display/intel_display_power_well.o CC [M] drivers/gpu/drm/xe/i915-display/intel_dsb.o CC drivers/gpu/drm/i915/display/intel_display_reset.o CC [M] drivers/gpu/drm/xe/i915-display/intel_dsi.o CC drivers/gpu/drm/i915/display/intel_display_rps.o CC drivers/gpu/drm/i915/display/intel_display_snapshot.o CC drivers/gpu/drm/i915/display/intel_display_wa.o CC drivers/gpu/drm/i915/display/intel_dmc.o CC [M] drivers/gpu/drm/xe/i915-display/intel_dsi_dcs_backlight.o CC drivers/gpu/drm/i915/display/intel_dmc_wl.o CC drivers/gpu/drm/i915/display/intel_dpio_phy.o CC [M] drivers/gpu/drm/xe/i915-display/intel_dsi_vbt.o CC drivers/gpu/drm/i915/display/intel_dpll.o CC [M] drivers/gpu/drm/xe/i915-display/intel_encoder.o CC [M] drivers/gpu/drm/xe/i915-display/intel_fb.o CC [M] drivers/gpu/drm/xe/i915-display/intel_fbc.o CC [M] drivers/gpu/drm/xe/i915-display/intel_fdi.o CC [M] drivers/gpu/drm/xe/i915-display/intel_fifo_underrun.o CC drivers/gpu/drm/i915/display/intel_dpll_mgr.o CC drivers/gpu/drm/i915/display/intel_dpt.o CC drivers/gpu/drm/i915/display/intel_dpt_common.o CC [M] drivers/gpu/drm/xe/i915-display/intel_frontbuffer.o CC drivers/gpu/drm/i915/display/intel_drrs.o CC drivers/gpu/drm/i915/display/intel_dsb.o CC [M] drivers/gpu/drm/xe/i915-display/intel_global_state.o CC [M] drivers/gpu/drm/xe/i915-display/intel_gmbus.o CC drivers/gpu/drm/i915/display/intel_dsb_buffer.o CC drivers/gpu/drm/i915/display/intel_fb.o CC [M] drivers/gpu/drm/xe/i915-display/intel_hdcp.o CC drivers/gpu/drm/i915/display/intel_fb_bo.o CC drivers/gpu/drm/i915/display/intel_fb_pin.o CC [M] drivers/gpu/drm/xe/i915-display/intel_hdcp_gsc_message.o CC [M] drivers/gpu/drm/xe/i915-display/intel_hdmi.o CC drivers/gpu/drm/i915/display/intel_fbc.o CC drivers/gpu/drm/i915/display/intel_fdi.o CC [M] drivers/gpu/drm/xe/i915-display/intel_hotplug.o CC drivers/gpu/drm/i915/display/intel_fifo_underrun.o CC drivers/gpu/drm/i915/display/intel_frontbuffer.o CC [M] drivers/gpu/drm/xe/i915-display/intel_hotplug_irq.o CC [M] drivers/gpu/drm/xe/i915-display/intel_hti.o CC [M] drivers/gpu/drm/xe/i915-display/intel_link_bw.o CC drivers/gpu/drm/i915/display/intel_global_state.o CC [M] drivers/gpu/drm/xe/i915-display/intel_lspcon.o CC drivers/gpu/drm/i915/display/intel_hdcp.o CC drivers/gpu/drm/i915/display/intel_hdcp_gsc.o CC [M] drivers/gpu/drm/xe/i915-display/intel_modeset_lock.o CC drivers/gpu/drm/i915/display/intel_hdcp_gsc_message.o CC [M] drivers/gpu/drm/xe/i915-display/intel_modeset_setup.o CC drivers/gpu/drm/i915/display/intel_hotplug.o CC [M] drivers/gpu/drm/xe/i915-display/intel_modeset_verify.o CC drivers/gpu/drm/i915/display/intel_hotplug_irq.o CC [M] drivers/gpu/drm/xe/i915-display/intel_panel.o CC [M] drivers/gpu/drm/xe/i915-display/intel_pfit.o CC drivers/gpu/drm/i915/display/intel_hti.o CC [M] drivers/gpu/drm/xe/i915-display/intel_pmdemand.o CC drivers/gpu/drm/i915/display/intel_link_bw.o CC drivers/gpu/drm/i915/display/intel_load_detect.o CC [M] drivers/gpu/drm/xe/i915-display/intel_pps.o CC [M] drivers/gpu/drm/xe/i915-display/intel_psr.o CC drivers/gpu/drm/i915/display/intel_lpe_audio.o CC drivers/gpu/drm/i915/display/intel_modeset_lock.o CC [M] drivers/gpu/drm/xe/i915-display/intel_qp_tables.o CC [M] drivers/gpu/drm/xe/i915-display/intel_quirks.o CC drivers/gpu/drm/i915/display/intel_modeset_setup.o CC [M] drivers/gpu/drm/xe/i915-display/intel_snps_phy.o CC drivers/gpu/drm/i915/display/intel_modeset_verify.o CC drivers/gpu/drm/i915/display/intel_overlay.o CC drivers/gpu/drm/i915/display/intel_pch_display.o CC drivers/gpu/drm/i915/display/intel_pch_refclk.o CC drivers/gpu/drm/i915/display/intel_plane_initial.o CC [M] drivers/gpu/drm/xe/i915-display/intel_tc.o CC [M] drivers/gpu/drm/xe/i915-display/intel_vblank.o CC [M] drivers/gpu/drm/xe/i915-display/intel_vdsc.o CC [M] drivers/gpu/drm/xe/i915-display/intel_vga.o CC [M] drivers/gpu/drm/xe/i915-display/intel_vrr.o CC drivers/gpu/drm/i915/display/intel_pmdemand.o CC [M] drivers/gpu/drm/xe/i915-display/intel_dmc_wl.o CC [M] drivers/gpu/drm/xe/i915-display/intel_wm.o CC drivers/gpu/drm/i915/display/intel_psr.o CC drivers/gpu/drm/i915/display/intel_quirks.o CC drivers/gpu/drm/i915/display/intel_sprite.o CC [M] drivers/gpu/drm/xe/i915-display/skl_scaler.o CC drivers/gpu/drm/i915/display/intel_sprite_uapi.o CC drivers/gpu/drm/i915/display/intel_tc.o CC [M] drivers/gpu/drm/xe/i915-display/skl_universal_plane.o CC drivers/gpu/drm/i915/display/intel_vblank.o CC drivers/gpu/drm/i915/display/intel_vga.o CC [M] drivers/gpu/drm/xe/i915-display/skl_watermark.o CC [M] drivers/gpu/drm/xe/i915-display/intel_acpi.o CC [M] drivers/gpu/drm/xe/i915-display/intel_opregion.o CC [M] drivers/gpu/drm/xe/xe_debugfs.o CC drivers/gpu/drm/i915/display/intel_wm.o CC [M] drivers/gpu/drm/xe/xe_gt_debugfs.o CC [M] drivers/gpu/drm/xe/xe_gt_sriov_vf_debugfs.o CC drivers/gpu/drm/i915/display/skl_scaler.o CC drivers/gpu/drm/i915/display/skl_universal_plane.o CC drivers/gpu/drm/i915/display/skl_watermark.o CC [M] drivers/gpu/drm/xe/xe_gt_stats.o CC [M] drivers/gpu/drm/xe/xe_guc_debugfs.o CC [M] drivers/gpu/drm/xe/xe_huc_debugfs.o CC [M] drivers/gpu/drm/xe/xe_uc_debugfs.o CC drivers/gpu/drm/i915/display/intel_acpi.o CC drivers/gpu/drm/i915/display/intel_opregion.o CC [M] drivers/gpu/drm/xe/i915-display/intel_display_debugfs.o CC drivers/gpu/drm/i915/display/intel_display_debugfs.o CC [M] drivers/gpu/drm/xe/i915-display/intel_display_debugfs_params.o CC [M] drivers/gpu/drm/xe/i915-display/intel_pipe_crc.o CC drivers/gpu/drm/i915/display/intel_display_debugfs_params.o CC drivers/gpu/drm/i915/display/intel_pipe_crc.o CC drivers/gpu/drm/i915/display/dvo_ch7017.o CC drivers/gpu/drm/i915/display/dvo_ch7xxx.o CC drivers/gpu/drm/i915/display/dvo_ivch.o CC drivers/gpu/drm/i915/display/dvo_ns2501.o CC drivers/gpu/drm/i915/display/dvo_sil164.o CC drivers/gpu/drm/i915/display/dvo_tfp410.o CC drivers/gpu/drm/i915/display/g4x_dp.o CC drivers/gpu/drm/i915/display/g4x_hdmi.o CC drivers/gpu/drm/i915/display/icl_dsi.o CC drivers/gpu/drm/i915/display/intel_backlight.o CC drivers/gpu/drm/i915/display/intel_crt.o CC drivers/gpu/drm/i915/display/intel_cx0_phy.o CC drivers/gpu/drm/i915/display/intel_ddi.o CC drivers/gpu/drm/i915/display/intel_ddi_buf_trans.o CC drivers/gpu/drm/i915/display/intel_display_device.o CC drivers/gpu/drm/i915/display/intel_display_trace.o CC drivers/gpu/drm/i915/display/intel_dkl_phy.o CC drivers/gpu/drm/i915/display/intel_dp.o CC drivers/gpu/drm/i915/display/intel_dp_aux.o CC drivers/gpu/drm/i915/display/intel_dp_aux_backlight.o CC drivers/gpu/drm/i915/display/intel_dp_hdcp.o CC drivers/gpu/drm/i915/display/intel_dp_link_training.o CC drivers/gpu/drm/i915/display/intel_dp_mst.o CC drivers/gpu/drm/i915/display/intel_dp_test.o CC drivers/gpu/drm/i915/display/intel_dsi.o CC drivers/gpu/drm/i915/display/intel_dsi_dcs_backlight.o CC drivers/gpu/drm/i915/display/intel_dsi_vbt.o CC drivers/gpu/drm/i915/display/intel_dvo.o CC drivers/gpu/drm/i915/display/intel_encoder.o CC drivers/gpu/drm/i915/display/intel_gmbus.o CC drivers/gpu/drm/i915/display/intel_hdmi.o CC drivers/gpu/drm/i915/display/intel_lspcon.o CC drivers/gpu/drm/i915/display/intel_lvds.o CC drivers/gpu/drm/i915/display/intel_panel.o CC drivers/gpu/drm/i915/display/intel_pfit.o CC drivers/gpu/drm/i915/display/intel_pps.o CC drivers/gpu/drm/i915/display/intel_qp_tables.o CC drivers/gpu/drm/i915/display/intel_sdvo.o CC drivers/gpu/drm/i915/display/intel_snps_phy.o CC drivers/gpu/drm/i915/display/intel_tv.o CC drivers/gpu/drm/i915/display/intel_vdsc.o CC drivers/gpu/drm/i915/display/intel_vrr.o CC drivers/gpu/drm/i915/display/vlv_dsi.o CC drivers/gpu/drm/i915/display/vlv_dsi_pll.o CC drivers/gpu/drm/i915/i915_perf.o CC drivers/gpu/drm/i915/pxp/intel_pxp.o CC drivers/gpu/drm/i915/pxp/intel_pxp_huc.o CC drivers/gpu/drm/i915/pxp/intel_pxp_tee.o CC drivers/gpu/drm/i915/i915_gpu_error.o CC drivers/gpu/drm/i915/i915_vgpu.o LD [M] drivers/gpu/drm/xe/xe.o AR drivers/gpu/drm/i915/built-in.a AR drivers/gpu/drm/built-in.a AR drivers/gpu/built-in.a AR drivers/built-in.a AR built-in.a AR vmlinux.a LD vmlinux.o OBJCOPY modules.builtin.modinfo GEN modules.builtin MODPOST Module.symvers CC .vmlinux.export.o CC [M] fs/efivarfs/efivarfs.mod.o CC [M] .module-common.o CC [M] drivers/gpu/drm/drm_exec.mod.o CC [M] drivers/gpu/drm/drm_gpuvm.mod.o CC [M] drivers/gpu/drm/drm_suballoc_helper.mod.o CC [M] drivers/gpu/drm/drm_ttm_helper.mod.o CC [M] drivers/gpu/drm/scheduler/gpu-sched.mod.o CC [M] drivers/gpu/drm/xe/xe.mod.o CC [M] drivers/thermal/intel/x86_pkg_temp_thermal.mod.o CC [M] net/netfilter/nf_log_syslog.mod.o CC [M] net/netfilter/xt_mark.mod.o CC [M] net/netfilter/xt_nat.mod.o CC [M] net/netfilter/xt_LOG.mod.o CC [M] net/netfilter/xt_MASQUERADE.mod.o CC [M] net/netfilter/xt_addrtype.mod.o CC [M] net/ipv4/netfilter/iptable_nat.mod.o LD [M] fs/efivarfs/efivarfs.ko LD [M] drivers/gpu/drm/drm_gpuvm.ko LD [M] drivers/gpu/drm/drm_ttm_helper.ko LD [M] drivers/gpu/drm/scheduler/gpu-sched.ko LD [M] drivers/thermal/intel/x86_pkg_temp_thermal.ko LD [M] net/netfilter/nf_log_syslog.ko LD [M] net/netfilter/xt_mark.ko LD [M] net/netfilter/xt_nat.ko LD [M] net/netfilter/xt_LOG.ko LD [M] net/netfilter/xt_addrtype.ko LD [M] net/netfilter/xt_MASQUERADE.ko LD [M] net/ipv4/netfilter/iptable_nat.ko LD [M] drivers/gpu/drm/drm_suballoc_helper.ko LD [M] drivers/gpu/drm/drm_exec.ko LD [M] drivers/gpu/drm/xe/xe.ko UPD include/generated/utsversion.h CC init/version-timestamp.o KSYMS .tmp_vmlinux0.kallsyms.S AS .tmp_vmlinux0.kallsyms.o LD .tmp_vmlinux1 NM .tmp_vmlinux1.syms KSYMS .tmp_vmlinux1.kallsyms.S AS .tmp_vmlinux1.kallsyms.o LD .tmp_vmlinux2 NM .tmp_vmlinux2.syms KSYMS .tmp_vmlinux2.kallsyms.S AS .tmp_vmlinux2.kallsyms.o LD vmlinux NM System.map SORTTAB vmlinux RELOCS arch/x86/boot/compressed/vmlinux.relocs RSTRIP vmlinux CC arch/x86/boot/a20.o AS arch/x86/boot/bioscall.o CC arch/x86/boot/cmdline.o AS arch/x86/boot/copy.o HOSTCC arch/x86/boot/mkcpustr CC arch/x86/boot/cpuflags.o CC arch/x86/boot/cpucheck.o CC arch/x86/boot/early_serial_console.o CC arch/x86/boot/edd.o CC arch/x86/boot/main.o CC arch/x86/boot/memory.o CC arch/x86/boot/pm.o AS arch/x86/boot/pmjump.o CC arch/x86/boot/printf.o CC arch/x86/boot/regs.o CC arch/x86/boot/string.o CC arch/x86/boot/tty.o CC arch/x86/boot/video.o CC arch/x86/boot/video-mode.o CC arch/x86/boot/version.o CC arch/x86/boot/video-vga.o CC arch/x86/boot/video-vesa.o CC arch/x86/boot/video-bios.o HOSTCC arch/x86/boot/tools/build LDS arch/x86/boot/compressed/vmlinux.lds AS arch/x86/boot/compressed/kernel_info.o AS arch/x86/boot/compressed/head_32.o VOFFSET arch/x86/boot/compressed/../voffset.h CC arch/x86/boot/compressed/string.o CPUSTR arch/x86/boot/cpustr.h CC arch/x86/boot/compressed/cmdline.o CC arch/x86/boot/compressed/error.o OBJCOPY arch/x86/boot/compressed/vmlinux.bin CC arch/x86/boot/cpu.o HOSTCC arch/x86/boot/compressed/mkpiggy CC arch/x86/boot/compressed/cpuflags.o CC arch/x86/boot/compressed/early_serial_console.o CC arch/x86/boot/compressed/kaslr.o CC arch/x86/boot/compressed/acpi.o CC arch/x86/boot/compressed/efi.o GZIP arch/x86/boot/compressed/vmlinux.bin.gz CC arch/x86/boot/compressed/misc.o MKPIGGY arch/x86/boot/compressed/piggy.S AS arch/x86/boot/compressed/piggy.o LD arch/x86/boot/compressed/vmlinux ZOFFSET arch/x86/boot/zoffset.h OBJCOPY arch/x86/boot/vmlinux.bin AS arch/x86/boot/header.o LD arch/x86/boot/setup.elf OBJCOPY arch/x86/boot/setup.bin BUILD arch/x86/boot/bzImage Kernel: arch/x86/boot/bzImage is ready (#1) run-parts: executing /workspace/ci/hooks/20-kernel-doc + SRC_DIR=/workspace/kernel + cd /workspace/kernel + find drivers/gpu/drm/xe/ -name '*.[ch]' -not -path 'drivers/gpu/drm/xe/display/*' + xargs ./scripts/kernel-doc -Werror -none include/uapi/drm/xe_drm.h All hooks done ^ permalink raw reply [flat|nested] 22+ messages in thread
* ✓ CI.checksparse: success for series starting with [v3,1/1] drm/xe/guc: Fix GuC log/ct output via debugfs 2025-01-07 20:22 [PATCH v3 1/1] drm/xe/guc: Fix GuC log/ct output via debugfs Julia Filipchuk ` (5 preceding siblings ...) 2025-01-07 21:28 ` ✓ CI.Hooks: " Patchwork @ 2025-01-07 21:30 ` Patchwork 2025-01-07 21:55 ` ✓ Xe.CI.BAT: " Patchwork 2025-01-09 10:47 ` ✗ Xe.CI.Full: failure " Patchwork 8 siblings, 0 replies; 22+ messages in thread From: Patchwork @ 2025-01-07 21:30 UTC (permalink / raw) To: Julia Filipchuk; +Cc: intel-xe == Series Details == Series: series starting with [v3,1/1] drm/xe/guc: Fix GuC log/ct output via debugfs URL : https://patchwork.freedesktop.org/series/143203/ State : success == Summary == + trap cleanup EXIT + KERNEL=/kernel + MT=/root/linux/maintainer-tools + git clone https://gitlab.freedesktop.org/drm/maintainer-tools /root/linux/maintainer-tools Cloning into '/root/linux/maintainer-tools'... warning: redirecting to https://gitlab.freedesktop.org/drm/maintainer-tools.git/ + make -C /root/linux/maintainer-tools make: Entering directory '/root/linux/maintainer-tools' cc -O2 -g -Wextra -o remap-log remap-log.c make: Leaving directory '/root/linux/maintainer-tools' + cd /kernel + git config --global --add safe.directory /kernel + /root/linux/maintainer-tools/dim sparse --fast dbd476153d41352ad6022088be16301051b9bce7 Sparse version: 0.6.4 (Ubuntu: 0.6.4-4ubuntu3) Fast mode used, each commit won't be checked separately. Okay! + cleanup ++ stat -c %u:%g /kernel + chown -R 1003:1003 /kernel ^ permalink raw reply [flat|nested] 22+ messages in thread
* ✓ Xe.CI.BAT: success for series starting with [v3,1/1] drm/xe/guc: Fix GuC log/ct output via debugfs 2025-01-07 20:22 [PATCH v3 1/1] drm/xe/guc: Fix GuC log/ct output via debugfs Julia Filipchuk ` (6 preceding siblings ...) 2025-01-07 21:30 ` ✓ CI.checksparse: " Patchwork @ 2025-01-07 21:55 ` Patchwork 2025-01-09 10:47 ` ✗ Xe.CI.Full: failure " Patchwork 8 siblings, 0 replies; 22+ messages in thread From: Patchwork @ 2025-01-07 21:55 UTC (permalink / raw) To: Julia Filipchuk; +Cc: intel-xe [-- Attachment #1: Type: text/plain, Size: 1823 bytes --] == Series Details == Series: series starting with [v3,1/1] drm/xe/guc: Fix GuC log/ct output via debugfs URL : https://patchwork.freedesktop.org/series/143203/ State : success == Summary == CI Bug Log - changes from xe-2450-dfcd517d1169ab05be63134ba5cbc7bfaf030eb1_BAT -> xe-pw-143203v1_BAT ==================================================== Summary ------- **SUCCESS** No regressions found. Participating hosts (9 -> 8) ------------------------------ Missing (1): bat-adlp-vm Known issues ------------ Here are the changes found in xe-pw-143203v1_BAT that come from known issues: ### IGT changes ### #### Issues hit #### * igt@xe_live_ktest@xe_migrate@xe_validate_ccs_kunit: - bat-adlp-vf: NOTRUN -> [SKIP][1] ([Intel XE#2229]) [1]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-143203v1/bat-adlp-vf/igt@xe_live_ktest@xe_migrate@xe_validate_ccs_kunit.html #### Possible fixes #### * igt@xe_live_ktest@xe_migrate: - bat-adlp-vf: [DMESG-FAIL][2] -> [PASS][3] +1 other test pass [2]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-2450-dfcd517d1169ab05be63134ba5cbc7bfaf030eb1/bat-adlp-vf/igt@xe_live_ktest@xe_migrate.html [3]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-143203v1/bat-adlp-vf/igt@xe_live_ktest@xe_migrate.html [Intel XE#2229]: https://gitlab.freedesktop.org/drm/xe/kernel/issues/2229 Build changes ------------- * Linux: xe-2450-dfcd517d1169ab05be63134ba5cbc7bfaf030eb1 -> xe-pw-143203v1 IGT_8179: 183b33f81365dd4a57fe3100a13d3fb13788d158 @ https://gitlab.freedesktop.org/drm/igt-gpu-tools.git xe-2450-dfcd517d1169ab05be63134ba5cbc7bfaf030eb1: dfcd517d1169ab05be63134ba5cbc7bfaf030eb1 xe-pw-143203v1: 143203v1 == Logs == For more details see: https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-143203v1/index.html [-- Attachment #2: Type: text/html, Size: 2416 bytes --] ^ permalink raw reply [flat|nested] 22+ messages in thread
* ✗ Xe.CI.Full: failure for series starting with [v3,1/1] drm/xe/guc: Fix GuC log/ct output via debugfs 2025-01-07 20:22 [PATCH v3 1/1] drm/xe/guc: Fix GuC log/ct output via debugfs Julia Filipchuk ` (7 preceding siblings ...) 2025-01-07 21:55 ` ✓ Xe.CI.BAT: " Patchwork @ 2025-01-09 10:47 ` Patchwork 8 siblings, 0 replies; 22+ messages in thread From: Patchwork @ 2025-01-09 10:47 UTC (permalink / raw) To: Julia Filipchuk; +Cc: intel-xe [-- Attachment #1: Type: text/plain, Size: 104513 bytes --] == Series Details == Series: series starting with [v3,1/1] drm/xe/guc: Fix GuC log/ct output via debugfs URL : https://patchwork.freedesktop.org/series/143203/ State : failure == Summary == CI Bug Log - changes from xe-2450-dfcd517d1169ab05be63134ba5cbc7bfaf030eb1_full -> xe-pw-143203v1_full ==================================================== Summary ------- **FAILURE** Serious unknown changes coming with xe-pw-143203v1_full absolutely need to be verified manually. If you think the reported changes have nothing to do with the changes introduced in xe-pw-143203v1_full, please notify your bug team (I915-ci-infra@lists.freedesktop.org) to allow them to document this new failure mode, which will reduce false positives in CI. Participating hosts (4 -> 4) ------------------------------ No changes in participating hosts Possible new issues ------------------- Here are the unknown changes that may have been introduced in xe-pw-143203v1_full: ### IGT changes ### #### Possible regressions #### * igt@kms_plane@plane-panning-bottom-right-suspend: - shard-bmg: [PASS][1] -> [FAIL][2] +3 other tests fail [1]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-2450-dfcd517d1169ab05be63134ba5cbc7bfaf030eb1/shard-bmg-3/igt@kms_plane@plane-panning-bottom-right-suspend.html [2]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-143203v1/shard-bmg-5/igt@kms_plane@plane-panning-bottom-right-suspend.html Known issues ------------ Here are the changes found in xe-pw-143203v1_full that come from known issues: ### IGT changes ### #### Issues hit #### * igt@core_getversion@all-cards: - shard-dg2-set2: [PASS][3] -> [FAIL][4] ([Intel XE#3440]) [3]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-2450-dfcd517d1169ab05be63134ba5cbc7bfaf030eb1/shard-dg2-434/igt@core_getversion@all-cards.html [4]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-143203v1/shard-dg2-466/igt@core_getversion@all-cards.html * igt@intel_hwmon@hwmon-write: - shard-lnl: NOTRUN -> [SKIP][5] ([Intel XE#1125]) [5]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-143203v1/shard-lnl-5/igt@intel_hwmon@hwmon-write.html * igt@kms_async_flips@async-flip-suspend-resume: - shard-adlp: NOTRUN -> [DMESG-WARN][6] ([Intel XE#1033]) +2 other tests dmesg-warn [6]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-143203v1/shard-adlp-4/igt@kms_async_flips@async-flip-suspend-resume.html * igt@kms_async_flips@async-flip-with-page-flip-events@pipe-b-hdmi-a-6-4-mc-ccs: - shard-dg2-set2: NOTRUN -> [SKIP][7] ([Intel XE#2550]) +23 other tests skip [7]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-143203v1/shard-dg2-436/igt@kms_async_flips@async-flip-with-page-flip-events@pipe-b-hdmi-a-6-4-mc-ccs.html * igt@kms_async_flips@crc-atomic@pipe-b-hdmi-a-1: - shard-adlp: [PASS][8] -> [DMESG-FAIL][9] ([Intel XE#1033]) [8]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-2450-dfcd517d1169ab05be63134ba5cbc7bfaf030eb1/shard-adlp-3/igt@kms_async_flips@crc-atomic@pipe-b-hdmi-a-1.html [9]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-143203v1/shard-adlp-8/igt@kms_async_flips@crc-atomic@pipe-b-hdmi-a-1.html * igt@kms_atomic_transition@modeset-transition-nonblocking-fencing: - shard-dg2-set2: [PASS][10] -> [SKIP][11] ([Intel XE#2423] / [i915#2575]) +36 other tests skip [10]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-2450-dfcd517d1169ab05be63134ba5cbc7bfaf030eb1/shard-dg2-434/igt@kms_atomic_transition@modeset-transition-nonblocking-fencing.html [11]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-143203v1/shard-dg2-466/igt@kms_atomic_transition@modeset-transition-nonblocking-fencing.html * igt@kms_atomic_transition@plane-all-modeset-transition-fencing-internal-panels: - shard-bmg: NOTRUN -> [SKIP][12] ([Intel XE#2370]) [12]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-143203v1/shard-bmg-3/igt@kms_atomic_transition@plane-all-modeset-transition-fencing-internal-panels.html * igt@kms_big_fb@4-tiled-64bpp-rotate-0: - shard-adlp: NOTRUN -> [SKIP][13] ([Intel XE#1124]) +1 other test skip [13]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-143203v1/shard-adlp-4/igt@kms_big_fb@4-tiled-64bpp-rotate-0.html * igt@kms_big_fb@4-tiled-64bpp-rotate-90: - shard-bmg: NOTRUN -> [SKIP][14] ([Intel XE#2327]) +1 other test skip [14]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-143203v1/shard-bmg-3/igt@kms_big_fb@4-tiled-64bpp-rotate-90.html * igt@kms_big_fb@linear-16bpp-rotate-90: - shard-dg2-set2: NOTRUN -> [SKIP][15] ([Intel XE#316]) +2 other tests skip [15]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-143203v1/shard-dg2-434/igt@kms_big_fb@linear-16bpp-rotate-90.html * igt@kms_big_fb@linear-32bpp-rotate-270: - shard-lnl: NOTRUN -> [SKIP][16] ([Intel XE#1407]) [16]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-143203v1/shard-lnl-3/igt@kms_big_fb@linear-32bpp-rotate-270.html * igt@kms_big_fb@linear-32bpp-rotate-90: - shard-adlp: NOTRUN -> [SKIP][17] ([Intel XE#316]) +1 other test skip [17]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-143203v1/shard-adlp-4/igt@kms_big_fb@linear-32bpp-rotate-90.html * igt@kms_big_fb@x-tiled-max-hw-stride-64bpp-rotate-0-hflip: - shard-dg2-set2: [PASS][18] -> [SKIP][19] ([Intel XE#2136] / [Intel XE#2351]) [18]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-2450-dfcd517d1169ab05be63134ba5cbc7bfaf030eb1/shard-dg2-434/igt@kms_big_fb@x-tiled-max-hw-stride-64bpp-rotate-0-hflip.html [19]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-143203v1/shard-dg2-466/igt@kms_big_fb@x-tiled-max-hw-stride-64bpp-rotate-0-hflip.html * igt@kms_big_fb@x-tiled-max-hw-stride-64bpp-rotate-180-hflip: - shard-adlp: NOTRUN -> [DMESG-FAIL][20] ([Intel XE#1033]) [20]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-143203v1/shard-adlp-4/igt@kms_big_fb@x-tiled-max-hw-stride-64bpp-rotate-180-hflip.html * igt@kms_big_fb@y-tiled-32bpp-rotate-180: - shard-lnl: NOTRUN -> [SKIP][21] ([Intel XE#1124]) +3 other tests skip [21]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-143203v1/shard-lnl-3/igt@kms_big_fb@y-tiled-32bpp-rotate-180.html * igt@kms_big_fb@y-tiled-64bpp-rotate-270: - shard-bmg: NOTRUN -> [SKIP][22] ([Intel XE#1124]) +1 other test skip [22]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-143203v1/shard-bmg-5/igt@kms_big_fb@y-tiled-64bpp-rotate-270.html * igt@kms_big_fb@y-tiled-max-hw-stride-32bpp-rotate-0: - shard-dg2-set2: NOTRUN -> [SKIP][23] ([Intel XE#1124]) +5 other tests skip [23]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-143203v1/shard-dg2-436/igt@kms_big_fb@y-tiled-max-hw-stride-32bpp-rotate-0.html * igt@kms_bw@connected-linear-tiling-1-displays-3840x2160p: - shard-dg2-set2: NOTRUN -> [SKIP][24] ([Intel XE#367]) [24]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-143203v1/shard-dg2-436/igt@kms_bw@connected-linear-tiling-1-displays-3840x2160p.html * igt@kms_bw@connected-linear-tiling-3-displays-1920x1080p: - shard-dg2-set2: NOTRUN -> [SKIP][25] ([Intel XE#2191]) [25]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-143203v1/shard-dg2-434/igt@kms_bw@connected-linear-tiling-3-displays-1920x1080p.html * igt@kms_bw@connected-linear-tiling-3-displays-2560x1440p: - shard-lnl: NOTRUN -> [SKIP][26] ([Intel XE#2191]) [26]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-143203v1/shard-lnl-3/igt@kms_bw@connected-linear-tiling-3-displays-2560x1440p.html * igt@kms_bw@linear-tiling-2-displays-1920x1080p: - shard-bmg: NOTRUN -> [SKIP][27] ([Intel XE#367]) +1 other test skip [27]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-143203v1/shard-bmg-5/igt@kms_bw@linear-tiling-2-displays-1920x1080p.html * igt@kms_bw@linear-tiling-2-displays-2160x1440p: - shard-lnl: NOTRUN -> [SKIP][28] ([Intel XE#367]) [28]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-143203v1/shard-lnl-5/igt@kms_bw@linear-tiling-2-displays-2160x1440p.html * igt@kms_bw@linear-tiling-3-displays-2560x1440p: - shard-adlp: NOTRUN -> [SKIP][29] ([Intel XE#367]) [29]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-143203v1/shard-adlp-4/igt@kms_bw@linear-tiling-3-displays-2560x1440p.html * igt@kms_ccs@bad-rotation-90-y-tiled-gen12-mc-ccs: - shard-lnl: NOTRUN -> [SKIP][30] ([Intel XE#2887]) +2 other tests skip [30]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-143203v1/shard-lnl-3/igt@kms_ccs@bad-rotation-90-y-tiled-gen12-mc-ccs.html * igt@kms_ccs@bad-rotation-90-yf-tiled-ccs@pipe-c-hdmi-a-1: - shard-adlp: NOTRUN -> [SKIP][31] ([Intel XE#787]) +5 other tests skip [31]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-143203v1/shard-adlp-4/igt@kms_ccs@bad-rotation-90-yf-tiled-ccs@pipe-c-hdmi-a-1.html * igt@kms_ccs@crc-primary-basic-4-tiled-mtl-rc-ccs@pipe-b-hdmi-a-6: - shard-dg2-set2: NOTRUN -> [SKIP][32] ([Intel XE#787]) +125 other tests skip [32]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-143203v1/shard-dg2-436/igt@kms_ccs@crc-primary-basic-4-tiled-mtl-rc-ccs@pipe-b-hdmi-a-6.html * igt@kms_ccs@crc-primary-suspend-4-tiled-dg2-mc-ccs: - shard-bmg: NOTRUN -> [SKIP][33] ([Intel XE#3432]) [33]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-143203v1/shard-bmg-3/igt@kms_ccs@crc-primary-suspend-4-tiled-dg2-mc-ccs.html * igt@kms_ccs@crc-primary-suspend-4-tiled-dg2-rc-ccs-cc: - shard-lnl: NOTRUN -> [SKIP][34] ([Intel XE#3432]) +1 other test skip [34]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-143203v1/shard-lnl-3/igt@kms_ccs@crc-primary-suspend-4-tiled-dg2-rc-ccs-cc.html * igt@kms_ccs@crc-sprite-planes-basic-y-tiled-gen12-rc-ccs-cc: - shard-bmg: NOTRUN -> [SKIP][35] ([Intel XE#2887]) +6 other tests skip [35]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-143203v1/shard-bmg-5/igt@kms_ccs@crc-sprite-planes-basic-y-tiled-gen12-rc-ccs-cc.html * igt@kms_ccs@missing-ccs-buffer-4-tiled-mtl-mc-ccs@pipe-d-dp-4: - shard-dg2-set2: NOTRUN -> [SKIP][36] ([Intel XE#455] / [Intel XE#787]) +22 other tests skip [36]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-143203v1/shard-dg2-434/igt@kms_ccs@missing-ccs-buffer-4-tiled-mtl-mc-ccs@pipe-d-dp-4.html * igt@kms_ccs@missing-ccs-buffer-y-tiled-gen12-rc-ccs: - shard-adlp: NOTRUN -> [SKIP][37] ([Intel XE#455] / [Intel XE#787]) +3 other tests skip [37]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-143203v1/shard-adlp-4/igt@kms_ccs@missing-ccs-buffer-y-tiled-gen12-rc-ccs.html * igt@kms_ccs@random-ccs-data-4-tiled-bmg-ccs: - shard-lnl: NOTRUN -> [SKIP][38] ([Intel XE#2669]) +3 other tests skip [38]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-143203v1/shard-lnl-3/igt@kms_ccs@random-ccs-data-4-tiled-bmg-ccs.html * igt@kms_cdclk@mode-transition@pipe-b-edp-1: - shard-lnl: NOTRUN -> [SKIP][39] ([Intel XE#314]) +3 other tests skip [39]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-143203v1/shard-lnl-3/igt@kms_cdclk@mode-transition@pipe-b-edp-1.html * igt@kms_chamelium_color@ctm-green-to-red: - shard-adlp: NOTRUN -> [SKIP][40] ([Intel XE#306]) [40]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-143203v1/shard-adlp-4/igt@kms_chamelium_color@ctm-green-to-red.html * igt@kms_chamelium_frames@dp-crc-single: - shard-bmg: NOTRUN -> [SKIP][41] ([Intel XE#2252]) +3 other tests skip [41]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-143203v1/shard-bmg-5/igt@kms_chamelium_frames@dp-crc-single.html * igt@kms_chamelium_hpd@common-hpd-after-hibernate: - shard-adlp: NOTRUN -> [SKIP][42] ([Intel XE#373]) [42]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-143203v1/shard-adlp-4/igt@kms_chamelium_hpd@common-hpd-after-hibernate.html * igt@kms_chamelium_hpd@hdmi-hpd-for-each-pipe: - shard-dg2-set2: NOTRUN -> [SKIP][43] ([Intel XE#373]) +4 other tests skip [43]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-143203v1/shard-dg2-436/igt@kms_chamelium_hpd@hdmi-hpd-for-each-pipe.html * igt@kms_chamelium_hpd@vga-hpd: - shard-lnl: NOTRUN -> [SKIP][44] ([Intel XE#373]) +2 other tests skip [44]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-143203v1/shard-lnl-3/igt@kms_chamelium_hpd@vga-hpd.html * igt@kms_content_protection@dp-mst-type-1: - shard-bmg: NOTRUN -> [SKIP][45] ([Intel XE#2390]) [45]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-143203v1/shard-bmg-5/igt@kms_content_protection@dp-mst-type-1.html * igt@kms_content_protection@lic-type-0@pipe-a-dp-2: - shard-bmg: NOTRUN -> [FAIL][46] ([Intel XE#1178]) +1 other test fail [46]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-143203v1/shard-bmg-3/igt@kms_content_protection@lic-type-0@pipe-a-dp-2.html * igt@kms_cursor_crc@cursor-offscreen-512x170: - shard-dg2-set2: NOTRUN -> [SKIP][47] ([Intel XE#308]) [47]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-143203v1/shard-dg2-434/igt@kms_cursor_crc@cursor-offscreen-512x170.html * igt@kms_cursor_crc@cursor-offscreen-64x21: - shard-lnl: NOTRUN -> [SKIP][48] ([Intel XE#1424]) +1 other test skip [48]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-143203v1/shard-lnl-5/igt@kms_cursor_crc@cursor-offscreen-64x21.html * igt@kms_cursor_crc@cursor-random-512x512: - shard-adlp: NOTRUN -> [SKIP][49] ([Intel XE#308]) [49]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-143203v1/shard-adlp-4/igt@kms_cursor_crc@cursor-random-512x512.html * igt@kms_cursor_crc@cursor-rapid-movement-32x10: - shard-bmg: NOTRUN -> [SKIP][50] ([Intel XE#2320]) +3 other tests skip [50]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-143203v1/shard-bmg-3/igt@kms_cursor_crc@cursor-rapid-movement-32x10.html * igt@kms_cursor_legacy@2x-flip-vs-cursor-legacy: - shard-adlp: NOTRUN -> [SKIP][51] ([Intel XE#309]) +1 other test skip [51]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-143203v1/shard-adlp-4/igt@kms_cursor_legacy@2x-flip-vs-cursor-legacy.html * igt@kms_cursor_legacy@2x-nonblocking-modeset-vs-cursor-atomic: - shard-lnl: NOTRUN -> [SKIP][52] ([Intel XE#309]) [52]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-143203v1/shard-lnl-5/igt@kms_cursor_legacy@2x-nonblocking-modeset-vs-cursor-atomic.html * igt@kms_cursor_legacy@cursorb-vs-flipa-varying-size: - shard-bmg: [PASS][53] -> [DMESG-WARN][54] ([Intel XE#877]) [53]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-2450-dfcd517d1169ab05be63134ba5cbc7bfaf030eb1/shard-bmg-3/igt@kms_cursor_legacy@cursorb-vs-flipa-varying-size.html [54]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-143203v1/shard-bmg-7/igt@kms_cursor_legacy@cursorb-vs-flipa-varying-size.html * igt@kms_cursor_legacy@short-busy-flip-before-cursor-atomic-transitions-varying-size: - shard-lnl: NOTRUN -> [SKIP][55] ([Intel XE#323]) +1 other test skip [55]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-143203v1/shard-lnl-5/igt@kms_cursor_legacy@short-busy-flip-before-cursor-atomic-transitions-varying-size.html * igt@kms_display_modes@extended-mode-basic: - shard-lnl: NOTRUN -> [SKIP][56] ([Intel XE#3383]) [56]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-143203v1/shard-lnl-3/igt@kms_display_modes@extended-mode-basic.html * igt@kms_dsc@dsc-with-bpc: - shard-bmg: NOTRUN -> [SKIP][57] ([Intel XE#2244]) [57]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-143203v1/shard-bmg-3/igt@kms_dsc@dsc-with-bpc.html * igt@kms_fbcon_fbt@fbc: - shard-bmg: NOTRUN -> [FAIL][58] ([Intel XE#1695]) [58]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-143203v1/shard-bmg-5/igt@kms_fbcon_fbt@fbc.html * igt@kms_feature_discovery@psr2: - shard-dg2-set2: NOTRUN -> [SKIP][59] ([Intel XE#1135]) [59]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-143203v1/shard-dg2-434/igt@kms_feature_discovery@psr2.html * igt@kms_flip@2x-dpms-vs-vblank-race: - shard-dg2-set2: NOTRUN -> [SKIP][60] ([Intel XE#2423] / [i915#2575]) +8 other tests skip [60]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-143203v1/shard-dg2-466/igt@kms_flip@2x-dpms-vs-vblank-race.html * igt@kms_flip@2x-flip-vs-wf_vblank: - shard-adlp: NOTRUN -> [SKIP][61] ([Intel XE#310]) +1 other test skip [61]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-143203v1/shard-adlp-4/igt@kms_flip@2x-flip-vs-wf_vblank.html * igt@kms_flip@2x-plain-flip-fb-recreate: - shard-lnl: NOTRUN -> [SKIP][62] ([Intel XE#1421]) +1 other test skip [62]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-143203v1/shard-lnl-3/igt@kms_flip@2x-plain-flip-fb-recreate.html * igt@kms_flip@flip-vs-expired-vblank-interruptible: - shard-bmg: [PASS][63] -> [FAIL][64] ([Intel XE#2882] / [Intel XE#3288]) [63]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-2450-dfcd517d1169ab05be63134ba5cbc7bfaf030eb1/shard-bmg-7/igt@kms_flip@flip-vs-expired-vblank-interruptible.html [64]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-143203v1/shard-bmg-5/igt@kms_flip@flip-vs-expired-vblank-interruptible.html * igt@kms_flip@flip-vs-expired-vblank-interruptible@a-dp2: - shard-bmg: [PASS][65] -> [FAIL][66] ([Intel XE#3288] / [Intel XE#3321]) [65]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-2450-dfcd517d1169ab05be63134ba5cbc7bfaf030eb1/shard-bmg-7/igt@kms_flip@flip-vs-expired-vblank-interruptible@a-dp2.html [66]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-143203v1/shard-bmg-5/igt@kms_flip@flip-vs-expired-vblank-interruptible@a-dp2.html * igt@kms_flip@flip-vs-expired-vblank-interruptible@b-hdmi-a6: - shard-dg2-set2: [PASS][67] -> [FAIL][68] ([Intel XE#301]) +1 other test fail [67]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-2450-dfcd517d1169ab05be63134ba5cbc7bfaf030eb1/shard-dg2-435/igt@kms_flip@flip-vs-expired-vblank-interruptible@b-hdmi-a6.html [68]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-143203v1/shard-dg2-434/igt@kms_flip@flip-vs-expired-vblank-interruptible@b-hdmi-a6.html * igt@kms_flip@flip-vs-expired-vblank@a-dp2: - shard-bmg: [PASS][69] -> [FAIL][70] ([Intel XE#2882]) +2 other tests fail [69]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-2450-dfcd517d1169ab05be63134ba5cbc7bfaf030eb1/shard-bmg-5/igt@kms_flip@flip-vs-expired-vblank@a-dp2.html [70]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-143203v1/shard-bmg-3/igt@kms_flip@flip-vs-expired-vblank@a-dp2.html * igt@kms_flip@flip-vs-suspend-interruptible@b-dp2: - shard-bmg: [PASS][71] -> [INCOMPLETE][72] ([Intel XE#2597]) [71]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-2450-dfcd517d1169ab05be63134ba5cbc7bfaf030eb1/shard-bmg-7/igt@kms_flip@flip-vs-suspend-interruptible@b-dp2.html [72]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-143203v1/shard-bmg-5/igt@kms_flip@flip-vs-suspend-interruptible@b-dp2.html * igt@kms_flip_scaled_crc@flip-32bpp-ytile-to-32bpp-ytilegen12rcccs-upscaling: - shard-bmg: NOTRUN -> [SKIP][73] ([Intel XE#2293] / [Intel XE#2380]) +1 other test skip [73]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-143203v1/shard-bmg-3/igt@kms_flip_scaled_crc@flip-32bpp-ytile-to-32bpp-ytilegen12rcccs-upscaling.html * igt@kms_flip_scaled_crc@flip-64bpp-4tile-to-32bpp-4tiledg2rcccs-downscaling: - shard-bmg: NOTRUN -> [SKIP][74] ([Intel XE#2380]) +1 other test skip [74]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-143203v1/shard-bmg-5/igt@kms_flip_scaled_crc@flip-64bpp-4tile-to-32bpp-4tiledg2rcccs-downscaling.html * igt@kms_flip_scaled_crc@flip-64bpp-ytile-to-16bpp-ytile-downscaling@pipe-a-valid-mode: - shard-bmg: NOTRUN -> [SKIP][75] ([Intel XE#2293]) +1 other test skip [75]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-143203v1/shard-bmg-3/igt@kms_flip_scaled_crc@flip-64bpp-ytile-to-16bpp-ytile-downscaling@pipe-a-valid-mode.html * igt@kms_flip_scaled_crc@flip-64bpp-ytile-to-32bpp-ytile-downscaling: - shard-adlp: NOTRUN -> [DMESG-FAIL][76] ([Intel XE#1033] / [Intel XE#324]) +1 other test dmesg-fail [76]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-143203v1/shard-adlp-4/igt@kms_flip_scaled_crc@flip-64bpp-ytile-to-32bpp-ytile-downscaling.html * igt@kms_flip_scaled_crc@flip-64bpp-ytile-to-32bpp-ytile-downscaling@pipe-a-valid-mode: - shard-dg2-set2: NOTRUN -> [SKIP][77] ([Intel XE#455]) +8 other tests skip [77]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-143203v1/shard-dg2-435/igt@kms_flip_scaled_crc@flip-64bpp-ytile-to-32bpp-ytile-downscaling@pipe-a-valid-mode.html * igt@kms_flip_scaled_crc@flip-64bpp-ytile-to-32bpp-ytilegen12rcccs-upscaling: - shard-lnl: NOTRUN -> [SKIP][78] ([Intel XE#1401] / [Intel XE#1745]) +2 other tests skip [78]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-143203v1/shard-lnl-3/igt@kms_flip_scaled_crc@flip-64bpp-ytile-to-32bpp-ytilegen12rcccs-upscaling.html * igt@kms_flip_scaled_crc@flip-64bpp-ytile-to-32bpp-ytilegen12rcccs-upscaling@pipe-a-default-mode: - shard-lnl: NOTRUN -> [SKIP][79] ([Intel XE#1401]) +2 other tests skip [79]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-143203v1/shard-lnl-3/igt@kms_flip_scaled_crc@flip-64bpp-ytile-to-32bpp-ytilegen12rcccs-upscaling@pipe-a-default-mode.html * igt@kms_frontbuffer_tracking@drrs-1p-primscrn-spr-indfb-fullscreen: - shard-bmg: NOTRUN -> [SKIP][80] ([Intel XE#2311]) +10 other tests skip [80]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-143203v1/shard-bmg-5/igt@kms_frontbuffer_tracking@drrs-1p-primscrn-spr-indfb-fullscreen.html * igt@kms_frontbuffer_tracking@drrs-1p-primscrn-spr-indfb-onoff: - shard-lnl: NOTRUN -> [SKIP][81] ([Intel XE#651]) +7 other tests skip [81]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-143203v1/shard-lnl-3/igt@kms_frontbuffer_tracking@drrs-1p-primscrn-spr-indfb-onoff.html * igt@kms_frontbuffer_tracking@fbc-rgb101010-draw-mmap-wc: - shard-dg2-set2: [PASS][82] -> [SKIP][83] ([Intel XE#2136]) +10 other tests skip [82]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-2450-dfcd517d1169ab05be63134ba5cbc7bfaf030eb1/shard-dg2-434/igt@kms_frontbuffer_tracking@fbc-rgb101010-draw-mmap-wc.html [83]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-143203v1/shard-dg2-466/igt@kms_frontbuffer_tracking@fbc-rgb101010-draw-mmap-wc.html * igt@kms_frontbuffer_tracking@fbc-tiling-linear: - shard-bmg: NOTRUN -> [FAIL][84] ([Intel XE#2333]) +5 other tests fail [84]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-143203v1/shard-bmg-5/igt@kms_frontbuffer_tracking@fbc-tiling-linear.html * igt@kms_frontbuffer_tracking@fbcdrrs-2p-scndscrn-shrfb-plflip-blt: - shard-dg2-set2: NOTRUN -> [SKIP][85] ([Intel XE#651]) +11 other tests skip [85]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-143203v1/shard-dg2-434/igt@kms_frontbuffer_tracking@fbcdrrs-2p-scndscrn-shrfb-plflip-blt.html * igt@kms_frontbuffer_tracking@fbcdrrs-tiling-linear: - shard-adlp: NOTRUN -> [SKIP][86] ([Intel XE#651]) +1 other test skip [86]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-143203v1/shard-adlp-4/igt@kms_frontbuffer_tracking@fbcdrrs-tiling-linear.html * igt@kms_frontbuffer_tracking@fbcpsr-1p-primscrn-pri-indfb-draw-mmap-wc: - shard-dg2-set2: NOTRUN -> [SKIP][87] ([Intel XE#2136]) +3 other tests skip [87]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-143203v1/shard-dg2-466/igt@kms_frontbuffer_tracking@fbcpsr-1p-primscrn-pri-indfb-draw-mmap-wc.html * igt@kms_frontbuffer_tracking@fbcpsr-1p-primscrn-spr-indfb-onoff: - shard-adlp: NOTRUN -> [SKIP][88] ([Intel XE#653]) [88]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-143203v1/shard-adlp-4/igt@kms_frontbuffer_tracking@fbcpsr-1p-primscrn-spr-indfb-onoff.html * igt@kms_frontbuffer_tracking@fbcpsr-2p-scndscrn-shrfb-pgflip-blt: - shard-adlp: NOTRUN -> [SKIP][89] ([Intel XE#656]) +7 other tests skip [89]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-143203v1/shard-adlp-4/igt@kms_frontbuffer_tracking@fbcpsr-2p-scndscrn-shrfb-pgflip-blt.html * igt@kms_frontbuffer_tracking@fbcpsr-2p-scndscrn-shrfb-plflip-blt: - shard-bmg: NOTRUN -> [SKIP][90] ([Intel XE#2313]) +8 other tests skip [90]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-143203v1/shard-bmg-3/igt@kms_frontbuffer_tracking@fbcpsr-2p-scndscrn-shrfb-plflip-blt.html * igt@kms_frontbuffer_tracking@fbcpsr-2p-scndscrn-spr-indfb-draw-mmap-wc: - shard-lnl: NOTRUN -> [SKIP][91] ([Intel XE#656]) +11 other tests skip [91]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-143203v1/shard-lnl-3/igt@kms_frontbuffer_tracking@fbcpsr-2p-scndscrn-spr-indfb-draw-mmap-wc.html * igt@kms_frontbuffer_tracking@psr-2p-scndscrn-pri-shrfb-draw-mmap-wc: - shard-dg2-set2: NOTRUN -> [SKIP][92] ([Intel XE#653]) +11 other tests skip [92]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-143203v1/shard-dg2-434/igt@kms_frontbuffer_tracking@psr-2p-scndscrn-pri-shrfb-draw-mmap-wc.html * igt@kms_panel_fitting@atomic-fastset: - shard-bmg: NOTRUN -> [SKIP][93] ([Intel XE#2486]) [93]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-143203v1/shard-bmg-5/igt@kms_panel_fitting@atomic-fastset.html * igt@kms_plane_lowres@tiling-y: - shard-bmg: NOTRUN -> [SKIP][94] ([Intel XE#2393]) [94]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-143203v1/shard-bmg-5/igt@kms_plane_lowres@tiling-y.html * igt@kms_plane_scaling@intel-max-src-size@pipe-a-hdmi-a-6: - shard-dg2-set2: NOTRUN -> [FAIL][95] ([Intel XE#361]) +1 other test fail [95]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-143203v1/shard-dg2-434/igt@kms_plane_scaling@intel-max-src-size@pipe-a-hdmi-a-6.html * igt@kms_plane_scaling@plane-downscale-factor-0-25-with-pixel-format: - shard-adlp: NOTRUN -> [SKIP][96] ([Intel XE#2763] / [Intel XE#455]) +1 other test skip [96]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-143203v1/shard-adlp-4/igt@kms_plane_scaling@plane-downscale-factor-0-25-with-pixel-format.html * igt@kms_plane_scaling@plane-downscale-factor-0-25-with-pixel-format@pipe-a: - shard-adlp: NOTRUN -> [SKIP][97] ([Intel XE#2763]) +2 other tests skip [97]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-143203v1/shard-adlp-4/igt@kms_plane_scaling@plane-downscale-factor-0-25-with-pixel-format@pipe-a.html * igt@kms_plane_scaling@plane-downscale-factor-0-25-with-pixel-format@pipe-b: - shard-dg2-set2: NOTRUN -> [SKIP][98] ([Intel XE#2763]) +5 other tests skip [98]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-143203v1/shard-dg2-435/igt@kms_plane_scaling@plane-downscale-factor-0-25-with-pixel-format@pipe-b.html * igt@kms_plane_scaling@plane-downscale-factor-0-25-with-pixel-format@pipe-d: - shard-dg2-set2: NOTRUN -> [SKIP][99] ([Intel XE#2763] / [Intel XE#455]) +2 other tests skip [99]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-143203v1/shard-dg2-435/igt@kms_plane_scaling@plane-downscale-factor-0-25-with-pixel-format@pipe-d.html * igt@kms_plane_scaling@plane-downscale-factor-0-5-with-pixel-format@pipe-c: - shard-lnl: NOTRUN -> [SKIP][100] ([Intel XE#2763]) +7 other tests skip [100]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-143203v1/shard-lnl-5/igt@kms_plane_scaling@plane-downscale-factor-0-5-with-pixel-format@pipe-c.html * igt@kms_plane_scaling@planes-upscale-20x20-downscale-factor-0-5@pipe-b: - shard-bmg: NOTRUN -> [SKIP][101] ([Intel XE#2763]) +9 other tests skip [101]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-143203v1/shard-bmg-5/igt@kms_plane_scaling@planes-upscale-20x20-downscale-factor-0-5@pipe-b.html * igt@kms_pm_backlight@bad-brightness: - shard-adlp: NOTRUN -> [SKIP][102] ([Intel XE#870]) [102]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-143203v1/shard-adlp-4/igt@kms_pm_backlight@bad-brightness.html * igt@kms_pm_backlight@fade-with-dpms: - shard-dg2-set2: NOTRUN -> [SKIP][103] ([Intel XE#870]) [103]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-143203v1/shard-dg2-434/igt@kms_pm_backlight@fade-with-dpms.html * igt@kms_pm_dc@dc5-dpms-negative: - shard-lnl: NOTRUN -> [SKIP][104] ([Intel XE#1131]) [104]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-143203v1/shard-lnl-3/igt@kms_pm_dc@dc5-dpms-negative.html * igt@kms_pm_dc@dc5-retention-flops: - shard-dg2-set2: NOTRUN -> [SKIP][105] ([Intel XE#3309]) [105]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-143203v1/shard-dg2-434/igt@kms_pm_dc@dc5-retention-flops.html * igt@kms_pm_dc@dc6-dpms: - shard-adlp: NOTRUN -> [FAIL][106] ([Intel XE#718]) [106]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-143203v1/shard-adlp-4/igt@kms_pm_dc@dc6-dpms.html * igt@kms_pm_dc@dc6-psr: - shard-lnl: NOTRUN -> [FAIL][107] ([Intel XE#1430]) [107]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-143203v1/shard-lnl-5/igt@kms_pm_dc@dc6-psr.html * igt@kms_pm_rpm@cursor-dpms: - shard-dg2-set2: [PASS][108] -> [SKIP][109] ([Intel XE#2446]) +1 other test skip [108]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-2450-dfcd517d1169ab05be63134ba5cbc7bfaf030eb1/shard-dg2-434/igt@kms_pm_rpm@cursor-dpms.html [109]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-143203v1/shard-dg2-466/igt@kms_pm_rpm@cursor-dpms.html * igt@kms_pm_rpm@modeset-non-lpsp-stress-no-wait: - shard-lnl: NOTRUN -> [SKIP][110] ([Intel XE#1439] / [Intel XE#3141]) [110]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-143203v1/shard-lnl-5/igt@kms_pm_rpm@modeset-non-lpsp-stress-no-wait.html * igt@kms_psr2_sf@psr2-overlay-plane-move-continuous-sf: - shard-bmg: NOTRUN -> [SKIP][111] ([Intel XE#1489]) +3 other tests skip [111]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-143203v1/shard-bmg-3/igt@kms_psr2_sf@psr2-overlay-plane-move-continuous-sf.html * igt@kms_psr2_sf@psr2-overlay-primary-update-sf-dmg-area: - shard-dg2-set2: NOTRUN -> [SKIP][112] ([Intel XE#1489]) +3 other tests skip [112]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-143203v1/shard-dg2-434/igt@kms_psr2_sf@psr2-overlay-primary-update-sf-dmg-area.html * igt@kms_psr2_su@page_flip-xrgb8888: - shard-lnl: NOTRUN -> [SKIP][113] ([Intel XE#1128]) [113]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-143203v1/shard-lnl-3/igt@kms_psr2_su@page_flip-xrgb8888.html * igt@kms_psr@fbc-psr2-cursor-blt: - shard-adlp: NOTRUN -> [SKIP][114] ([Intel XE#2850] / [Intel XE#929]) +3 other tests skip [114]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-143203v1/shard-adlp-4/igt@kms_psr@fbc-psr2-cursor-blt.html * igt@kms_psr@fbc-psr2-primary-render: - shard-dg2-set2: NOTRUN -> [SKIP][115] ([Intel XE#2850] / [Intel XE#929]) +6 other tests skip [115]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-143203v1/shard-dg2-436/igt@kms_psr@fbc-psr2-primary-render.html * igt@kms_psr@psr-cursor-plane-onoff: - shard-bmg: NOTRUN -> [SKIP][116] ([Intel XE#2234] / [Intel XE#2850]) +4 other tests skip [116]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-143203v1/shard-bmg-3/igt@kms_psr@psr-cursor-plane-onoff.html * igt@kms_psr@psr-sprite-blt: - shard-dg2-set2: NOTRUN -> [SKIP][117] ([Intel XE#2136] / [Intel XE#2351]) +2 other tests skip [117]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-143203v1/shard-dg2-466/igt@kms_psr@psr-sprite-blt.html * igt@kms_rotation_crc@primary-y-tiled-reflect-x-180: - shard-bmg: NOTRUN -> [SKIP][118] ([Intel XE#2330]) +1 other test skip [118]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-143203v1/shard-bmg-3/igt@kms_rotation_crc@primary-y-tiled-reflect-x-180.html * igt@kms_rotation_crc@primary-y-tiled-reflect-x-90: - shard-adlp: NOTRUN -> [SKIP][119] ([Intel XE#3414]) [119]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-143203v1/shard-adlp-4/igt@kms_rotation_crc@primary-y-tiled-reflect-x-90.html * igt@kms_rotation_crc@sprite-rotation-90: - shard-dg2-set2: NOTRUN -> [SKIP][120] ([Intel XE#3414]) [120]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-143203v1/shard-dg2-434/igt@kms_rotation_crc@sprite-rotation-90.html * igt@kms_setmode@clone-exclusive-crtc: - shard-adlp: NOTRUN -> [SKIP][121] ([Intel XE#455]) +3 other tests skip [121]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-143203v1/shard-adlp-4/igt@kms_setmode@clone-exclusive-crtc.html * igt@kms_setmode@invalid-clone-single-crtc-stealing: - shard-lnl: NOTRUN -> [SKIP][122] ([Intel XE#1435]) [122]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-143203v1/shard-lnl-5/igt@kms_setmode@invalid-clone-single-crtc-stealing.html * igt@kms_tiled_display@basic-test-pattern-with-chamelium: - shard-dg2-set2: NOTRUN -> [SKIP][123] ([Intel XE#1500]) [123]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-143203v1/shard-dg2-434/igt@kms_tiled_display@basic-test-pattern-with-chamelium.html * igt@kms_vblank@ts-continuation-suspend: - shard-adlp: [PASS][124] -> [DMESG-WARN][125] ([Intel XE#2953]) +6 other tests dmesg-warn [124]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-2450-dfcd517d1169ab05be63134ba5cbc7bfaf030eb1/shard-adlp-1/igt@kms_vblank@ts-continuation-suspend.html [125]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-143203v1/shard-adlp-8/igt@kms_vblank@ts-continuation-suspend.html - shard-bmg: [PASS][126] -> [INCOMPLETE][127] ([Intel XE#3864]) +1 other test incomplete [126]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-2450-dfcd517d1169ab05be63134ba5cbc7bfaf030eb1/shard-bmg-3/igt@kms_vblank@ts-continuation-suspend.html [127]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-143203v1/shard-bmg-5/igt@kms_vblank@ts-continuation-suspend.html * igt@kms_vrr@cmrr: - shard-dg2-set2: NOTRUN -> [SKIP][128] ([Intel XE#2168]) [128]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-143203v1/shard-dg2-434/igt@kms_vrr@cmrr.html * igt@kms_vrr@negative-basic: - shard-lnl: NOTRUN -> [SKIP][129] ([Intel XE#1499]) +1 other test skip [129]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-143203v1/shard-lnl-5/igt@kms_vrr@negative-basic.html * igt@kms_writeback@writeback-check-output: - shard-bmg: NOTRUN -> [SKIP][130] ([Intel XE#756]) [130]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-143203v1/shard-bmg-5/igt@kms_writeback@writeback-check-output.html * igt@sriov_basic@enable-vfs-bind-unbind-each-numvfs-all: - shard-bmg: NOTRUN -> [SKIP][131] ([Intel XE#1091] / [Intel XE#2849]) [131]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-143203v1/shard-bmg-5/igt@sriov_basic@enable-vfs-bind-unbind-each-numvfs-all.html * igt@xe_ccs@suspend-resume@tile4-compressed-compfmt0-vram01-vram01: - shard-bmg: NOTRUN -> [FAIL][132] ([Intel XE#3981]) [132]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-143203v1/shard-bmg-3/igt@xe_ccs@suspend-resume@tile4-compressed-compfmt0-vram01-vram01.html * igt@xe_ccs@suspend-resume@xmajor-compressed-compfmt0-system-vram01: - shard-bmg: [PASS][133] -> [FAIL][134] ([Intel XE#3981]) [133]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-2450-dfcd517d1169ab05be63134ba5cbc7bfaf030eb1/shard-bmg-5/igt@xe_ccs@suspend-resume@xmajor-compressed-compfmt0-system-vram01.html [134]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-143203v1/shard-bmg-3/igt@xe_ccs@suspend-resume@xmajor-compressed-compfmt0-system-vram01.html * igt@xe_compute@ccs-mode-basic: - shard-lnl: NOTRUN -> [SKIP][135] ([Intel XE#1447]) [135]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-143203v1/shard-lnl-3/igt@xe_compute@ccs-mode-basic.html * igt@xe_compute_preempt@compute-threadgroup-preempt@engine-drm_xe_engine_class_compute: - shard-dg2-set2: NOTRUN -> [SKIP][136] ([Intel XE#1280] / [Intel XE#455]) [136]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-143203v1/shard-dg2-434/igt@xe_compute_preempt@compute-threadgroup-preempt@engine-drm_xe_engine_class_compute.html * igt@xe_copy_basic@mem-copy-linear-0xfd: - shard-adlp: NOTRUN -> [SKIP][137] ([Intel XE#1123]) [137]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-143203v1/shard-adlp-4/igt@xe_copy_basic@mem-copy-linear-0xfd.html * igt@xe_eudebug@discovery-empty: - shard-bmg: NOTRUN -> [SKIP][138] ([Intel XE#2905]) +2 other tests skip [138]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-143203v1/shard-bmg-5/igt@xe_eudebug@discovery-empty.html * igt@xe_eudebug@multiple-sessions: - shard-adlp: NOTRUN -> [SKIP][139] ([Intel XE#2905]) [139]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-143203v1/shard-adlp-4/igt@xe_eudebug@multiple-sessions.html * igt@xe_eudebug_online@reset-with-attention: - shard-lnl: NOTRUN -> [SKIP][140] ([Intel XE#2905]) +4 other tests skip [140]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-143203v1/shard-lnl-3/igt@xe_eudebug_online@reset-with-attention.html * igt@xe_eudebug_online@resume-dss: - shard-dg2-set2: NOTRUN -> [SKIP][141] ([Intel XE#2905]) +3 other tests skip [141]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-143203v1/shard-dg2-434/igt@xe_eudebug_online@resume-dss.html * igt@xe_evict@evict-beng-large-multi-vm-cm: - shard-adlp: NOTRUN -> [SKIP][142] ([Intel XE#261] / [Intel XE#688]) [142]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-143203v1/shard-adlp-4/igt@xe_evict@evict-beng-large-multi-vm-cm.html * igt@xe_evict@evict-mixed-many-threads-small: - shard-lnl: NOTRUN -> [SKIP][143] ([Intel XE#688]) +2 other tests skip [143]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-143203v1/shard-lnl-3/igt@xe_evict@evict-mixed-many-threads-small.html * igt@xe_evict@evict-mixed-threads-large: - shard-bmg: NOTRUN -> [TIMEOUT][144] ([Intel XE#1473] / [Intel XE#2472]) [144]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-143203v1/shard-bmg-3/igt@xe_evict@evict-mixed-threads-large.html * igt@xe_evict_ccs@evict-overcommit-parallel-instantfree-samefd: - shard-adlp: NOTRUN -> [SKIP][145] ([Intel XE#688]) [145]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-143203v1/shard-adlp-4/igt@xe_evict_ccs@evict-overcommit-parallel-instantfree-samefd.html * igt@xe_exec_balancer@twice-virtual-basic: - shard-dg2-set2: [PASS][146] -> [SKIP][147] ([Intel XE#1130]) +66 other tests skip [146]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-2450-dfcd517d1169ab05be63134ba5cbc7bfaf030eb1/shard-dg2-434/igt@xe_exec_balancer@twice-virtual-basic.html [147]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-143203v1/shard-dg2-466/igt@xe_exec_balancer@twice-virtual-basic.html * igt@xe_exec_basic@multigpu-many-execqueues-many-vm-bindexecqueue-userptr: - shard-bmg: NOTRUN -> [SKIP][148] ([Intel XE#2322]) +3 other tests skip [148]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-143203v1/shard-bmg-3/igt@xe_exec_basic@multigpu-many-execqueues-many-vm-bindexecqueue-userptr.html * igt@xe_exec_basic@multigpu-many-execqueues-many-vm-userptr-rebind: - shard-adlp: NOTRUN -> [SKIP][149] ([Intel XE#1392]) [149]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-143203v1/shard-adlp-4/igt@xe_exec_basic@multigpu-many-execqueues-many-vm-userptr-rebind.html * igt@xe_exec_basic@multigpu-no-exec-userptr-invalidate: - shard-lnl: NOTRUN -> [SKIP][150] ([Intel XE#1392]) +2 other tests skip [150]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-143203v1/shard-lnl-5/igt@xe_exec_basic@multigpu-no-exec-userptr-invalidate.html * igt@xe_exec_fault_mode@many-bindexecqueue-userptr-rebind-imm: - shard-dg2-set2: NOTRUN -> [SKIP][151] ([Intel XE#1130]) +15 other tests skip [151]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-143203v1/shard-dg2-466/igt@xe_exec_fault_mode@many-bindexecqueue-userptr-rebind-imm.html * igt@xe_exec_fault_mode@many-execqueues-userptr-rebind-prefetch: - shard-adlp: NOTRUN -> [SKIP][152] ([Intel XE#288]) +4 other tests skip [152]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-143203v1/shard-adlp-4/igt@xe_exec_fault_mode@many-execqueues-userptr-rebind-prefetch.html * igt@xe_exec_fault_mode@twice-bindexecqueue-userptr-rebind-prefetch: - shard-dg2-set2: NOTRUN -> [SKIP][153] ([Intel XE#288]) +7 other tests skip [153]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-143203v1/shard-dg2-434/igt@xe_exec_fault_mode@twice-bindexecqueue-userptr-rebind-prefetch.html * igt@xe_mmap@vram: - shard-lnl: NOTRUN -> [SKIP][154] ([Intel XE#1416]) [154]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-143203v1/shard-lnl-5/igt@xe_mmap@vram.html * igt@xe_oa@oa-tlb-invalidate: - shard-dg2-set2: NOTRUN -> [SKIP][155] ([Intel XE#2541] / [Intel XE#3573]) +2 other tests skip [155]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-143203v1/shard-dg2-436/igt@xe_oa@oa-tlb-invalidate.html * igt@xe_oa@syncs-syncobj-none: - shard-adlp: NOTRUN -> [SKIP][156] ([Intel XE#2541] / [Intel XE#3573]) +2 other tests skip [156]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-143203v1/shard-adlp-4/igt@xe_oa@syncs-syncobj-none.html * igt@xe_pat@pat-index-xelp: - shard-bmg: NOTRUN -> [SKIP][157] ([Intel XE#2245]) [157]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-143203v1/shard-bmg-5/igt@xe_pat@pat-index-xelp.html * igt@xe_peer2peer@write@write-gpua-vram01-gpub-system-p2p: - shard-dg2-set2: NOTRUN -> [FAIL][158] ([Intel XE#1173]) +1 other test fail [158]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-143203v1/shard-dg2-434/igt@xe_peer2peer@write@write-gpua-vram01-gpub-system-p2p.html * igt@xe_pm@d3cold-basic: - shard-bmg: NOTRUN -> [SKIP][159] ([Intel XE#2284]) [159]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-143203v1/shard-bmg-3/igt@xe_pm@d3cold-basic.html * igt@xe_pm@d3cold-basic-exec: - shard-lnl: NOTRUN -> [SKIP][160] ([Intel XE#2284] / [Intel XE#366]) [160]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-143203v1/shard-lnl-5/igt@xe_pm@d3cold-basic-exec.html * igt@xe_pm@s3-d3cold-basic-exec: - shard-dg2-set2: NOTRUN -> [SKIP][161] ([Intel XE#2284] / [Intel XE#366]) [161]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-143203v1/shard-dg2-436/igt@xe_pm@s3-d3cold-basic-exec.html * igt@xe_pm@s3-vm-bind-unbind-all: - shard-lnl: NOTRUN -> [SKIP][162] ([Intel XE#584]) [162]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-143203v1/shard-lnl-3/igt@xe_pm@s3-vm-bind-unbind-all.html * igt@xe_pm_residency@toggle-gt-c6: - shard-adlp: [PASS][163] -> [FAIL][164] ([Intel XE#958]) [163]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-2450-dfcd517d1169ab05be63134ba5cbc7bfaf030eb1/shard-adlp-6/igt@xe_pm_residency@toggle-gt-c6.html [164]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-143203v1/shard-adlp-1/igt@xe_pm_residency@toggle-gt-c6.html * igt@xe_query@multigpu-query-cs-cycles: - shard-dg2-set2: NOTRUN -> [SKIP][165] ([Intel XE#944]) +1 other test skip [165]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-143203v1/shard-dg2-434/igt@xe_query@multigpu-query-cs-cycles.html * igt@xe_query@multigpu-query-oa-units: - shard-adlp: NOTRUN -> [SKIP][166] ([Intel XE#944]) [166]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-143203v1/shard-adlp-4/igt@xe_query@multigpu-query-oa-units.html * igt@xe_query@multigpu-query-uc-fw-version-guc: - shard-lnl: NOTRUN -> [SKIP][167] ([Intel XE#944]) [167]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-143203v1/shard-lnl-3/igt@xe_query@multigpu-query-uc-fw-version-guc.html * igt@xe_query@multigpu-query-uc-fw-version-huc: - shard-bmg: NOTRUN -> [SKIP][168] ([Intel XE#944]) +1 other test skip [168]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-143203v1/shard-bmg-3/igt@xe_query@multigpu-query-uc-fw-version-huc.html * igt@xe_sriov_flr@flr-each-isolation: - shard-lnl: NOTRUN -> [SKIP][169] ([Intel XE#3342]) [169]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-143203v1/shard-lnl-3/igt@xe_sriov_flr@flr-each-isolation.html #### Possible fixes #### * igt@core_hotunplug@hotunbind-rebind: - shard-dg2-set2: [SKIP][170] ([Intel XE#1885]) -> [PASS][171] [170]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-2450-dfcd517d1169ab05be63134ba5cbc7bfaf030eb1/shard-dg2-466/igt@core_hotunplug@hotunbind-rebind.html [171]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-143203v1/shard-dg2-435/igt@core_hotunplug@hotunbind-rebind.html * igt@core_setmaster@master-drop-set-root: - shard-dg2-set2: [FAIL][172] ([Intel XE#3249]) -> [PASS][173] [172]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-2450-dfcd517d1169ab05be63134ba5cbc7bfaf030eb1/shard-dg2-466/igt@core_setmaster@master-drop-set-root.html [173]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-143203v1/shard-dg2-434/igt@core_setmaster@master-drop-set-root.html * igt@fbdev@write: - shard-dg2-set2: [SKIP][174] ([Intel XE#2134]) -> [PASS][175] [174]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-2450-dfcd517d1169ab05be63134ba5cbc7bfaf030eb1/shard-dg2-466/igt@fbdev@write.html [175]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-143203v1/shard-dg2-434/igt@fbdev@write.html * igt@kms_3d: - shard-dg2-set2: [SKIP][176] ([Intel XE#2423]) -> [PASS][177] +1 other test pass [176]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-2450-dfcd517d1169ab05be63134ba5cbc7bfaf030eb1/shard-dg2-466/igt@kms_3d.html [177]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-143203v1/shard-dg2-435/igt@kms_3d.html * igt@kms_async_flips@alternate-sync-async-flip: - shard-bmg: [FAIL][178] ([Intel XE#827]) -> [PASS][179] +1 other test pass [178]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-2450-dfcd517d1169ab05be63134ba5cbc7bfaf030eb1/shard-bmg-5/igt@kms_async_flips@alternate-sync-async-flip.html [179]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-143203v1/shard-bmg-3/igt@kms_async_flips@alternate-sync-async-flip.html * igt@kms_big_fb@y-tiled-max-hw-stride-64bpp-rotate-0-hflip-async-flip: - shard-adlp: [DMESG-WARN][180] ([Intel XE#1033]) -> [PASS][181] +2 other tests pass [180]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-2450-dfcd517d1169ab05be63134ba5cbc7bfaf030eb1/shard-adlp-1/igt@kms_big_fb@y-tiled-max-hw-stride-64bpp-rotate-0-hflip-async-flip.html [181]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-143203v1/shard-adlp-9/igt@kms_big_fb@y-tiled-max-hw-stride-64bpp-rotate-0-hflip-async-flip.html * igt@kms_ccs@random-ccs-data-4-tiled-dg2-rc-ccs-cc: - shard-dg2-set2: [INCOMPLETE][182] ([Intel XE#2692]) -> [PASS][183] +1 other test pass [182]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-2450-dfcd517d1169ab05be63134ba5cbc7bfaf030eb1/shard-dg2-436/igt@kms_ccs@random-ccs-data-4-tiled-dg2-rc-ccs-cc.html [183]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-143203v1/shard-dg2-436/igt@kms_ccs@random-ccs-data-4-tiled-dg2-rc-ccs-cc.html * igt@kms_cursor_crc@cursor-suspend: - shard-bmg: [FAIL][184] ([Intel XE#3999]) -> [PASS][185] +1 other test pass [184]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-2450-dfcd517d1169ab05be63134ba5cbc7bfaf030eb1/shard-bmg-3/igt@kms_cursor_crc@cursor-suspend.html [185]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-143203v1/shard-bmg-3/igt@kms_cursor_crc@cursor-suspend.html * igt@kms_cursor_crc@cursor-suspend@pipe-a-dp-2: - shard-bmg: [FAIL][186] -> [PASS][187] +1 other test pass [186]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-2450-dfcd517d1169ab05be63134ba5cbc7bfaf030eb1/shard-bmg-3/igt@kms_cursor_crc@cursor-suspend@pipe-a-dp-2.html [187]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-143203v1/shard-bmg-3/igt@kms_cursor_crc@cursor-suspend@pipe-a-dp-2.html * igt@kms_flip@busy-flip: - shard-dg2-set2: [SKIP][188] ([Intel XE#2423] / [i915#2575]) -> [PASS][189] +81 other tests pass [188]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-2450-dfcd517d1169ab05be63134ba5cbc7bfaf030eb1/shard-dg2-466/igt@kms_flip@busy-flip.html [189]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-143203v1/shard-dg2-436/igt@kms_flip@busy-flip.html * igt@kms_flip@flip-vs-expired-vblank-interruptible@a-dp4: - shard-dg2-set2: [FAIL][190] ([Intel XE#301]) -> [PASS][191] [190]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-2450-dfcd517d1169ab05be63134ba5cbc7bfaf030eb1/shard-dg2-435/igt@kms_flip@flip-vs-expired-vblank-interruptible@a-dp4.html [191]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-143203v1/shard-dg2-434/igt@kms_flip@flip-vs-expired-vblank-interruptible@a-dp4.html * igt@kms_flip@flip-vs-expired-vblank@c-dp2: - shard-bmg: [FAIL][192] ([Intel XE#2882]) -> [PASS][193] [192]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-2450-dfcd517d1169ab05be63134ba5cbc7bfaf030eb1/shard-bmg-5/igt@kms_flip@flip-vs-expired-vblank@c-dp2.html [193]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-143203v1/shard-bmg-3/igt@kms_flip@flip-vs-expired-vblank@c-dp2.html * igt@kms_frontbuffer_tracking@fbc-2p-primscrn-cur-indfb-move: - shard-dg2-set2: [SKIP][194] ([Intel XE#2136] / [Intel XE#2351]) -> [PASS][195] +6 other tests pass [194]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-2450-dfcd517d1169ab05be63134ba5cbc7bfaf030eb1/shard-dg2-466/igt@kms_frontbuffer_tracking@fbc-2p-primscrn-cur-indfb-move.html [195]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-143203v1/shard-dg2-436/igt@kms_frontbuffer_tracking@fbc-2p-primscrn-cur-indfb-move.html * igt@kms_joiner@basic-force-big-joiner: - shard-dg2-set2: [SKIP][196] ([Intel XE#2136]) -> [PASS][197] +25 other tests pass [196]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-2450-dfcd517d1169ab05be63134ba5cbc7bfaf030eb1/shard-dg2-466/igt@kms_joiner@basic-force-big-joiner.html [197]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-143203v1/shard-dg2-434/igt@kms_joiner@basic-force-big-joiner.html * igt@kms_pm_rpm@modeset-non-lpsp: - shard-dg2-set2: [SKIP][198] ([Intel XE#2446]) -> [PASS][199] +1 other test pass [198]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-2450-dfcd517d1169ab05be63134ba5cbc7bfaf030eb1/shard-dg2-466/igt@kms_pm_rpm@modeset-non-lpsp.html [199]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-143203v1/shard-dg2-434/igt@kms_pm_rpm@modeset-non-lpsp.html * igt@kms_vblank@ts-continuation-dpms-suspend: - shard-adlp: [DMESG-WARN][200] ([Intel XE#2953]) -> [PASS][201] +3 other tests pass [200]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-2450-dfcd517d1169ab05be63134ba5cbc7bfaf030eb1/shard-adlp-9/igt@kms_vblank@ts-continuation-dpms-suspend.html [201]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-143203v1/shard-adlp-2/igt@kms_vblank@ts-continuation-dpms-suspend.html * igt@xe_ccs@suspend-resume@xmajor-compressed-compfmt0-vram01-vram01: - shard-bmg: [INCOMPLETE][202] ([Intel XE#3918]) -> [PASS][203] [202]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-2450-dfcd517d1169ab05be63134ba5cbc7bfaf030eb1/shard-bmg-5/igt@xe_ccs@suspend-resume@xmajor-compressed-compfmt0-vram01-vram01.html [203]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-143203v1/shard-bmg-3/igt@xe_ccs@suspend-resume@xmajor-compressed-compfmt0-vram01-vram01.html * igt@xe_evict@evict-beng-mixed-many-threads-small: - shard-bmg: [TIMEOUT][204] ([Intel XE#1473]) -> [PASS][205] [204]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-2450-dfcd517d1169ab05be63134ba5cbc7bfaf030eb1/shard-bmg-3/igt@xe_evict@evict-beng-mixed-many-threads-small.html [205]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-143203v1/shard-bmg-7/igt@xe_evict@evict-beng-mixed-many-threads-small.html * igt@xe_evict@evict-mixed-many-threads-large: - shard-dg2-set2: [TIMEOUT][206] ([Intel XE#1473]) -> [PASS][207] [206]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-2450-dfcd517d1169ab05be63134ba5cbc7bfaf030eb1/shard-dg2-434/igt@xe_evict@evict-mixed-many-threads-large.html [207]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-143203v1/shard-dg2-435/igt@xe_evict@evict-mixed-many-threads-large.html * igt@xe_exec_threads@threads-hang-rebind-err: - shard-dg2-set2: [DMESG-WARN][208] ([Intel XE#3876]) -> [PASS][209] [208]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-2450-dfcd517d1169ab05be63134ba5cbc7bfaf030eb1/shard-dg2-434/igt@xe_exec_threads@threads-hang-rebind-err.html [209]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-143203v1/shard-dg2-435/igt@xe_exec_threads@threads-hang-rebind-err.html * igt@xe_module_load@reload-no-display: - shard-dg2-set2: [FAIL][210] ([Intel XE#3546]) -> [PASS][211] [210]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-2450-dfcd517d1169ab05be63134ba5cbc7bfaf030eb1/shard-dg2-466/igt@xe_module_load@reload-no-display.html [211]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-143203v1/shard-dg2-435/igt@xe_module_load@reload-no-display.html * igt@xe_pm@s4-basic-exec: - shard-adlp: [ABORT][212] ([Intel XE#1358] / [Intel XE#1607] / [Intel XE#1794]) -> [PASS][213] [212]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-2450-dfcd517d1169ab05be63134ba5cbc7bfaf030eb1/shard-adlp-9/igt@xe_pm@s4-basic-exec.html [213]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-143203v1/shard-adlp-4/igt@xe_pm@s4-basic-exec.html * igt@xe_pm@s4-vm-bind-prefetch: - shard-lnl: [ABORT][214] ([Intel XE#1358] / [Intel XE#1607] / [Intel XE#1794]) -> [PASS][215] [214]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-2450-dfcd517d1169ab05be63134ba5cbc7bfaf030eb1/shard-lnl-2/igt@xe_pm@s4-vm-bind-prefetch.html [215]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-143203v1/shard-lnl-5/igt@xe_pm@s4-vm-bind-prefetch.html * igt@xe_pm_residency@toggle-gt-c6: - shard-lnl: [FAIL][216] ([Intel XE#958]) -> [PASS][217] [216]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-2450-dfcd517d1169ab05be63134ba5cbc7bfaf030eb1/shard-lnl-3/igt@xe_pm_residency@toggle-gt-c6.html [217]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-143203v1/shard-lnl-6/igt@xe_pm_residency@toggle-gt-c6.html * igt@xe_vm@mmap-style-bind-userptr-one-partial: - shard-dg2-set2: [SKIP][218] ([Intel XE#1130]) -> [PASS][219] +149 other tests pass [218]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-2450-dfcd517d1169ab05be63134ba5cbc7bfaf030eb1/shard-dg2-466/igt@xe_vm@mmap-style-bind-userptr-one-partial.html [219]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-143203v1/shard-dg2-435/igt@xe_vm@mmap-style-bind-userptr-one-partial.html #### Warnings #### * igt@kms_async_flips@async-flip-with-page-flip-events: - shard-adlp: [DMESG-WARN][220] ([Intel XE#1033] / [Intel XE#2953]) -> [DMESG-WARN][221] ([Intel XE#1033]) [220]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-2450-dfcd517d1169ab05be63134ba5cbc7bfaf030eb1/shard-adlp-2/igt@kms_async_flips@async-flip-with-page-flip-events.html [221]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-143203v1/shard-adlp-9/igt@kms_async_flips@async-flip-with-page-flip-events.html * igt@kms_async_flips@crc-atomic@pipe-c-hdmi-a-1: - shard-adlp: [DMESG-FAIL][222] ([Intel XE#1033]) -> [FAIL][223] ([Intel XE#3884]) [222]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-2450-dfcd517d1169ab05be63134ba5cbc7bfaf030eb1/shard-adlp-3/igt@kms_async_flips@crc-atomic@pipe-c-hdmi-a-1.html [223]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-143203v1/shard-adlp-8/igt@kms_async_flips@crc-atomic@pipe-c-hdmi-a-1.html * igt@kms_async_flips@invalid-async-flip: - shard-dg2-set2: [SKIP][224] ([Intel XE#2423] / [i915#2575]) -> [SKIP][225] ([Intel XE#873]) [224]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-2450-dfcd517d1169ab05be63134ba5cbc7bfaf030eb1/shard-dg2-466/igt@kms_async_flips@invalid-async-flip.html [225]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-143203v1/shard-dg2-436/igt@kms_async_flips@invalid-async-flip.html * igt@kms_big_fb@4-tiled-16bpp-rotate-90: - shard-dg2-set2: [SKIP][226] ([Intel XE#316]) -> [SKIP][227] ([Intel XE#2136] / [Intel XE#2351]) [226]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-2450-dfcd517d1169ab05be63134ba5cbc7bfaf030eb1/shard-dg2-434/igt@kms_big_fb@4-tiled-16bpp-rotate-90.html [227]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-143203v1/shard-dg2-466/igt@kms_big_fb@4-tiled-16bpp-rotate-90.html * igt@kms_big_fb@4-tiled-64bpp-rotate-90: - shard-dg2-set2: [SKIP][228] ([Intel XE#316]) -> [SKIP][229] ([Intel XE#2136]) +1 other test skip [228]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-2450-dfcd517d1169ab05be63134ba5cbc7bfaf030eb1/shard-dg2-434/igt@kms_big_fb@4-tiled-64bpp-rotate-90.html [229]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-143203v1/shard-dg2-466/igt@kms_big_fb@4-tiled-64bpp-rotate-90.html * igt@kms_big_fb@x-tiled-32bpp-rotate-90: - shard-dg2-set2: [SKIP][230] ([Intel XE#2136]) -> [SKIP][231] ([Intel XE#316]) +2 other tests skip [230]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-2450-dfcd517d1169ab05be63134ba5cbc7bfaf030eb1/shard-dg2-466/igt@kms_big_fb@x-tiled-32bpp-rotate-90.html [231]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-143203v1/shard-dg2-436/igt@kms_big_fb@x-tiled-32bpp-rotate-90.html * igt@kms_big_fb@y-tiled-addfb-size-offset-overflow: - shard-dg2-set2: [SKIP][232] ([Intel XE#2136] / [Intel XE#2351]) -> [SKIP][233] ([Intel XE#607]) [232]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-2450-dfcd517d1169ab05be63134ba5cbc7bfaf030eb1/shard-dg2-466/igt@kms_big_fb@y-tiled-addfb-size-offset-overflow.html [233]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-143203v1/shard-dg2-435/igt@kms_big_fb@y-tiled-addfb-size-offset-overflow.html * igt@kms_big_fb@y-tiled-addfb-size-overflow: - shard-dg2-set2: [SKIP][234] ([Intel XE#2136]) -> [SKIP][235] ([Intel XE#610]) [234]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-2450-dfcd517d1169ab05be63134ba5cbc7bfaf030eb1/shard-dg2-466/igt@kms_big_fb@y-tiled-addfb-size-overflow.html [235]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-143203v1/shard-dg2-436/igt@kms_big_fb@y-tiled-addfb-size-overflow.html * igt@kms_big_fb@y-tiled-max-hw-stride-32bpp-rotate-0-hflip: - shard-dg2-set2: [SKIP][236] ([Intel XE#1124]) -> [SKIP][237] ([Intel XE#2136] / [Intel XE#2351]) +2 other tests skip [236]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-2450-dfcd517d1169ab05be63134ba5cbc7bfaf030eb1/shard-dg2-434/igt@kms_big_fb@y-tiled-max-hw-stride-32bpp-rotate-0-hflip.html [237]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-143203v1/shard-dg2-466/igt@kms_big_fb@y-tiled-max-hw-stride-32bpp-rotate-0-hflip.html * igt@kms_big_fb@y-tiled-max-hw-stride-32bpp-rotate-180-hflip: - shard-dg2-set2: [SKIP][238] ([Intel XE#1124]) -> [SKIP][239] ([Intel XE#2136]) +1 other test skip [238]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-2450-dfcd517d1169ab05be63134ba5cbc7bfaf030eb1/shard-dg2-434/igt@kms_big_fb@y-tiled-max-hw-stride-32bpp-rotate-180-hflip.html [239]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-143203v1/shard-dg2-466/igt@kms_big_fb@y-tiled-max-hw-stride-32bpp-rotate-180-hflip.html * igt@kms_big_fb@yf-tiled-32bpp-rotate-180: - shard-dg2-set2: [SKIP][240] ([Intel XE#2136]) -> [SKIP][241] ([Intel XE#1124]) +4 other tests skip [240]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-2450-dfcd517d1169ab05be63134ba5cbc7bfaf030eb1/shard-dg2-466/igt@kms_big_fb@yf-tiled-32bpp-rotate-180.html [241]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-143203v1/shard-dg2-436/igt@kms_big_fb@yf-tiled-32bpp-rotate-180.html * igt@kms_big_fb@yf-tiled-max-hw-stride-32bpp-rotate-180-hflip-async-flip: - shard-dg2-set2: [SKIP][242] ([Intel XE#2136] / [Intel XE#2351]) -> [SKIP][243] ([Intel XE#1124]) +2 other tests skip [242]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-2450-dfcd517d1169ab05be63134ba5cbc7bfaf030eb1/shard-dg2-466/igt@kms_big_fb@yf-tiled-max-hw-stride-32bpp-rotate-180-hflip-async-flip.html [243]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-143203v1/shard-dg2-435/igt@kms_big_fb@yf-tiled-max-hw-stride-32bpp-rotate-180-hflip-async-flip.html * igt@kms_bw@connected-linear-tiling-1-displays-2160x1440p: - shard-dg2-set2: [SKIP][244] ([Intel XE#2423] / [i915#2575]) -> [SKIP][245] ([Intel XE#367]) +5 other tests skip [244]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-2450-dfcd517d1169ab05be63134ba5cbc7bfaf030eb1/shard-dg2-466/igt@kms_bw@connected-linear-tiling-1-displays-2160x1440p.html [245]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-143203v1/shard-dg2-435/igt@kms_bw@connected-linear-tiling-1-displays-2160x1440p.html * igt@kms_bw@connected-linear-tiling-2-displays-3840x2160p: - shard-dg2-set2: [SKIP][246] ([Intel XE#367]) -> [SKIP][247] ([Intel XE#2423] / [i915#2575]) +3 other tests skip [246]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-2450-dfcd517d1169ab05be63134ba5cbc7bfaf030eb1/shard-dg2-434/igt@kms_bw@connected-linear-tiling-2-displays-3840x2160p.html [247]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-143203v1/shard-dg2-466/igt@kms_bw@connected-linear-tiling-2-displays-3840x2160p.html * igt@kms_ccs@bad-rotation-90-4-tiled-lnl-ccs: - shard-dg2-set2: [SKIP][248] ([Intel XE#2136]) -> [SKIP][249] ([Intel XE#2907]) +2 other tests skip [248]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-2450-dfcd517d1169ab05be63134ba5cbc7bfaf030eb1/shard-dg2-466/igt@kms_ccs@bad-rotation-90-4-tiled-lnl-ccs.html [249]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-143203v1/shard-dg2-434/igt@kms_ccs@bad-rotation-90-4-tiled-lnl-ccs.html * igt@kms_ccs@bad-rotation-90-y-tiled-gen12-rc-ccs: - shard-dg2-set2: [SKIP][250] ([Intel XE#455] / [Intel XE#787]) -> [SKIP][251] ([Intel XE#2136] / [Intel XE#2351]) [250]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-2450-dfcd517d1169ab05be63134ba5cbc7bfaf030eb1/shard-dg2-434/igt@kms_ccs@bad-rotation-90-y-tiled-gen12-rc-ccs.html [251]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-143203v1/shard-dg2-466/igt@kms_ccs@bad-rotation-90-y-tiled-gen12-rc-ccs.html * igt@kms_ccs@crc-primary-basic-y-tiled-gen12-rc-ccs: - shard-dg2-set2: [SKIP][252] ([Intel XE#455] / [Intel XE#787]) -> [SKIP][253] ([Intel XE#2136]) +2 other tests skip [252]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-2450-dfcd517d1169ab05be63134ba5cbc7bfaf030eb1/shard-dg2-434/igt@kms_ccs@crc-primary-basic-y-tiled-gen12-rc-ccs.html [253]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-143203v1/shard-dg2-466/igt@kms_ccs@crc-primary-basic-y-tiled-gen12-rc-ccs.html * igt@kms_ccs@crc-primary-rotation-180-4-tiled-mtl-rc-ccs-cc: - shard-dg2-set2: [SKIP][254] ([Intel XE#2136] / [Intel XE#2351]) -> [SKIP][255] ([Intel XE#455] / [Intel XE#787]) +2 other tests skip [254]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-2450-dfcd517d1169ab05be63134ba5cbc7bfaf030eb1/shard-dg2-466/igt@kms_ccs@crc-primary-rotation-180-4-tiled-mtl-rc-ccs-cc.html [255]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-143203v1/shard-dg2-434/igt@kms_ccs@crc-primary-rotation-180-4-tiled-mtl-rc-ccs-cc.html * igt@kms_ccs@crc-primary-suspend-y-tiled-gen12-rc-ccs: - shard-dg2-set2: [SKIP][256] ([Intel XE#2136]) -> [SKIP][257] ([Intel XE#455] / [Intel XE#787]) +9 other tests skip [256]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-2450-dfcd517d1169ab05be63134ba5cbc7bfaf030eb1/shard-dg2-466/igt@kms_ccs@crc-primary-suspend-y-tiled-gen12-rc-ccs.html [257]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-143203v1/shard-dg2-435/igt@kms_ccs@crc-primary-suspend-y-tiled-gen12-rc-ccs.html * igt@kms_ccs@random-ccs-data-4-tiled-dg2-rc-ccs: - shard-dg2-set2: [INCOMPLETE][258] ([Intel XE#1727] / [Intel XE#3124]) -> [SKIP][259] ([Intel XE#2136]) [258]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-2450-dfcd517d1169ab05be63134ba5cbc7bfaf030eb1/shard-dg2-434/igt@kms_ccs@random-ccs-data-4-tiled-dg2-rc-ccs.html [259]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-143203v1/shard-dg2-466/igt@kms_ccs@random-ccs-data-4-tiled-dg2-rc-ccs.html * igt@kms_chamelium_color@ctm-0-75: - shard-dg2-set2: [SKIP][260] ([Intel XE#2423] / [i915#2575]) -> [SKIP][261] ([Intel XE#306]) +2 other tests skip [260]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-2450-dfcd517d1169ab05be63134ba5cbc7bfaf030eb1/shard-dg2-466/igt@kms_chamelium_color@ctm-0-75.html [261]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-143203v1/shard-dg2-435/igt@kms_chamelium_color@ctm-0-75.html * igt@kms_chamelium_color@degamma: - shard-dg2-set2: [SKIP][262] ([Intel XE#306]) -> [SKIP][263] ([Intel XE#2423] / [i915#2575]) [262]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-2450-dfcd517d1169ab05be63134ba5cbc7bfaf030eb1/shard-dg2-434/igt@kms_chamelium_color@degamma.html [263]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-143203v1/shard-dg2-466/igt@kms_chamelium_color@degamma.html * igt@kms_chamelium_hpd@hdmi-hpd: - shard-dg2-set2: [SKIP][264] ([Intel XE#2423] / [i915#2575]) -> [SKIP][265] ([Intel XE#373]) +9 other tests skip [264]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-2450-dfcd517d1169ab05be63134ba5cbc7bfaf030eb1/shard-dg2-466/igt@kms_chamelium_hpd@hdmi-hpd.html [265]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-143203v1/shard-dg2-434/igt@kms_chamelium_hpd@hdmi-hpd.html * igt@kms_chamelium_hpd@hdmi-hpd-storm: - shard-dg2-set2: [SKIP][266] ([Intel XE#373]) -> [SKIP][267] ([Intel XE#2423] / [i915#2575]) +4 other tests skip [266]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-2450-dfcd517d1169ab05be63134ba5cbc7bfaf030eb1/shard-dg2-434/igt@kms_chamelium_hpd@hdmi-hpd-storm.html [267]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-143203v1/shard-dg2-466/igt@kms_chamelium_hpd@hdmi-hpd-storm.html * igt@kms_content_protection@dp-mst-lic-type-0: - shard-dg2-set2: [SKIP][268] ([Intel XE#2423] / [i915#2575]) -> [SKIP][269] ([Intel XE#307]) [268]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-2450-dfcd517d1169ab05be63134ba5cbc7bfaf030eb1/shard-dg2-466/igt@kms_content_protection@dp-mst-lic-type-0.html [269]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-143203v1/shard-dg2-434/igt@kms_content_protection@dp-mst-lic-type-0.html * igt@kms_content_protection@lic-type-0: - shard-dg2-set2: [FAIL][270] ([Intel XE#1178]) -> [SKIP][271] ([Intel XE#2423] / [i915#2575]) [270]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-2450-dfcd517d1169ab05be63134ba5cbc7bfaf030eb1/shard-dg2-434/igt@kms_content_protection@lic-type-0.html [271]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-143203v1/shard-dg2-466/igt@kms_content_protection@lic-type-0.html * igt@kms_cursor_crc@cursor-random-512x170: - shard-dg2-set2: [SKIP][272] ([Intel XE#308]) -> [SKIP][273] ([Intel XE#2423] / [i915#2575]) [272]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-2450-dfcd517d1169ab05be63134ba5cbc7bfaf030eb1/shard-dg2-434/igt@kms_cursor_crc@cursor-random-512x170.html [273]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-143203v1/shard-dg2-466/igt@kms_cursor_crc@cursor-random-512x170.html * igt@kms_cursor_crc@cursor-random-max-size: - shard-dg2-set2: [SKIP][274] ([Intel XE#2423] / [i915#2575]) -> [SKIP][275] ([Intel XE#455]) +7 other tests skip [274]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-2450-dfcd517d1169ab05be63134ba5cbc7bfaf030eb1/shard-dg2-466/igt@kms_cursor_crc@cursor-random-max-size.html [275]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-143203v1/shard-dg2-435/igt@kms_cursor_crc@cursor-random-max-size.html * igt@kms_cursor_crc@cursor-rapid-movement-512x170: - shard-dg2-set2: [SKIP][276] ([Intel XE#2423] / [i915#2575]) -> [SKIP][277] ([Intel XE#308]) +1 other test skip [276]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-2450-dfcd517d1169ab05be63134ba5cbc7bfaf030eb1/shard-dg2-466/igt@kms_cursor_crc@cursor-rapid-movement-512x170.html [277]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-143203v1/shard-dg2-434/igt@kms_cursor_crc@cursor-rapid-movement-512x170.html * igt@kms_cursor_legacy@short-busy-flip-before-cursor-atomic-transitions: - shard-dg2-set2: [SKIP][278] ([Intel XE#2423] / [i915#2575]) -> [SKIP][279] ([Intel XE#323]) [278]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-2450-dfcd517d1169ab05be63134ba5cbc7bfaf030eb1/shard-dg2-466/igt@kms_cursor_legacy@short-busy-flip-before-cursor-atomic-transitions.html [279]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-143203v1/shard-dg2-436/igt@kms_cursor_legacy@short-busy-flip-before-cursor-atomic-transitions.html * igt@kms_dsc@dsc-basic: - shard-dg2-set2: [SKIP][280] ([Intel XE#2351]) -> [SKIP][281] ([Intel XE#455]) [280]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-2450-dfcd517d1169ab05be63134ba5cbc7bfaf030eb1/shard-dg2-466/igt@kms_dsc@dsc-basic.html [281]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-143203v1/shard-dg2-435/igt@kms_dsc@dsc-basic.html * igt@kms_dsc@dsc-with-bpc: - shard-dg2-set2: [SKIP][282] ([Intel XE#455]) -> [SKIP][283] ([Intel XE#2136]) +2 other tests skip [282]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-2450-dfcd517d1169ab05be63134ba5cbc7bfaf030eb1/shard-dg2-434/igt@kms_dsc@dsc-with-bpc.html [283]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-143203v1/shard-dg2-466/igt@kms_dsc@dsc-with-bpc.html * igt@kms_feature_discovery@display-4x: - shard-dg2-set2: [SKIP][284] ([Intel XE#2423] / [i915#2575]) -> [SKIP][285] ([Intel XE#1138]) [284]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-2450-dfcd517d1169ab05be63134ba5cbc7bfaf030eb1/shard-dg2-466/igt@kms_feature_discovery@display-4x.html [285]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-143203v1/shard-dg2-436/igt@kms_feature_discovery@display-4x.html * igt@kms_flip@2x-flip-vs-suspend-interruptible@ac-dp2-hdmi-a3: - shard-bmg: [FAIL][286] ([Intel XE#3879]) -> [INCOMPLETE][287] ([Intel XE#2597]) [286]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-2450-dfcd517d1169ab05be63134ba5cbc7bfaf030eb1/shard-bmg-3/igt@kms_flip@2x-flip-vs-suspend-interruptible@ac-dp2-hdmi-a3.html [287]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-143203v1/shard-bmg-5/igt@kms_flip@2x-flip-vs-suspend-interruptible@ac-dp2-hdmi-a3.html * igt@kms_flip_scaled_crc@flip-32bpp-yftile-to-64bpp-yftile-downscaling: - shard-dg2-set2: [SKIP][288] ([Intel XE#2136]) -> [SKIP][289] ([Intel XE#455]) +3 other tests skip [288]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-2450-dfcd517d1169ab05be63134ba5cbc7bfaf030eb1/shard-dg2-466/igt@kms_flip_scaled_crc@flip-32bpp-yftile-to-64bpp-yftile-downscaling.html [289]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-143203v1/shard-dg2-434/igt@kms_flip_scaled_crc@flip-32bpp-yftile-to-64bpp-yftile-downscaling.html * igt@kms_flip_scaled_crc@flip-32bpp-ytile-to-32bpp-ytilegen12rcccs-upscaling: - shard-dg2-set2: [SKIP][290] ([Intel XE#455]) -> [SKIP][291] ([Intel XE#2136] / [Intel XE#2351]) [290]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-2450-dfcd517d1169ab05be63134ba5cbc7bfaf030eb1/shard-dg2-434/igt@kms_flip_scaled_crc@flip-32bpp-ytile-to-32bpp-ytilegen12rcccs-upscaling.html [291]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-143203v1/shard-dg2-466/igt@kms_flip_scaled_crc@flip-32bpp-ytile-to-32bpp-ytilegen12rcccs-upscaling.html * igt@kms_flip_scaled_crc@flip-64bpp-ytile-to-32bpp-ytile-downscaling: - shard-dg2-set2: [SKIP][292] ([Intel XE#2136] / [Intel XE#2351]) -> [SKIP][293] ([Intel XE#455]) +1 other test skip [292]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-2450-dfcd517d1169ab05be63134ba5cbc7bfaf030eb1/shard-dg2-466/igt@kms_flip_scaled_crc@flip-64bpp-ytile-to-32bpp-ytile-downscaling.html [293]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-143203v1/shard-dg2-435/igt@kms_flip_scaled_crc@flip-64bpp-ytile-to-32bpp-ytile-downscaling.html * igt@kms_force_connector_basic@prune-stale-modes: - shard-dg2-set2: [SKIP][294] ([i915#5274]) -> [SKIP][295] ([Intel XE#2423] / [i915#2575]) [294]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-2450-dfcd517d1169ab05be63134ba5cbc7bfaf030eb1/shard-dg2-434/igt@kms_force_connector_basic@prune-stale-modes.html [295]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-143203v1/shard-dg2-466/igt@kms_force_connector_basic@prune-stale-modes.html * igt@kms_frontbuffer_tracking@drrs-suspend: - shard-dg2-set2: [SKIP][296] ([Intel XE#2136] / [Intel XE#2351]) -> [SKIP][297] ([Intel XE#651]) +9 other tests skip [296]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-2450-dfcd517d1169ab05be63134ba5cbc7bfaf030eb1/shard-dg2-466/igt@kms_frontbuffer_tracking@drrs-suspend.html [297]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-143203v1/shard-dg2-434/igt@kms_frontbuffer_tracking@drrs-suspend.html * igt@kms_frontbuffer_tracking@fbcdrrs-1p-primscrn-cur-indfb-draw-render: - shard-dg2-set2: [SKIP][298] ([Intel XE#2136]) -> [SKIP][299] ([Intel XE#651]) +19 other tests skip [298]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-2450-dfcd517d1169ab05be63134ba5cbc7bfaf030eb1/shard-dg2-466/igt@kms_frontbuffer_tracking@fbcdrrs-1p-primscrn-cur-indfb-draw-render.html [299]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-143203v1/shard-dg2-435/igt@kms_frontbuffer_tracking@fbcdrrs-1p-primscrn-cur-indfb-draw-render.html * igt@kms_frontbuffer_tracking@fbcdrrs-2p-primscrn-pri-shrfb-draw-blt: - shard-dg2-set2: [SKIP][300] ([Intel XE#651]) -> [SKIP][301] ([Intel XE#2136] / [Intel XE#2351]) +3 other tests skip [300]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-2450-dfcd517d1169ab05be63134ba5cbc7bfaf030eb1/shard-dg2-434/igt@kms_frontbuffer_tracking@fbcdrrs-2p-primscrn-pri-shrfb-draw-blt.html [301]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-143203v1/shard-dg2-466/igt@kms_frontbuffer_tracking@fbcdrrs-2p-primscrn-pri-shrfb-draw-blt.html * igt@kms_frontbuffer_tracking@fbcdrrs-2p-scndscrn-spr-indfb-onoff: - shard-dg2-set2: [SKIP][302] ([Intel XE#651]) -> [SKIP][303] ([Intel XE#2136]) +8 other tests skip [302]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-2450-dfcd517d1169ab05be63134ba5cbc7bfaf030eb1/shard-dg2-434/igt@kms_frontbuffer_tracking@fbcdrrs-2p-scndscrn-spr-indfb-onoff.html [303]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-143203v1/shard-dg2-466/igt@kms_frontbuffer_tracking@fbcdrrs-2p-scndscrn-spr-indfb-onoff.html * igt@kms_frontbuffer_tracking@fbcdrrs-tiling-y: - shard-dg2-set2: [SKIP][304] ([Intel XE#2136] / [Intel XE#2351]) -> [SKIP][305] ([Intel XE#658]) [304]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-2450-dfcd517d1169ab05be63134ba5cbc7bfaf030eb1/shard-dg2-466/igt@kms_frontbuffer_tracking@fbcdrrs-tiling-y.html [305]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-143203v1/shard-dg2-435/igt@kms_frontbuffer_tracking@fbcdrrs-tiling-y.html * igt@kms_frontbuffer_tracking@fbcpsr-1p-primscrn-indfb-msflip-blt: - shard-dg2-set2: [SKIP][306] ([Intel XE#653]) -> [SKIP][307] ([Intel XE#2136]) +8 other tests skip [306]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-2450-dfcd517d1169ab05be63134ba5cbc7bfaf030eb1/shard-dg2-434/igt@kms_frontbuffer_tracking@fbcpsr-1p-primscrn-indfb-msflip-blt.html [307]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-143203v1/shard-dg2-466/igt@kms_frontbuffer_tracking@fbcpsr-1p-primscrn-indfb-msflip-blt.html * igt@kms_frontbuffer_tracking@fbcpsr-1p-primscrn-spr-indfb-draw-blt: - shard-dg2-set2: [SKIP][308] ([Intel XE#2136]) -> [SKIP][309] ([Intel XE#653]) +23 other tests skip [308]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-2450-dfcd517d1169ab05be63134ba5cbc7bfaf030eb1/shard-dg2-466/igt@kms_frontbuffer_tracking@fbcpsr-1p-primscrn-spr-indfb-draw-blt.html [309]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-143203v1/shard-dg2-436/igt@kms_frontbuffer_tracking@fbcpsr-1p-primscrn-spr-indfb-draw-blt.html * igt@kms_frontbuffer_tracking@fbcpsr-tiling-y: - shard-dg2-set2: [SKIP][310] ([Intel XE#658]) -> [SKIP][311] ([Intel XE#2136] / [Intel XE#2351]) [310]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-2450-dfcd517d1169ab05be63134ba5cbc7bfaf030eb1/shard-dg2-434/igt@kms_frontbuffer_tracking@fbcpsr-tiling-y.html [311]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-143203v1/shard-dg2-466/igt@kms_frontbuffer_tracking@fbcpsr-tiling-y.html * igt@kms_frontbuffer_tracking@plane-fbc-rte: - shard-dg2-set2: [SKIP][312] ([Intel XE#2136]) -> [SKIP][313] ([Intel XE#1158]) [312]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-2450-dfcd517d1169ab05be63134ba5cbc7bfaf030eb1/shard-dg2-466/igt@kms_frontbuffer_tracking@plane-fbc-rte.html [313]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-143203v1/shard-dg2-436/igt@kms_frontbuffer_tracking@plane-fbc-rte.html * igt@kms_frontbuffer_tracking@psr-1p-primscrn-pri-shrfb-draw-render: - shard-dg2-set2: [SKIP][314] ([Intel XE#653]) -> [SKIP][315] ([Intel XE#2136] / [Intel XE#2351]) +3 other tests skip [314]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-2450-dfcd517d1169ab05be63134ba5cbc7bfaf030eb1/shard-dg2-434/igt@kms_frontbuffer_tracking@psr-1p-primscrn-pri-shrfb-draw-render.html [315]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-143203v1/shard-dg2-466/igt@kms_frontbuffer_tracking@psr-1p-primscrn-pri-shrfb-draw-render.html * igt@kms_frontbuffer_tracking@psr-2p-primscrn-shrfb-msflip-blt: - shard-dg2-set2: [SKIP][316] ([Intel XE#2136] / [Intel XE#2351]) -> [SKIP][317] ([Intel XE#653]) +6 other tests skip [316]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-2450-dfcd517d1169ab05be63134ba5cbc7bfaf030eb1/shard-dg2-466/igt@kms_frontbuffer_tracking@psr-2p-primscrn-shrfb-msflip-blt.html [317]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-143203v1/shard-dg2-435/igt@kms_frontbuffer_tracking@psr-2p-primscrn-shrfb-msflip-blt.html * igt@kms_hdr@brightness-with-hdr: - shard-dg2-set2: [SKIP][318] ([Intel XE#455]) -> [SKIP][319] ([Intel XE#2423] / [i915#2575]) +3 other tests skip [318]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-2450-dfcd517d1169ab05be63134ba5cbc7bfaf030eb1/shard-dg2-434/igt@kms_hdr@brightness-with-hdr.html [319]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-143203v1/shard-dg2-466/igt@kms_hdr@brightness-with-hdr.html * igt@kms_histogram@algo-color: - shard-dg2-set2: [SKIP][320] ([Intel XE#2423] / [i915#2575]) -> [SKIP][321] ([Intel XE#3897]) [320]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-2450-dfcd517d1169ab05be63134ba5cbc7bfaf030eb1/shard-dg2-466/igt@kms_histogram@algo-color.html [321]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-143203v1/shard-dg2-434/igt@kms_histogram@algo-color.html * igt@kms_plane_scaling@plane-downscale-factor-0-25-with-pixel-format: - shard-dg2-set2: [SKIP][322] ([Intel XE#2423] / [i915#2575]) -> [SKIP][323] ([Intel XE#2763] / [Intel XE#455]) [322]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-2450-dfcd517d1169ab05be63134ba5cbc7bfaf030eb1/shard-dg2-466/igt@kms_plane_scaling@plane-downscale-factor-0-25-with-pixel-format.html [323]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-143203v1/shard-dg2-435/igt@kms_plane_scaling@plane-downscale-factor-0-25-with-pixel-format.html * igt@kms_pm_backlight@fade: - shard-dg2-set2: [SKIP][324] ([Intel XE#2136]) -> [SKIP][325] ([Intel XE#870]) +1 other test skip [324]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-2450-dfcd517d1169ab05be63134ba5cbc7bfaf030eb1/shard-dg2-466/igt@kms_pm_backlight@fade.html [325]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-143203v1/shard-dg2-435/igt@kms_pm_backlight@fade.html * igt@kms_pm_dc@dc3co-vpb-simulation: - shard-dg2-set2: [SKIP][326] ([Intel XE#2136] / [Intel XE#2351]) -> [SKIP][327] ([Intel XE#1122]) [326]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-2450-dfcd517d1169ab05be63134ba5cbc7bfaf030eb1/shard-dg2-466/igt@kms_pm_dc@dc3co-vpb-simulation.html [327]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-143203v1/shard-dg2-436/igt@kms_pm_dc@dc3co-vpb-simulation.html * igt@kms_pm_dc@dc6-dpms: - shard-dg2-set2: [SKIP][328] ([Intel XE#2136] / [Intel XE#2351]) -> [SKIP][329] ([Intel XE#908]) [328]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-2450-dfcd517d1169ab05be63134ba5cbc7bfaf030eb1/shard-dg2-466/igt@kms_pm_dc@dc6-dpms.html [329]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-143203v1/shard-dg2-435/igt@kms_pm_dc@dc6-dpms.html * igt@kms_pm_dc@deep-pkgc: - shard-dg2-set2: [SKIP][330] ([Intel XE#2136]) -> [SKIP][331] ([Intel XE#908]) [330]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-2450-dfcd517d1169ab05be63134ba5cbc7bfaf030eb1/shard-dg2-466/igt@kms_pm_dc@deep-pkgc.html [331]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-143203v1/shard-dg2-434/igt@kms_pm_dc@deep-pkgc.html * igt@kms_psr2_sf@fbc-pr-cursor-plane-update-sf: - shard-dg2-set2: [SKIP][332] ([Intel XE#2136]) -> [SKIP][333] ([Intel XE#1489]) +5 other tests skip [332]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-2450-dfcd517d1169ab05be63134ba5cbc7bfaf030eb1/shard-dg2-466/igt@kms_psr2_sf@fbc-pr-cursor-plane-update-sf.html [333]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-143203v1/shard-dg2-436/igt@kms_psr2_sf@fbc-pr-cursor-plane-update-sf.html * igt@kms_psr2_sf@pr-cursor-plane-move-continuous-sf: - shard-dg2-set2: [SKIP][334] ([Intel XE#1489]) -> [SKIP][335] ([Intel XE#2136]) +3 other tests skip [334]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-2450-dfcd517d1169ab05be63134ba5cbc7bfaf030eb1/shard-dg2-434/igt@kms_psr2_sf@pr-cursor-plane-move-continuous-sf.html [335]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-143203v1/shard-dg2-466/igt@kms_psr2_sf@pr-cursor-plane-move-continuous-sf.html * igt@kms_psr2_su@page_flip-nv12: - shard-dg2-set2: [SKIP][336] ([Intel XE#2136]) -> [SKIP][337] ([Intel XE#1122]) [336]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-2450-dfcd517d1169ab05be63134ba5cbc7bfaf030eb1/shard-dg2-466/igt@kms_psr2_su@page_flip-nv12.html [337]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-143203v1/shard-dg2-435/igt@kms_psr2_su@page_flip-nv12.html * igt@kms_psr@fbc-pr-no-drrs: - shard-dg2-set2: [SKIP][338] ([Intel XE#2850] / [Intel XE#929]) -> [SKIP][339] ([Intel XE#2136] / [Intel XE#2351]) [338]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-2450-dfcd517d1169ab05be63134ba5cbc7bfaf030eb1/shard-dg2-434/igt@kms_psr@fbc-pr-no-drrs.html [339]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-143203v1/shard-dg2-466/igt@kms_psr@fbc-pr-no-drrs.html * igt@kms_psr@fbc-psr-sprite-render: - shard-dg2-set2: [SKIP][340] ([Intel XE#2850] / [Intel XE#929]) -> [SKIP][341] ([Intel XE#2136]) +5 other tests skip [340]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-2450-dfcd517d1169ab05be63134ba5cbc7bfaf030eb1/shard-dg2-434/igt@kms_psr@fbc-psr-sprite-render.html [341]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-143203v1/shard-dg2-466/igt@kms_psr@fbc-psr-sprite-render.html * igt@kms_psr@fbc-psr2-cursor-blt: - shard-dg2-set2: [SKIP][342] ([Intel XE#2136] / [Intel XE#2351]) -> [SKIP][343] ([Intel XE#2850] / [Intel XE#929]) +1 other test skip [342]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-2450-dfcd517d1169ab05be63134ba5cbc7bfaf030eb1/shard-dg2-466/igt@kms_psr@fbc-psr2-cursor-blt.html [343]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-143203v1/shard-dg2-435/igt@kms_psr@fbc-psr2-cursor-blt.html * igt@kms_psr@fbc-psr2-cursor-plane-onoff: - shard-dg2-set2: [SKIP][344] ([Intel XE#2136]) -> [SKIP][345] ([Intel XE#2850] / [Intel XE#929]) +10 other tests skip [344]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-2450-dfcd517d1169ab05be63134ba5cbc7bfaf030eb1/shard-dg2-466/igt@kms_psr@fbc-psr2-cursor-plane-onoff.html [345]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-143203v1/shard-dg2-435/igt@kms_psr@fbc-psr2-cursor-plane-onoff.html * igt@kms_psr@psr-cursor-plane-move: - shard-dg2-set2: [SKIP][346] ([Intel XE#2351]) -> [SKIP][347] ([Intel XE#2850] / [Intel XE#929]) [346]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-2450-dfcd517d1169ab05be63134ba5cbc7bfaf030eb1/shard-dg2-466/igt@kms_psr@psr-cursor-plane-move.html [347]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-143203v1/shard-dg2-435/igt@kms_psr@psr-cursor-plane-move.html * igt@kms_rotation_crc@bad-tiling: - shard-dg2-set2: [SKIP][348] ([Intel XE#3414]) -> [SKIP][349] ([Intel XE#2423] / [i915#2575]) [348]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-2450-dfcd517d1169ab05be63134ba5cbc7bfaf030eb1/shard-dg2-434/igt@kms_rotation_crc@bad-tiling.html [349]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-143203v1/shard-dg2-466/igt@kms_rotation_crc@bad-tiling.html * igt@kms_rotation_crc@primary-y-tiled-reflect-x-180: - shard-dg2-set2: [SKIP][350] ([Intel XE#1127]) -> [SKIP][351] ([Intel XE#2423] / [i915#2575]) [350]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-2450-dfcd517d1169ab05be63134ba5cbc7bfaf030eb1/shard-dg2-434/igt@kms_rotation_crc@primary-y-tiled-reflect-x-180.html [351]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-143203v1/shard-dg2-466/igt@kms_rotation_crc@primary-y-tiled-reflect-x-180.html * igt@kms_rotation_crc@primary-y-tiled-reflect-x-90: - shard-dg2-set2: [SKIP][352] ([Intel XE#2423] / [i915#2575]) -> [SKIP][353] ([Intel XE#3414]) +1 other test skip [352]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-2450-dfcd517d1169ab05be63134ba5cbc7bfaf030eb1/shard-dg2-466/igt@kms_rotation_crc@primary-y-tiled-reflect-x-90.html [353]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-143203v1/shard-dg2-435/igt@kms_rotation_crc@primary-y-tiled-reflect-x-90.html * igt@xe_ccs@suspend-resume: - shard-bmg: [INCOMPLETE][354] ([Intel XE#3918]) -> [FAIL][355] ([Intel XE#3981]) [354]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-2450-dfcd517d1169ab05be63134ba5cbc7bfaf030eb1/shard-bmg-5/igt@xe_ccs@suspend-resume.html [355]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-143203v1/shard-bmg-3/igt@xe_ccs@suspend-resume.html * igt@xe_compute_preempt@compute-threadgroup-preempt: - shard-dg2-set2: [SKIP][356] ([Intel XE#1130]) -> [SKIP][357] ([Intel XE#1280] / [Intel XE#455]) [356]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-2450-dfcd517d1169ab05be63134ba5cbc7bfaf030eb1/shard-dg2-466/igt@xe_compute_preempt@compute-threadgroup-preempt.html [357]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-143203v1/shard-dg2-434/igt@xe_compute_preempt@compute-threadgroup-preempt.html * igt@xe_copy_basic@mem-copy-linear-0xfd: - shard-dg2-set2: [SKIP][358] ([Intel XE#1130]) -> [SKIP][359] ([Intel XE#1123]) [358]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-2450-dfcd517d1169ab05be63134ba5cbc7bfaf030eb1/shard-dg2-466/igt@xe_copy_basic@mem-copy-linear-0xfd.html [359]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-143203v1/shard-dg2-435/igt@xe_copy_basic@mem-copy-linear-0xfd.html * igt@xe_copy_basic@mem-set-linear-0xfd: - shard-dg2-set2: [SKIP][360] ([Intel XE#1130]) -> [SKIP][361] ([Intel XE#1126]) [360]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-2450-dfcd517d1169ab05be63134ba5cbc7bfaf030eb1/shard-dg2-466/igt@xe_copy_basic@mem-set-linear-0xfd.html [361]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-143203v1/shard-dg2-436/igt@xe_copy_basic@mem-set-linear-0xfd.html * igt@xe_eudebug@multiple-sessions: - shard-dg2-set2: [SKIP][362] ([Intel XE#1130]) -> [SKIP][363] ([Intel XE#2905]) +11 other tests skip [362]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-2450-dfcd517d1169ab05be63134ba5cbc7bfaf030eb1/shard-dg2-466/igt@xe_eudebug@multiple-sessions.html [363]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-143203v1/shard-dg2-435/igt@xe_eudebug@multiple-sessions.html * igt@xe_eudebug_online@interrupt-all-set-breakpoint: - shard-dg2-set2: [SKIP][364] ([Intel XE#2905]) -> [SKIP][365] ([Intel XE#1130]) +4 other tests skip [364]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-2450-dfcd517d1169ab05be63134ba5cbc7bfaf030eb1/shard-dg2-434/igt@xe_eudebug_online@interrupt-all-set-breakpoint.html [365]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-143203v1/shard-dg2-466/igt@xe_eudebug_online@interrupt-all-set-breakpoint.html * igt@xe_evict@evict-beng-large-multi-vm-cm: - shard-dg2-set2: [SKIP][366] ([Intel XE#1130]) -> [FAIL][367] ([Intel XE#1600]) [366]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-2450-dfcd517d1169ab05be63134ba5cbc7bfaf030eb1/shard-dg2-466/igt@xe_evict@evict-beng-large-multi-vm-cm.html [367]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-143203v1/shard-dg2-435/igt@xe_evict@evict-beng-large-multi-vm-cm.html * igt@xe_evict@evict-beng-mixed-many-threads-large: - shard-dg2-set2: [SKIP][368] ([Intel XE#1130]) -> [TIMEOUT][369] ([Intel XE#1473]) [368]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-2450-dfcd517d1169ab05be63134ba5cbc7bfaf030eb1/shard-dg2-466/igt@xe_evict@evict-beng-mixed-many-threads-large.html [369]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-143203v1/shard-dg2-434/igt@xe_evict@evict-beng-mixed-many-threads-large.html * igt@xe_exec_fault_mode@many-execqueues-userptr-invalidate-imm: - shard-dg2-set2: [SKIP][370] ([Intel XE#1130]) -> [SKIP][371] ([Intel XE#288]) +25 other tests skip [370]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-2450-dfcd517d1169ab05be63134ba5cbc7bfaf030eb1/shard-dg2-466/igt@xe_exec_fault_mode@many-execqueues-userptr-invalidate-imm.html [371]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-143203v1/shard-dg2-436/igt@xe_exec_fault_mode@many-execqueues-userptr-invalidate-imm.html * igt@xe_exec_fault_mode@once-bindexecqueue-userptr-rebind: - shard-dg2-set2: [SKIP][372] ([Intel XE#288]) -> [SKIP][373] ([Intel XE#1130]) +8 other tests skip [372]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-2450-dfcd517d1169ab05be63134ba5cbc7bfaf030eb1/shard-dg2-434/igt@xe_exec_fault_mode@once-bindexecqueue-userptr-rebind.html [373]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-143203v1/shard-dg2-466/igt@xe_exec_fault_mode@once-bindexecqueue-userptr-rebind.html * igt@xe_huc_copy@huc_copy: - shard-dg2-set2: [SKIP][374] ([Intel XE#1130]) -> [SKIP][375] ([Intel XE#255]) [374]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-2450-dfcd517d1169ab05be63134ba5cbc7bfaf030eb1/shard-dg2-466/igt@xe_huc_copy@huc_copy.html [375]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-143203v1/shard-dg2-435/igt@xe_huc_copy@huc_copy.html * igt@xe_oa@oa-unit-exclusive-stream-sample-oa: - shard-dg2-set2: [SKIP][376] ([Intel XE#2541] / [Intel XE#3573]) -> [SKIP][377] ([Intel XE#1130]) +3 other tests skip [376]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-2450-dfcd517d1169ab05be63134ba5cbc7bfaf030eb1/shard-dg2-434/igt@xe_oa@oa-unit-exclusive-stream-sample-oa.html [377]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-143203v1/shard-dg2-466/igt@xe_oa@oa-unit-exclusive-stream-sample-oa.html * igt@xe_oa@whitelisted-registers-userspace-config: - shard-dg2-set2: [SKIP][378] ([Intel XE#1130]) -> [SKIP][379] ([Intel XE#2541] / [Intel XE#3573]) +6 other tests skip [378]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-2450-dfcd517d1169ab05be63134ba5cbc7bfaf030eb1/shard-dg2-466/igt@xe_oa@whitelisted-registers-userspace-config.html [379]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-143203v1/shard-dg2-435/igt@xe_oa@whitelisted-registers-userspace-config.html * igt@xe_pat@pat-index-xe2: - shard-dg2-set2: [SKIP][380] ([Intel XE#1130]) -> [SKIP][381] ([Intel XE#977]) [380]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-2450-dfcd517d1169ab05be63134ba5cbc7bfaf030eb1/shard-dg2-466/igt@xe_pat@pat-index-xe2.html [381]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-143203v1/shard-dg2-436/igt@xe_pat@pat-index-xe2.html * igt@xe_pm@d3cold-basic: - shard-dg2-set2: [SKIP][382] ([Intel XE#2284] / [Intel XE#366]) -> [SKIP][383] ([Intel XE#1130]) [382]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-2450-dfcd517d1169ab05be63134ba5cbc7bfaf030eb1/shard-dg2-434/igt@xe_pm@d3cold-basic.html [383]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-143203v1/shard-dg2-466/igt@xe_pm@d3cold-basic.html * igt@xe_query@multigpu-query-oa-units: - shard-dg2-set2: [SKIP][384] ([Intel XE#1130]) -> [SKIP][385] ([Intel XE#944]) +2 other tests skip [384]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-2450-dfcd517d1169ab05be63134ba5cbc7bfaf030eb1/shard-dg2-466/igt@xe_query@multigpu-query-oa-units.html [385]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-143203v1/shard-dg2-435/igt@xe_query@multigpu-query-oa-units.html * igt@xe_query@multigpu-query-uc-fw-version-huc: - shard-dg2-set2: [SKIP][386] ([Intel XE#944]) -> [SKIP][387] ([Intel XE#1130]) [386]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-2450-dfcd517d1169ab05be63134ba5cbc7bfaf030eb1/shard-dg2-434/igt@xe_query@multigpu-query-uc-fw-version-huc.html [387]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-143203v1/shard-dg2-466/igt@xe_query@multigpu-query-uc-fw-version-huc.html [Intel XE#1033]: https://gitlab.freedesktop.org/drm/xe/kernel/issues/1033 [Intel XE#1091]: https://gitlab.freedesktop.org/drm/xe/kernel/issues/1091 [Intel XE#1122]: https://gitlab.freedesktop.org/drm/xe/kernel/issues/1122 [Intel XE#1123]: https://gitlab.freedesktop.org/drm/xe/kernel/issues/1123 [Intel XE#1124]: https://gitlab.freedesktop.org/drm/xe/kernel/issues/1124 [Intel XE#1125]: https://gitlab.freedesktop.org/drm/xe/kernel/issues/1125 [Intel XE#1126]: https://gitlab.freedesktop.org/drm/xe/kernel/issues/1126 [Intel XE#1127]: https://gitlab.freedesktop.org/drm/xe/kernel/issues/1127 [Intel XE#1128]: https://gitlab.freedesktop.org/drm/xe/kernel/issues/1128 [Intel XE#1130]: https://gitlab.freedesktop.org/drm/xe/kernel/issues/1130 [Intel XE#1131]: https://gitlab.freedesktop.org/drm/xe/kernel/issues/1131 [Intel XE#1135]: https://gitlab.freedesktop.org/drm/xe/kernel/issues/1135 [Intel XE#1138]: https://gitlab.freedesktop.org/drm/xe/kernel/issues/1138 [Intel XE#1158]: https://gitlab.freedesktop.org/drm/xe/kernel/issues/1158 [Intel XE#1173]: https://gitlab.freedesktop.org/drm/xe/kernel/issues/1173 [Intel XE#1178]: https://gitlab.freedesktop.org/drm/xe/kernel/issues/1178 [Intel XE#1280]: https://gitlab.freedesktop.org/drm/xe/kernel/issues/1280 [Intel XE#1358]: https://gitlab.freedesktop.org/drm/xe/kernel/issues/1358 [Intel XE#1392]: https://gitlab.freedesktop.org/drm/xe/kernel/issues/1392 [Intel XE#1401]: https://gitlab.freedesktop.org/drm/xe/kernel/issues/1401 [Intel XE#1407]: https://gitlab.freedesktop.org/drm/xe/kernel/issues/1407 [Intel XE#1416]: https://gitlab.freedesktop.org/drm/xe/kernel/issues/1416 [Intel XE#1421]: https://gitlab.freedesktop.org/drm/xe/kernel/issues/1421 [Intel XE#1424]: https://gitlab.freedesktop.org/drm/xe/kernel/issues/1424 [Intel XE#1430]: https://gitlab.freedesktop.org/drm/xe/kernel/issues/1430 [Intel XE#1435]: https://gitlab.freedesktop.org/drm/xe/kernel/issues/1435 [Intel XE#1439]: https://gitlab.freedesktop.org/drm/xe/kernel/issues/1439 [Intel XE#1447]: https://gitlab.freedesktop.org/drm/xe/kernel/issues/1447 [Intel XE#1473]: https://gitlab.freedesktop.org/drm/xe/kernel/issues/1473 [Intel XE#1489]: https://gitlab.freedesktop.org/drm/xe/kernel/issues/1489 [Intel XE#1499]: https://gitlab.freedesktop.org/drm/xe/kernel/issues/1499 [Intel XE#1500]: https://gitlab.freedesktop.org/drm/xe/kernel/issues/1500 [Intel XE#1600]: https://gitlab.freedesktop.org/drm/xe/kernel/issues/1600 [Intel XE#1607]: https://gitlab.freedesktop.org/drm/xe/kernel/issues/1607 [Intel XE#1695]: https://gitlab.freedesktop.org/drm/xe/kernel/issues/1695 [Intel XE#1727]: https://gitlab.freedesktop.org/drm/xe/kernel/issues/1727 [Intel XE#1745]: https://gitlab.freedesktop.org/drm/xe/kernel/issues/1745 [Intel XE#1794]: https://gitlab.freedesktop.org/drm/xe/kernel/issues/1794 [Intel XE#1885]: https://gitlab.freedesktop.org/drm/xe/kernel/issues/1885 [Intel XE#2134]: https://gitlab.freedesktop.org/drm/xe/kernel/issues/2134 [Intel XE#2136]: https://gitlab.freedesktop.org/drm/xe/kernel/issues/2136 [Intel XE#2168]: https://gitlab.freedesktop.org/drm/xe/kernel/issues/2168 [Intel XE#2191]: https://gitlab.freedesktop.org/drm/xe/kernel/issues/2191 [Intel XE#2234]: https://gitlab.freedesktop.org/drm/xe/kernel/issues/2234 [Intel XE#2244]: https://gitlab.freedesktop.org/drm/xe/kernel/issues/2244 [Intel XE#2245]: https://gitlab.freedesktop.org/drm/xe/kernel/issues/2245 [Intel XE#2252]: https://gitlab.freedesktop.org/drm/xe/kernel/issues/2252 [Intel XE#2284]: https://gitlab.freedesktop.org/drm/xe/kernel/issues/2284 [Intel XE#2293]: https://gitlab.freedesktop.org/drm/xe/kernel/issues/2293 [Intel XE#2311]: https://gitlab.freedesktop.org/drm/xe/kernel/issues/2311 [Intel XE#2313]: https://gitlab.freedesktop.org/drm/xe/kernel/issues/2313 [Intel XE#2320]: https://gitlab.freedesktop.org/drm/xe/kernel/issues/2320 [Intel XE#2322]: https://gitlab.freedesktop.org/drm/xe/kernel/issues/2322 [Intel XE#2327]: https://gitlab.freedesktop.org/drm/xe/kernel/issues/2327 [Intel XE#2330]: https://gitlab.freedesktop.org/drm/xe/kernel/issues/2330 [Intel XE#2333]: https://gitlab.freedesktop.org/drm/xe/kernel/issues/2333 [Intel XE#2351]: https://gitlab.freedesktop.org/drm/xe/kernel/issues/2351 [Intel XE#2370]: https://gitlab.freedesktop.org/drm/xe/kernel/issues/2370 [Intel XE#2380]: https://gitlab.freedesktop.org/drm/xe/kernel/issues/2380 [Intel XE#2390]: https://gitlab.freedesktop.org/drm/xe/kernel/issues/2390 [Intel XE#2393]: https://gitlab.freedesktop.org/drm/xe/kernel/issues/2393 [Intel XE#2423]: https://gitlab.freedesktop.org/drm/xe/kernel/issues/2423 [Intel XE#2446]: https://gitlab.freedesktop.org/drm/xe/kernel/issues/2446 [Intel XE#2472]: https://gitlab.freedesktop.org/drm/xe/kernel/issues/2472 [Intel XE#2486]: https://gitlab.freedesktop.org/drm/xe/kernel/issues/2486 [Intel XE#2541]: https://gitlab.freedesktop.org/drm/xe/kernel/issues/2541 [Intel XE#255]: https://gitlab.freedesktop.org/drm/xe/kernel/issues/255 [Intel XE#2550]: https://gitlab.freedesktop.org/drm/xe/kernel/issues/2550 [Intel XE#2597]: https://gitlab.freedesktop.org/drm/xe/kernel/issues/2597 [Intel XE#261]: https://gitlab.freedesktop.org/drm/xe/kernel/issues/261 [Intel XE#2669]: https://gitlab.freedesktop.org/drm/xe/kernel/issues/2669 [Intel XE#2692]: https://gitlab.freedesktop.org/drm/xe/kernel/issues/2692 [Intel XE#2763]: https://gitlab.freedesktop.org/drm/xe/kernel/issues/2763 [Intel XE#2849]: https://gitlab.freedesktop.org/drm/xe/kernel/issues/2849 [Intel XE#2850]: https://gitlab.freedesktop.org/drm/xe/kernel/issues/2850 [Intel XE#288]: https://gitlab.freedesktop.org/drm/xe/kernel/issues/288 [Intel XE#2882]: https://gitlab.freedesktop.org/drm/xe/kernel/issues/2882 [Intel XE#2887]: https://gitlab.freedesktop.org/drm/xe/kernel/issues/2887 [Intel XE#2905]: https://gitlab.freedesktop.org/drm/xe/kernel/issues/2905 [Intel XE#2907]: https://gitlab.freedesktop.org/drm/xe/kernel/issues/2907 [Intel XE#2953]: https://gitlab.freedesktop.org/drm/xe/kernel/issues/2953 [Intel XE#301]: https://gitlab.freedesktop.org/drm/xe/kernel/issues/301 [Intel XE#306]: https://gitlab.freedesktop.org/drm/xe/kernel/issues/306 [Intel XE#307]: https://gitlab.freedesktop.org/drm/xe/kernel/issues/307 [Intel XE#308]: https://gitlab.freedesktop.org/drm/xe/kernel/issues/308 [Intel XE#309]: https://gitlab.freedesktop.org/drm/xe/kernel/issues/309 [Intel XE#310]: https://gitlab.freedesktop.org/drm/xe/kernel/issues/310 [Intel XE#3124]: https://gitlab.freedesktop.org/drm/xe/kernel/issues/3124 [Intel XE#314]: https://gitlab.freedesktop.org/drm/xe/kernel/issues/314 [Intel XE#3141]: https://gitlab.freedesktop.org/drm/xe/kernel/issues/3141 [Intel XE#316]: https://gitlab.freedesktop.org/drm/xe/kernel/issues/316 [Intel XE#323]: https://gitlab.freedesktop.org/drm/xe/kernel/issues/323 [Intel XE#324]: https://gitlab.freedesktop.org/drm/xe/kernel/issues/324 [Intel XE#3249]: https://gitlab.freedesktop.org/drm/xe/kernel/issues/3249 [Intel XE#3288]: https://gitlab.freedesktop.org/drm/xe/kernel/issues/3288 [Intel XE#3309]: https://gitlab.freedesktop.org/drm/xe/kernel/issues/3309 [Intel XE#3321]: https://gitlab.freedesktop.org/drm/xe/kernel/issues/3321 [Intel XE#3342]: https://gitlab.freedesktop.org/drm/xe/kernel/issues/3342 [Intel XE#3383]: https://gitlab.freedesktop.org/drm/xe/kernel/issues/3383 [Intel XE#3414]: https://gitlab.freedesktop.org/drm/xe/kernel/issues/3414 [Intel XE#3432]: https://gitlab.freedesktop.org/drm/xe/kernel/issues/3432 [Intel XE#3440]: https://gitlab.freedesktop.org/drm/xe/kernel/issues/3440 [Intel XE#3546]: https://gitlab.freedesktop.org/drm/xe/kernel/issues/3546 [Intel XE#3573]: https://gitlab.freedesktop.org/drm/xe/kernel/issues/3573 [Intel XE#361]: https://gitlab.freedesktop.org/drm/xe/kernel/issues/361 [Intel XE#366]: https://gitlab.freedesktop.org/drm/xe/kernel/issues/366 [Intel XE#367]: https://gitlab.freedesktop.org/drm/xe/kernel/issues/367 [Intel XE#373]: https://gitlab.freedesktop.org/drm/xe/kernel/issues/373 [Intel XE#3864]: https://gitlab.freedesktop.org/drm/xe/kernel/issues/3864 [Intel XE#3876]: https://gitlab.freedesktop.org/drm/xe/kernel/issues/3876 [Intel XE#3879]: https://gitlab.freedesktop.org/drm/xe/kernel/issues/3879 [Intel XE#3884]: https://gitlab.freedesktop.org/drm/xe/kernel/issues/3884 [Intel XE#3897]: https://gitlab.freedesktop.org/drm/xe/kernel/issues/3897 [Intel XE#3918]: https://gitlab.freedesktop.org/drm/xe/kernel/issues/3918 [Intel XE#3981]: https://gitlab.freedesktop.org/drm/xe/kernel/issues/3981 [Intel XE#3999]: https://gitlab.freedesktop.org/drm/xe/kernel/issues/3999 [Intel XE#455]: https://gitlab.freedesktop.org/drm/xe/kernel/issues/455 [Intel XE#584]: https://gitlab.freedesktop.org/drm/xe/kernel/issues/584 [Intel XE#607]: https://gitlab.freedesktop.org/drm/xe/kernel/issues/607 [Intel XE#610]: https://gitlab.freedesktop.org/drm/xe/kernel/issues/610 [Intel XE#651]: https://gitlab.freedesktop.org/drm/xe/kernel/issues/651 [Intel XE#653]: https://gitlab.freedesktop.org/drm/xe/kernel/issues/653 [Intel XE#656]: https://gitlab.freedesktop.org/drm/xe/kernel/issues/656 [Intel XE#658]: https://gitlab.freedesktop.org/drm/xe/kernel/issues/658 [Intel XE#688]: https://gitlab.freedesktop.org/drm/xe/kernel/issues/688 [Intel XE#718]: https://gitlab.freedesktop.org/drm/xe/kernel/issues/718 [Intel XE#756]: https://gitlab.freedesktop.org/drm/xe/kernel/issues/756 [Intel XE#787]: https://gitlab.freedesktop.org/drm/xe/kernel/issues/787 [Intel XE#827]: https://gitlab.freedesktop.org/drm/xe/kernel/issues/827 [Intel XE#870]: https://gitlab.freedesktop.org/drm/xe/kernel/issues/870 [Intel XE#873]: https://gitlab.freedesktop.org/drm/xe/kernel/issues/873 [Intel XE#877]: https://gitlab.freedesktop.org/drm/xe/kernel/issues/877 [Intel XE#908]: https://gitlab.freedesktop.org/drm/xe/kernel/issues/908 [Intel XE#929]: https://gitlab.freedesktop.org/drm/xe/kernel/issues/929 [Intel XE#944]: https://gitlab.freedesktop.org/drm/xe/kernel/issues/944 [Intel XE#958]: https://gitlab.freedesktop.org/drm/xe/kernel/issues/958 [Intel XE#977]: https://gitlab.freedesktop.org/drm/xe/kernel/issues/977 [i915#2575]: https://gitlab.freedesktop.org/drm/i915/kernel/-/issues/2575 [i915#5274]: https://gitlab.freedesktop.org/drm/i915/kernel/-/issues/5274 Build changes ------------- * Linux: xe-2450-dfcd517d1169ab05be63134ba5cbc7bfaf030eb1 -> xe-pw-143203v1 IGT_8179: 183b33f81365dd4a57fe3100a13d3fb13788d158 @ https://gitlab.freedesktop.org/drm/igt-gpu-tools.git xe-2450-dfcd517d1169ab05be63134ba5cbc7bfaf030eb1: dfcd517d1169ab05be63134ba5cbc7bfaf030eb1 xe-pw-143203v1: 143203v1 == Logs == For more details see: https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-143203v1/index.html [-- Attachment #2: Type: text/html, Size: 130938 bytes --] ^ permalink raw reply [flat|nested] 22+ messages in thread
end of thread, other threads:[~2025-01-23 14:21 UTC | newest] Thread overview: 22+ messages (download: mbox.gz follow: Atom feed -- links below jump to the message on this page -- 2025-01-07 20:22 [PATCH v3 1/1] drm/xe/guc: Fix GuC log/ct output via debugfs Julia Filipchuk 2025-01-07 20:57 ` ✓ CI.Patch_applied: success for series starting with [v3,1/1] " Patchwork 2025-01-07 20:58 ` ✓ CI.checkpatch: " Patchwork 2025-01-07 20:59 ` ✓ CI.KUnit: " Patchwork 2025-01-07 21:10 ` [PATCH v3 1/1] " Lucas De Marchi 2025-01-08 20:14 ` John Harrison 2025-01-08 22:11 ` Lucas De Marchi 2025-01-08 23:59 ` John Harrison 2025-01-09 15:39 ` Lucas De Marchi 2025-01-09 20:40 ` John Harrison 2025-01-09 22:43 ` Lucas De Marchi 2025-01-22 16:45 ` John Harrison 2025-01-22 16:59 ` Souza, Jose 2025-01-22 18:29 ` Souza, Jose 2025-01-22 21:09 ` John Harrison 2025-01-23 14:02 ` Souza, Jose 2025-01-23 14:21 ` Lucas De Marchi 2025-01-07 21:25 ` ✓ CI.Build: success for series starting with [v3,1/1] " Patchwork 2025-01-07 21:28 ` ✓ CI.Hooks: " Patchwork 2025-01-07 21:30 ` ✓ CI.checksparse: " Patchwork 2025-01-07 21:55 ` ✓ Xe.CI.BAT: " Patchwork 2025-01-09 10:47 ` ✗ Xe.CI.Full: failure " Patchwork
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox