mes_v12_1_sw_init() seeded an 8 KB dbgext buffer,
so the log came up at boot with no module parameter.
Leave dbgext_runtime_kb at 0 to disable it by default.
hw_init() still starts the log when mes_dbgext_buffer_size is set,
and debugfs can still enable it at runtime.

Signed-off-by: Yongqiang Sun <[email protected]>
---
 drivers/gpu/drm/amd/amdgpu/mes_v12_1.c | 9 ---------
 1 file changed, 9 deletions(-)

diff --git a/drivers/gpu/drm/amd/amdgpu/mes_v12_1.c 
b/drivers/gpu/drm/amd/amdgpu/mes_v12_1.c
index 65adbf5541e4..a31da8d12fb4 100644
--- a/drivers/gpu/drm/amd/amdgpu/mes_v12_1.c
+++ b/drivers/gpu/drm/amd/amdgpu/mes_v12_1.c
@@ -1583,15 +1583,6 @@ static int mes_v12_1_sw_init(struct amdgpu_ip_block 
*ip_block)
        adev->mes.kiq_hw_fini = &mes_v12_1_kiq_hw_fini;
        adev->mes.enable_legacy_queue_map = true;
 
-       /*
-        * Enable mes_dbgext by default on mes12.1: seed an 8 KB runtime
-        * request so hw_init() -> amdgpu_mes_dbgext_start() brings the log up 
at
-        * boot with no mes_dbgext_buffer_size module param needed.  The
-        * collection mode still follows mes_dbgext_options (default bit0 = 1,
-        * interrupt-driven).  Both module params continue to override this.
-        */
-       adev->mes.dbgext_runtime_kb = 8;
-
        adev->mes.event_log_size = AMDGPU_MAX_MES_PIPES *
                                   AMDGPU_MES_LOG_BUFFER_SIZE * num_xcc;
 
-- 
2.43.0

Reply via email to