From: Tvrtko Ursulin <tvrtko.ursulin@linux.intel.com>
To: Hong Liu <hong.liu@intel.com>, intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH] drm/i915: tidy up request alloc
Date: Thu, 30 Jun 2016 09:50:20 +0100 [thread overview]
Message-ID: <5774DD4C.6030702@linux.intel.com> (raw)
In-Reply-To: <1467250532-23644-1-git-send-email-hong.liu@intel.com>
On 30/06/16 02:35, Hong Liu wrote:
> Return the allocated request pointer directly to remove
> the double pointer parameter.
>
> Signed-off-by: Hong Liu <hong.liu@intel.com>
> ---
> drivers/gpu/drm/i915/i915_gem.c | 25 +++++++------------------
> 1 file changed, 7 insertions(+), 18 deletions(-)
>
> diff --git a/drivers/gpu/drm/i915/i915_gem.c b/drivers/gpu/drm/i915/i915_gem.c
> index 1d98782..9881455 100644
> --- a/drivers/gpu/drm/i915/i915_gem.c
> +++ b/drivers/gpu/drm/i915/i915_gem.c
> @@ -2988,32 +2988,26 @@ void i915_gem_request_free(struct kref *req_ref)
> kmem_cache_free(req->i915->requests, req);
> }
>
> -static inline int
> +static inline struct drm_i915_gem_request *
> __i915_gem_request_alloc(struct intel_engine_cs *engine,
> - struct i915_gem_context *ctx,
> - struct drm_i915_gem_request **req_out)
> + struct i915_gem_context *ctx)
> {
> struct drm_i915_private *dev_priv = engine->i915;
> unsigned reset_counter = i915_reset_counter(&dev_priv->gpu_error);
> struct drm_i915_gem_request *req;
> int ret;
>
> - if (!req_out)
> - return -EINVAL;
> -
> - *req_out = NULL;
> -
> /* ABI: Before userspace accesses the GPU (e.g. execbuffer), report
> * EIO if the GPU is already wedged, or EAGAIN to drop the struct_mutex
> * and restart.
> */
> ret = i915_gem_check_wedge(reset_counter, dev_priv->mm.interruptible);
> if (ret)
> - return ret;
> + return ERR_PTR(ret);
>
> req = kmem_cache_zalloc(dev_priv->requests, GFP_KERNEL);
> if (req == NULL)
> - return -ENOMEM;
> + return ERR_PTR(-ENOMEM);
>
> ret = i915_gem_get_seqno(engine->i915, &req->seqno);
> if (ret)
> @@ -3041,14 +3035,13 @@ __i915_gem_request_alloc(struct intel_engine_cs *engine,
> if (ret)
> goto err_ctx;
>
> - *req_out = req;
> - return 0;
> + return req;
>
> err_ctx:
> i915_gem_context_unreference(ctx);
> err:
> kmem_cache_free(dev_priv->requests, req);
> - return ret;
> + return ERR_PTR(ret);
> }
>
> /**
> @@ -3067,13 +3060,9 @@ struct drm_i915_gem_request *
> i915_gem_request_alloc(struct intel_engine_cs *engine,
> struct i915_gem_context *ctx)
> {
> - struct drm_i915_gem_request *req;
> - int err;
> -
> if (ctx == NULL)
> ctx = engine->i915->kernel_context;
> - err = __i915_gem_request_alloc(engine, ctx, &req);
> - return err ? ERR_PTR(err) : req;
> + return __i915_gem_request_alloc(engine, ctx);
> }
>
> struct drm_i915_gem_request *
>
Looks good to me. And have this feeling I've seen this somewhere before.
Reviewed-by: Tvrtko Ursulin <tvrtko.ursulin@intel.com>
Regards,
Tvrtko
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2016-06-30 8:50 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-30 1:35 [PATCH] drm/i915: tidy up request alloc Hong Liu
2016-06-30 5:43 ` ✓ Ro.CI.BAT: success for " Patchwork
2016-06-30 8:50 ` Tvrtko Ursulin [this message]
2016-06-30 10:22 ` [PATCH] " Chris Wilson
2016-06-30 12:49 ` Tvrtko Ursulin
2016-07-01 16:58 ` Dave Gordon
2016-07-01 18:34 ` Chris Wilson
2016-07-04 4:08 ` Liu, Hong
2016-07-04 10:36 ` Dave Gordon
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=5774DD4C.6030702@linux.intel.com \
--to=tvrtko.ursulin@linux.intel.com \
--cc=hong.liu@intel.com \
--cc=intel-gfx@lists.freedesktop.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox