Skip to contentSkip to conversation

drm/i915: Remove unreachable code

PATCH In review Vinicius Tinti 3 participants 6 messages Jan 29, 2021 – Feb 1, 2021

Subsystems (3)
lore
Share & tools
lore
#0 lore raw

PATCH 1/1 drm/i915: Remove unreachable code

By enabling -Wunreachable-code-aggressive on Clang the following code paths are unreachable.

Commit ce22c320b8ca ("drm/i915/sdvo: convert to encoder disable/enable") Commit 19f1f627b333 ("drm/i915/gt: Move ivb GT workarounds from init_clock_gating to workarounds")
Commit 0a97015d45ee ("drm/i915: Compress GPU objects in error state")

By removing the unreachable code at drivers/gpu/drm/i915/display/intel_sdvo.c the function intel_sdvo_set_encoder_power_state becomes unused.

Commit ea5b213ad4b1 ("drm/i915: Subclass intel_encoder.")

Clang warns unreachable:

drivers/gpu/drm/i915/display/intel_sdvo.c:1768:3: warning: code will never be executed [-Wunreachable-code]

                intel_sdvo_set_encoder_power_state(intel_sdvo,
                ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
drivers/gpu/drm/i915/display/intel_sdvo.c:1767:6: note: silence by adding
parentheses to mark code as explicitly dead
        if (0)
            ^
            /* DISABLES CODE */ ( )
drivers/gpu/drm/i915/display/intel_sdvo.c:1852:3: warning: code will never
be executed [-Wunreachable-code]
                intel_sdvo_set_encoder_power_state(intel_sdvo,
                ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
drivers/gpu/drm/i915/display/intel_sdvo.c:1851:6: note: silence by adding
parentheses to mark code as explicitly dead
        if (0)
            ^
            /* DISABLES CODE */ ( )

drivers/gpu/drm/i915/gt/intel_workarounds.c:884:3: warning: code will never be executed [-Wunreachable-code]

                wa_masked_dis(wal, CACHE_MODE_0_GEN7, HIZ_RAW_STALL_OPT_DISABLE);
                ^~~~~~~~~~~~~
drivers/gpu/drm/i915/gt/intel_workarounds.c:882:6: note: silence by adding
parentheses to mark code as explicitly dead
        if (0) { /* causes HiZ corruption on ivb:gt1 */
            ^
            /* DISABLES CODE */ ( )

drivers/gpu/drm/i915/i915_gpu_error.c:319:11: warning: code will never be executed [-Wunreachable-code]

        if (0 && zstream->total_out > zstream->total_in)
                 ^~~~~~~
drivers/gpu/drm/i915/i915_gpu_error.c:319:6: note: silence by adding
parentheses to mark code as explicitly dead
        if (0 && zstream->total_out > zstream->total_in)
            ^
            /* DISABLES CODE */ ( )

Clang warns unused after removing unreachable:

drivers/gpu/drm/i915/display/intel_sdvo.c:696:13: warning: unused function 'intel_sdvo_set_encoder_power_state' [-Wunused-function]
static bool intel_sdvo_set_encoder_power_state(struct intel_sdvo *intel_sdvo,

            ^
---
 drivers/gpu/drm/i915/display/intel_sdvo.c   | 30 ---------------------
 drivers/gpu/drm/i915/gt/intel_workarounds.c |  5 ----
 drivers/gpu/drm/i915/i915_gpu_error.c       |  4 ---
 3 files changed, 39 deletions(-)
drivers/gpu/drm/i915/display/intel_sdvo.c +0 -30
index 4eaa4aa86ecd..45d03b09f8f0 100644
@@ -693,30 +693,6 @@ static bool intel_sdvo_get_active_outputs(struct intel_sdvo *intel_sdvo,
 				    outputs, sizeof(*outputs));
 }
 
-static bool intel_sdvo_set_encoder_power_state(struct intel_sdvo *intel_sdvo,
-					       int mode)
-{
-	u8 state = SDVO_ENCODER_STATE_ON;
-
-	switch (mode) {
-	case DRM_MODE_DPMS_ON:
-		state = SDVO_ENCODER_STATE_ON;
-		break;
-	case DRM_MODE_DPMS_STANDBY:
-		state = SDVO_ENCODER_STATE_STANDBY;
-		break;
-	case DRM_MODE_DPMS_SUSPEND:
-		state = SDVO_ENCODER_STATE_SUSPEND;
-		break;
-	case DRM_MODE_DPMS_OFF:
-		state = SDVO_ENCODER_STATE_OFF;
-		break;
-	}
-
-	return intel_sdvo_set_value(intel_sdvo,
-				    SDVO_CMD_SET_ENCODER_POWER_STATE, &state, sizeof(state));
-}
-
 static bool intel_sdvo_get_input_pixel_clock_range(struct intel_sdvo *intel_sdvo,
 						   int *clock_min,
 						   int *clock_max)
@@ -1764,9 +1740,6 @@ static void intel_disable_sdvo(struct intel_atomic_state *state,
 		intel_sdvo_disable_audio(intel_sdvo);
 
 	intel_sdvo_set_active_outputs(intel_sdvo, 0);
-	if (0)
-		intel_sdvo_set_encoder_power_state(intel_sdvo,
-						   DRM_MODE_DPMS_OFF);
 
 	temp = intel_de_read(dev_priv, intel_sdvo->sdvo_reg);
 
@@ -1848,9 +1821,6 @@ static void intel_enable_sdvo(struct intel_atomic_state *state,
 			    "sync\n", SDVO_NAME(intel_sdvo));
 	}
 
-	if (0)
-		intel_sdvo_set_encoder_power_state(intel_sdvo,
-						   DRM_MODE_DPMS_ON);
 	intel_sdvo_set_active_outputs(intel_sdvo, intel_sdvo->attached_output);
 
 	if (pipe_config->has_audio)
drivers/gpu/drm/i915/gt/intel_workarounds.c +0 -5
index adc9a8ea410a..d60ff2c67138 100644
@@ -879,11 +879,6 @@ ivb_gt_workarounds_init(struct drm_i915_private *i915, struct i915_wa_list *wal)
 			   GEN7_FF_VS_SCHED_HW |
 			   GEN7_FF_DS_SCHED_HW);
 
-	if (0) { /* causes HiZ corruption on ivb:gt1 */
-		/* enable HiZ Raw Stall Optimization */
-		wa_masked_dis(wal, CACHE_MODE_0_GEN7, HIZ_RAW_STALL_OPT_DISABLE);
-	}
-
 	/* WaDisable4x2SubspanOptimization:ivb */
 	wa_masked_en(wal, CACHE_MODE_1, PIXEL_SUBSPAN_COLLECT_OPT_DISABLE);
 
drivers/gpu/drm/i915/i915_gpu_error.c +0 -4
index d8cac4c5881f..6ec699da1dc2 100644
@@ -315,10 +315,6 @@ static int compress_page(struct i915_vma_compress *c,
 		cond_resched();
 	} while (zstream->avail_in);
 
-	/* Fallback to uncompressed if we increase size? */
-	if (0 && zstream->total_out > zstream->total_in)
-		return -E2BIG;
-
 	return 0;
 }
 
Signature · 1 line
2.25.1
#1 lore raw

Quoting Vinicius Tinti (2021-01-29 18:15:19)

Quoted 2 lines

By enabling -Wunreachable-code-aggressive on Clang the following code paths are unreachable.

That code exists as commentary and, especially for sdvo, library functions that we may need in future.

The ivb-gt1 case => as we now set the gt level for ivb, should we not enable the optimisation for ivb unaffected by the w/a? Just no one has taken the time to see if it causes a regression.

For error state, the question remains whether we should revert to uncompressed data if the compressed stream is larger than the original. -Chris

#2 lore raw
Quoted 6 lines · Chris Wilson

Quoting Vinicius Tinti (2021-01-29 18:15:19)

Quoted 2 lines

By enabling -Wunreachable-code-aggressive on Clang the following code paths are unreachable.

That code exists as commentary and, especially for sdvo, library functions that we may need in future.

I would argue that this code could be removed since it is in git history. It can be restored when needed.

This will make the code cleaner.

Quoted 3 lines

The ivb-gt1 case => as we now set the gt level for ivb, should we not enable the optimisation for ivb unaffected by the w/a? Just no one has taken the time to see if it causes a regression.

I don't know. I just found out that the code is unreachable.

Quoted 2 lines

For error state, the question remains whether we should revert to uncompressed data if the compressed stream is larger than the original.

I don't know too.

In this last two cases the code could be commented and the decisions and problems explained in the comment section.

Quoted 1 line

-Chris

#3 lore raw

Quoting Vinicius Tinti (2021-01-30 12:34:11)

Quoted 5 lines · Chris Wilson
Quoted 4 lines

Quoting Vinicius Tinti (2021-01-29 18:15:19)

Quoted 2 lines

By enabling -Wunreachable-code-aggressive on Clang the following code paths are unreachable.

Quoted 7 lines
Quoted 2 lines

That code exists as commentary and, especially for sdvo, library functions that we may need in future.

I would argue that this code could be removed since it is in git history. It can be restored when needed.

This will make the code cleaner.

It doesn't change the control flow, so no complexity argument. It removes documentation from the code, so I have the opposite opinion.

Quoted 6 lines
Quoted 3 lines

The ivb-gt1 case => as we now set the gt level for ivb, should we not enable the optimisation for ivb unaffected by the w/a? Just no one has taken the time to see if it causes a regression.

I don't know. I just found out that the code is unreachable.

Quoted 7 lines
Quoted 2 lines

For error state, the question remains whether we should revert to uncompressed data if the compressed stream is larger than the original.

I don't know too.

In this last two cases the code could be commented and the decisions and problems explained in the comment section.

They already are, that is the point.
-Chris

#4 lore raw
Quoted 10 lines · Chris Wilson

Quoting Vinicius Tinti (2021-01-30 12:34:11)

Quoted 8 lines · Chris Wilson
Quoted 6 lines

Quoting Vinicius Tinti (2021-01-29 18:15:19)

Quoted 2 lines

By enabling -Wunreachable-code-aggressive on Clang the following code paths are unreachable.

That code exists as commentary and, especially for sdvo, library functions that we may need in future.

Quoted 7 lines
Quoted 4 lines

I would argue that this code could be removed since it is in git history. It can be restored when needed.

This will make the code cleaner.

It doesn't change the control flow, so no complexity argument. It removes documentation from the code, so I have the opposite opinion.

The last change in sdvo related to this function is from commit ce22c320b8ca ("drm/i915/sdvo: convert to encoder disable/enable"), which dates from 2012.

It has not been used or changed for a long time. I think it could be converted to a block comment. This will preserve the documentation purpose. What do you think?

All this will avoid having "if (0)".

Quoted 9 lines
Quoted 9 lines
Quoted 3 lines

The ivb-gt1 case => as we now set the gt level for ivb, should we not enable the optimisation for ivb unaffected by the w/a? Just no one has taken the time to see if it causes a regression.

I don't know. I just found out that the code is unreachable.

Quoted 2 lines

For error state, the question remains whether we should revert to uncompressed data if the compressed stream is larger than the original.

Quoted 6 lines
Quoted 4 lines

I don't know too.

In this last two cases the code could be commented and the decisions and problems explained in the comment section.

They already are, that is the point.

I meant making them a block comment. For example:

/*
* Enabling HiZ Raw Stall Optimization, at this point, causes corruption. *
* Calling wa_masked_dis with the arguments wal, CACHE_MODE_0_GEN7,
* HIZ_RAW_STALL_OPT_DISABLE will cause an HiZ corruption on ivb:g1. */

/*
* Should fallback to uncompressed if we increase size
* (zstream->total_out > zstream->total_in) by returning -E2BIG? */

Quoted 1 line

-Chris

#5 lore raw

[Intel-gfx] ✗ Fi.CI.BUILD: failure for drm/i915: Remove unreachable code

In reply to Vinicius Tinti
== Series Details ==

== Series Details ==

Series: drm/i915: Remove unreachable code
URL : https://patchwork.freedesktop.org/series/86479/
State : failure

== Summary ==

Applying: drm/i915: Remove unreachable code
Using index info to reconstruct a base tree...
M drivers/gpu/drm/i915/gt/intel_workarounds.c
M drivers/gpu/drm/i915/i915_gpu_error.c
Falling back to patching base and 3-way merge...
Auto-merging drivers/gpu/drm/i915/i915_gpu_error.c
Auto-merging drivers/gpu/drm/i915/gt/intel_workarounds.c
CONFLICT (content): Merge conflict in drivers/gpu/drm/i915/gt/intel_workarounds.c
error: Failed to merge in the changes.
hint: Use 'git am --show-current-patch=diff' to see the failed patch Patch failed at 0001 drm/i915: Remove unreachable code
When you have resolved this problem, run "git am --continue".
If you prefer to skip this patch, run "git am --skip" instead.
To restore the original branch and stop patching, run "git am --abort".

_______________________________________________
Intel-gfx mailing list
[email protected]
https://lists.freedesktop.org/mailman/listinfo/intel-gfx