Re: [Intel-gfx] [PATCH v2] drm/i915: Unwind HW init after GVT setup failure

2018-07-10 Thread Chris Wilson
Quoting Michał Winiarski (2018-07-10 16:44:05) > On Tue, Jul 10, 2018 at 03:38:21PM +0100, Chris Wilson wrote: > > Following intel_gvt_init() failure, we missed unwinding our setup > > leaving pointers dangling past the module unload. For our example, the > > pm_qos: > > > > [ 441.057615] top:

Re: [Intel-gfx] [PATCH v2] drm/i915: Unwind HW init after GVT setup failure

2018-07-10 Thread Michał Winiarski
On Tue, Jul 10, 2018 at 03:38:21PM +0100, Chris Wilson wrote: > Following intel_gvt_init() failure, we missed unwinding our setup > leaving pointers dangling past the module unload. For our example, the > pm_qos: > > [ 441.057615] top: 6b3baf1c, n: 54d8ef33, p: 97cdf1a2 >

Re: [Intel-gfx] [PATCH v2] drm/i915: Unwind HW init after GVT setup failure

2018-07-10 Thread Chris Wilson
Quoting Chris Wilson (2018-07-10 15:38:21) > Following intel_gvt_init() failure, we missed unwinding our setup > leaving pointers dangling past the module unload. For our example, the > pm_qos: > > [ 441.057615] top: 6b3baf1c, n: 54d8ef33, p: 97cdf1a2 >

[Intel-gfx] [PATCH v2] drm/i915: Unwind HW init after GVT setup failure

2018-07-10 Thread Chris Wilson
Following intel_gvt_init() failure, we missed unwinding our setup leaving pointers dangling past the module unload. For our example, the pm_qos: [ 441.057615] top: 6b3baf1c, n: 54d8ef33, p: 97cdf1a2 prev: 54d8ef33, n: 97cdf1a2, p: