Skip to contentSkip to conversation

drm/i915: tidy up gen8_init_scratch

PATCH In review Matthew Auld 5 participants 5 messages Apr 26, 2016 – Apr 27, 2016

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

PATCH 1/1 drm/i915: tidy up gen8_init_scratch

Use goto teardown path and also ensure we reset any struct members which would otherwise contain an error encoded pointer, and could be mistaken for a valid address.

Cc Joonas Lahtinen <[email protected]>
---
 drivers/gpu/drm/i915/i915_gem_gtt.c | 36 +++++++++++++++++++++++++-----------
 1 file changed, 25 insertions(+), 11 deletions(-)
drivers/gpu/drm/i915/i915_gem_gtt.c +25 -11
index 0d666b3..a723b74 100644
@@ -866,31 +866,31 @@ static void gen8_free_page_tables(struct drm_device *dev,
 static int gen8_init_scratch(struct i915_address_space *vm)
 {
 	struct drm_device *dev = vm->dev;
+	int ret;
 
 	vm->scratch_page = alloc_scratch_page(dev);
-	if (IS_ERR(vm->scratch_page))
-		return PTR_ERR(vm->scratch_page);
+	if (IS_ERR(vm->scratch_page)) {
+		ret = PTR_ERR(vm->scratch_page);
+		goto fail_scratch;
+	}
 
 	vm->scratch_pt = alloc_pt(dev);
 	if (IS_ERR(vm->scratch_pt)) {
-		free_scratch_page(dev, vm->scratch_page);
-		return PTR_ERR(vm->scratch_pt);
+		ret = PTR_ERR(vm->scratch_pt);
+		goto fail_pt;
 	}
 
 	vm->scratch_pd = alloc_pd(dev);
 	if (IS_ERR(vm->scratch_pd)) {
-		free_pt(dev, vm->scratch_pt);
-		free_scratch_page(dev, vm->scratch_page);
-		return PTR_ERR(vm->scratch_pd);
+		ret = PTR_ERR(vm->scratch_pd);
+		goto fail_pd;
 	}
 
 	if (USES_FULL_48BIT_PPGTT(dev)) {
 		vm->scratch_pdp = alloc_pdp(dev);
 		if (IS_ERR(vm->scratch_pdp)) {
-			free_pd(dev, vm->scratch_pd);
-			free_pt(dev, vm->scratch_pt);
-			free_scratch_page(dev, vm->scratch_page);
-			return PTR_ERR(vm->scratch_pdp);
+			ret = PTR_ERR(vm->scratch_pdp);
+			goto fail_pdp;
 		}
 	}
 
@@ -900,6 +900,20 @@ static int gen8_init_scratch(struct i915_address_space *vm)
 		gen8_initialize_pdp(vm, vm->scratch_pdp);
 
 	return 0;
+
+fail_pdp:
+	vm->scratch_pdp = NULL;
+	free_pd(dev, vm->scratch_pd);
+fail_pd:
+	vm->scratch_pd = NULL;
+	free_pt(dev, vm->scratch_pt);
+fail_pt:
+	vm->scratch_pt = NULL;
+	free_scratch_page(dev, vm->scratch_page);
+fail_scratch:
+	vm->scratch_page = NULL;
+
+	return ret;
 }
 
 static int gen8_ppgtt_notify_vgt(struct i915_hw_ppgtt *ppgtt, bool create)
Signature · 6 lines
2.4.11

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

✗ Fi.CI.BAT: failure for drm/i915: tidy up gen8_init_scratch

== Series Details ==

== Series Details ==

Series: drm/i915: tidy up gen8_init_scratch
URL : https://patchwork.freedesktop.org/series/6315/
State : failure

== Summary ==

Series 6315v1 drm/i915: tidy up gen8_init_scratch
http://patchwork.freedesktop.org/api/1.0/series/6315/revisions/1/mbox/

Test kms_pipe_crc_basic:

        Subgroup hang-read-crc-pipe-b:
                pass       -> INCOMPLETE (snb-dellxps)
bdw-nuci7        total:200  pass:188  dwarn:0   dfail:0   fail:0   skip:12 
bdw-ultra        total:200  pass:175  dwarn:0   dfail:0   fail:0   skip:25 
bsw-nuc-2        total:199  pass:158  dwarn:0   dfail:0   fail:0   skip:41 
byt-nuc          total:199  pass:158  dwarn:0   dfail:0   fail:0   skip:41 
hsw-brixbox      total:200  pass:174  dwarn:0   dfail:0   fail:0   skip:26 
hsw-gt2          total:200  pass:178  dwarn:0   dfail:0   fail:1   skip:21 
ilk-hp8440p      total:200  pass:139  dwarn:0   dfail:0   fail:0   skip:61 
ivb-t430s        total:200  pass:169  dwarn:0   dfail:0   fail:0   skip:31 
skl-i7k-2        total:200  pass:173  dwarn:0   dfail:0   fail:0   skip:27 
skl-nuci5        total:200  pass:189  dwarn:0   dfail:0   fail:0   skip:11 
snb-dellxps      total:158  pass:118  dwarn:0   dfail:0   fail:0   skip:39 
snb-x220t        total:200  pass:158  dwarn:0   dfail:0   fail:1   skip:41 

Results at /archive/results/CI_IGT_test/Patchwork_2070/

9478b817812b1bf74a5e59f7d5f8220e0df20415 drm-intel-nightly: 2016y-04m-26d-11h-29m-24s UTC integration manifest b990c46 drm/i915: tidy up gen8_init_scratch

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

maintainer
#2 lore raw
In reply to Matthew Auld
Quoted 6 lines · Matthew Auld

Use goto teardown path and also ensure we reset any struct members which would otherwise contain an error encoded pointer, and could be mistaken for a valid address.

Cc Joonas Lahtinen <[email protected]>

As this goes through the whole function, good idea to check with git blame for the function author and CC (in this case Mika, added as CC).

Quoted 55 lines

---
 drivers/gpu/drm/i915/i915_gem_gtt.c | 36 +++++++++++++++++++++++++-----------

 1 file changed, 25 insertions(+), 11 deletions(-)
drivers/gpu/drm/i915/i915_gem_gtt.c +1 -0
index 0d666b3..a723b74 100644
@@ -866,31 +866,31 @@ static void gen8_free_page_tables(struct drm_device *dev,
  static int gen8_init_scratch(struct i915_address_space *vm)
  {
  	struct drm_device *dev = vm->dev;
+	int ret;


  vm->scratch_page = alloc_scratch_page(dev);

drivers/gpu/drm/i915/i915_gem_gtt.c +4 -2
-	if (IS_ERR(vm->scratch_page))
-		return PTR_ERR(vm->scratch_page);
+	if (IS_ERR(vm->scratch_page)) {
+		ret = PTR_ERR(vm->scratch_page);
+		goto fail_scratch;
+	}


  vm->scratch_pt = alloc_pt(dev);
  if (IS_ERR(vm->scratch_pt)) {

drivers/gpu/drm/i915/i915_gem_gtt.c +2 -2
-		free_scratch_page(dev, vm->scratch_page);
-		return PTR_ERR(vm->scratch_pt);
+		ret = PTR_ERR(vm->scratch_pt);
+		goto fail_pt;

  }

  vm->scratch_pd = alloc_pd(dev);
  if (IS_ERR(vm->scratch_pd)) {

drivers/gpu/drm/i915/i915_gem_gtt.c +2 -3
-		free_pt(dev, vm->scratch_pt);
-		free_scratch_page(dev, vm->scratch_page);
-		return PTR_ERR(vm->scratch_pd);
+		ret = PTR_ERR(vm->scratch_pd);
+		goto fail_pd;

  }

  if (USES_FULL_48BIT_PPGTT(dev)) {
  vm->scratch_pdp = alloc_pdp(dev);
  if (IS_ERR(vm->scratch_pdp)) {

drivers/gpu/drm/i915/i915_gem_gtt.c +2 -4
-			free_pd(dev, vm->scratch_pd);
-			free_pt(dev, vm->scratch_pt);
-			free_scratch_page(dev, vm->scratch_page);
-			return PTR_ERR(vm->scratch_pdp);
+			ret = PTR_ERR(vm->scratch_pdp);
+			goto fail_pdp;

  }
  }

drivers/gpu/drm/i915/i915_gem_gtt.c +0 -0
@@ -900,6 +900,20 @@ static int gen8_init_scratch(struct i915_address_space *vm)
  		gen8_initialize_pdp(vm, vm->scratch_pdp);


  return 0;

drivers/gpu/drm/i915/i915_gem_gtt.c static int gen8_init_scratch(struct i915_address_space *vm) · line 905

Quoted 3 lines
drivers/gpu/drm/i915/i915_gem_gtt.c +3 -0
+
+fail_pdp:
+	vm->scratch_pdp = NULL;

I don't think assigning to NULL is necessary. If this function fails, it'll lead to driver init failure.

drivers/gpu/drm/i915/i915_gem_gtt.c static int gen8_init_scratch(struct i915_address_space *vm) · line 915

Quoted 10 lines
drivers/gpu/drm/i915/i915_gem_gtt.c +10 -0
+	free_pd(dev, vm->scratch_pd);
+fail_pd:
+	vm->scratch_pd = NULL;
+	free_pt(dev, vm->scratch_pt);
+fail_pt:
+	vm->scratch_pt = NULL;
+	free_scratch_page(dev, vm->scratch_page);
+fail_scratch:
+	vm->scratch_page = NULL;
+

Same comment as in the last patch, related to labels, the label should describe the code under goto section, not the code/situation that jumps to it.

Regards, Joonas

Quoted 4 lines
drivers/gpu/drm/i915/i915_gem_gtt.c +1 -0
+	return ret;

 }

 static int gen8_ppgtt_notify_vgt(struct i915_hw_ppgtt *ppgtt, bool create)

Signature · 7 lines
Joonas Lahtinen
Open Source Technology Center
Intel Corporation
_______________________________________________
Intel-gfx mailing list
[email protected]
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
#3 lore raw
In reply to Matthew Auld
Quoted 68 lines · Matthew Auld

Use goto teardown path and also ensure we reset any struct members which would otherwise contain an error encoded pointer, and could be mistaken for a valid address.

Cc Joonas Lahtinen <[email protected]>
---
  drivers/gpu/drm/i915/i915_gem_gtt.c | 36 +++++++++++++++++++++++++-----------
  1 file changed, 25 insertions(+), 11 deletions(-)
drivers/gpu/drm/i915/i915_gem_gtt.c +18 -11
index 0d666b3..a723b74 100644
@@ -866,31 +866,31 @@ static void gen8_free_page_tables(struct drm_device *dev,
  static int gen8_init_scratch(struct i915_address_space *vm)
  {
  	struct drm_device *dev = vm->dev;
+	int ret;
 
  	vm->scratch_page = alloc_scratch_page(dev);
-	if (IS_ERR(vm->scratch_page))
-		return PTR_ERR(vm->scratch_page);
+	if (IS_ERR(vm->scratch_page)) {
+		ret = PTR_ERR(vm->scratch_page);
+		goto fail_scratch;
+	}
 
  	vm->scratch_pt = alloc_pt(dev);
  	if (IS_ERR(vm->scratch_pt)) {
-		free_scratch_page(dev, vm->scratch_page);
-		return PTR_ERR(vm->scratch_pt);
+		ret = PTR_ERR(vm->scratch_pt);
+		goto fail_pt;
  	}
 
  	vm->scratch_pd = alloc_pd(dev);
  	if (IS_ERR(vm->scratch_pd)) {
-		free_pt(dev, vm->scratch_pt);
-		free_scratch_page(dev, vm->scratch_page);
-		return PTR_ERR(vm->scratch_pd);
+		ret = PTR_ERR(vm->scratch_pd);
+		goto fail_pd;
  	}
 
  	if (USES_FULL_48BIT_PPGTT(dev)) {
  		vm->scratch_pdp = alloc_pdp(dev);
  		if (IS_ERR(vm->scratch_pdp)) {
-			free_pd(dev, vm->scratch_pd);
-			free_pt(dev, vm->scratch_pt);
-			free_scratch_page(dev, vm->scratch_page);
-			return PTR_ERR(vm->scratch_pdp);
+			ret = PTR_ERR(vm->scratch_pdp);
+			goto fail_pdp;
  		}
  	}
 
@@ -900,6 +900,20 @@ static int gen8_init_scratch(struct i915_address_space *vm)
  		gen8_initialize_pdp(vm, vm->scratch_pdp);
 
  	return 0;
+
+fail_pdp:
+	vm->scratch_pdp = NULL;
+	free_pd(dev, vm->scratch_pd);
+fail_pd:
+	vm->scratch_pd = NULL;
+	free_pt(dev, vm->scratch_pt);

drivers/gpu/drm/i915/i915_gem_gtt.c static int gen8_init_scratch(struct i915_address_space *vm) · line 919

Quoted 10 lines
drivers/gpu/drm/i915/i915_gem_gtt.c +7 -0
+fail_pt:
+	vm->scratch_pt = NULL;
+	free_scratch_page(dev, vm->scratch_page);
+fail_scratch:
+	vm->scratch_page = NULL;
+
+	return ret;
  }
 
  static int gen8_ppgtt_notify_vgt(struct i915_hw_ppgtt *ppgtt, bool create)

Well, I agree it's a good idea not to assign non-NULL pointer values to members of an OUT parameter, but perhaps consider a strategy of assigning to a local, checking the result, and storing in the parameter block only after we know that it's a good pointer. Maybe even keep ALL the temporary pointers local and only assign *any* of them when we know we can assign *all* of them and return success. That way there's no cleanup of the result block required in the error path, only freeing of still-local values.

BTW, as it appears that this function can be called more than once in the lifetime of the driver, do we know that all these pointers will be NULL on entry? Even on the second and subsequent calls?

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

#4 lore raw
Quoted 79 lines · Dave Gordon

[ text/plain ]

Quoted 77 lines · Matthew Auld

Use goto teardown path and also ensure we reset any struct members which would otherwise contain an error encoded pointer, and could be mistaken for a valid address.

Cc Joonas Lahtinen <[email protected]>
---
  drivers/gpu/drm/i915/i915_gem_gtt.c | 36 +++++++++++++++++++++++++-----------
  1 file changed, 25 insertions(+), 11 deletions(-)
drivers/gpu/drm/i915/i915_gem_gtt.c +25 -11
index 0d666b3..a723b74 100644
@@ -866,31 +866,31 @@ static void gen8_free_page_tables(struct drm_device *dev,
  static int gen8_init_scratch(struct i915_address_space *vm)
  {
  	struct drm_device *dev = vm->dev;
+	int ret;
 
  	vm->scratch_page = alloc_scratch_page(dev);
-	if (IS_ERR(vm->scratch_page))
-		return PTR_ERR(vm->scratch_page);
+	if (IS_ERR(vm->scratch_page)) {
+		ret = PTR_ERR(vm->scratch_page);
+		goto fail_scratch;
+	}
 
  	vm->scratch_pt = alloc_pt(dev);
  	if (IS_ERR(vm->scratch_pt)) {
-		free_scratch_page(dev, vm->scratch_page);
-		return PTR_ERR(vm->scratch_pt);
+		ret = PTR_ERR(vm->scratch_pt);
+		goto fail_pt;
  	}
 
  	vm->scratch_pd = alloc_pd(dev);
  	if (IS_ERR(vm->scratch_pd)) {
-		free_pt(dev, vm->scratch_pt);
-		free_scratch_page(dev, vm->scratch_page);
-		return PTR_ERR(vm->scratch_pd);
+		ret = PTR_ERR(vm->scratch_pd);
+		goto fail_pd;
  	}
 
  	if (USES_FULL_48BIT_PPGTT(dev)) {
  		vm->scratch_pdp = alloc_pdp(dev);
  		if (IS_ERR(vm->scratch_pdp)) {
-			free_pd(dev, vm->scratch_pd);
-			free_pt(dev, vm->scratch_pt);
-			free_scratch_page(dev, vm->scratch_page);
-			return PTR_ERR(vm->scratch_pdp);
+			ret = PTR_ERR(vm->scratch_pdp);
+			goto fail_pdp;
  		}
  	}
 
@@ -900,6 +900,20 @@ static int gen8_init_scratch(struct i915_address_space *vm)
  		gen8_initialize_pdp(vm, vm->scratch_pdp);
 
  	return 0;
+
+fail_pdp:
+	vm->scratch_pdp = NULL;
+	free_pd(dev, vm->scratch_pd);
+fail_pd:
+	vm->scratch_pd = NULL;
+	free_pt(dev, vm->scratch_pt);
+fail_pt:
+	vm->scratch_pt = NULL;
+	free_scratch_page(dev, vm->scratch_page);
+fail_scratch:
+	vm->scratch_page = NULL;
+
+	return ret;
  }
 
Quoted 10 lines

drivers/gpu/drm/i915/i915_gem_gtt.c static int gen8_init_scratch(struct i915_address_space *vm) · line 919

Quoted 1 line
drivers/gpu/drm/i915/i915_gem_gtt.c +0 -0
  static int gen8_ppgtt_notify_vgt(struct i915_hw_ppgtt *ppgtt, bool create)

Well, I agree it's a good idea not to assign non-NULL pointer values to members of an OUT parameter, but perhaps consider a strategy of assigning to a local, checking the result, and storing in the parameter block only after we know that it's a good pointer. Maybe even keep ALL the temporary pointers local and only assign *any* of them when we know we can assign *all* of them and return success. That way there's no cleanup of the result block required in the error path, only freeing of still-local values.

Local would be clean but then it would be burden on the hot path. Lets just incur the, now useless, writes on the error path.

Quoted 5 lines

BTW, as it appears that this function can be called more than once in the lifetime of the driver, do we know that all these pointers will be NULL on entry? Even on the second and subsequent calls?

The defensive programming of is good, but in this case we kzalloc the ppgtt, which contains the struct we are initializing. If we are unsuccessful, we free the ppgtt. And the function is static so there are no external users.

That said, the value of separating the error handling into a goto teardown is valuable for readability.

Change the goto labels as Joonas suggested and I am ok with this.

Thanks,
-Mika

-

Quoted 5 lines

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

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