Re: [Intel-gfx] [PATCH] drm/i915/guc: Tidy ELSP port assignment

Quoting Chris Wilson (2017-11-24 12:29:16) > Since we know that the port is empty, we do not need to extract the > count from the old request it and copy it over to the new request, or > attempt to unref the NULL old request pointer. > > Signed-off-by: Chris Wilson >

Re: [Intel-gfx] [PATCH] drm/i915/guc: Tidy ELSP port assignment

Chris Wilson writes: > Since we know that the port is empty, we do not need to extract the > count from the old request it and copy it over to the new request, or on 'it' too many? > attempt to unref the NULL old request pointer. > > Signed-off-by: Chris Wilson

Re: [Intel-gfx] [PATCH] drm/i915/guc: Tidy ELSP port assignment

Quoting Michał Winiarski (2017-11-24 12:45:50) > On Fri, Nov 24, 2017 at 12:29:16PM +, Chris Wilson wrote: > > Since we know that the port is empty, we do not need to extract the > > count from the old request it and copy it over to the new request, or > > attempt to unref the NULL old request

Re: [Intel-gfx] [PATCH] drm/i915/guc: Tidy ELSP port assignment

On Fri, Nov 24, 2017 at 12:29:16PM +, Chris Wilson wrote: > Since we know that the port is empty, we do not need to extract the > count from the old request it and copy it over to the new request, or > attempt to unref the NULL old request pointer. > > Signed-off-by: Chris Wilson

[Intel-gfx] [PATCH] drm/i915/guc: Tidy ELSP port assignment

Since we know that the port is empty, we do not need to extract the count from the old request it and copy it over to the new request, or attempt to unref the NULL old request pointer. Signed-off-by: Chris Wilson Cc: Mika Kuoppala Cc: