From: "Thomas Hellström" <thomas.hellstrom@linux.intel.com>
To: Maarten Lankhorst <maarten.lankhorst@linux.intel.com>,
intel-gfx@lists.freedesktop.org
Cc: matthew.auld@intel.com
Subject: Re: [Intel-gfx] [PATCH v4 03/12] drm/i915: Introduce a ww transaction helper
Date: Wed, 16 Jun 2021 13:21:43 +0200 [thread overview]
Message-ID: <3c3fdf45-a1d0-b0e5-75c5-8521240e80e8@linux.intel.com> (raw)
In-Reply-To: <4a250ff0-5584-9c55-9717-88fc15197c75@linux.intel.com>
On 6/16/21 1:00 PM, Maarten Lankhorst wrote:
> Op 15-06-2021 om 15:14 schreef Thomas Hellström:
>> Introduce a for_i915_gem_ww(){} utility to help make the code
>> around a ww transaction more readable.
>>
>> Signed-off-by: Thomas Hellström <thomas.hellstrom@linux.intel.com>
>> Reviewed-by: Matthew Auld <matthew.auld@intel.com>
>> ---
>> drivers/gpu/drm/i915/i915_gem_ww.h | 31 +++++++++++++++++++++++++++++-
>> 1 file changed, 30 insertions(+), 1 deletion(-)
>>
>> diff --git a/drivers/gpu/drm/i915/i915_gem_ww.h b/drivers/gpu/drm/i915/i915_gem_ww.h
>> index f2d8769e4118..f6b1a796667b 100644
>> --- a/drivers/gpu/drm/i915/i915_gem_ww.h
>> +++ b/drivers/gpu/drm/i915/i915_gem_ww.h
>> @@ -11,11 +11,40 @@ struct i915_gem_ww_ctx {
>> struct ww_acquire_ctx ctx;
>> struct list_head obj_list;
>> struct drm_i915_gem_object *contended;
>> - bool intr;
>> + unsigned short intr;
>> + unsigned short loop;
>> };
>>
>> void i915_gem_ww_ctx_init(struct i915_gem_ww_ctx *ctx, bool intr);
>> void i915_gem_ww_ctx_fini(struct i915_gem_ww_ctx *ctx);
>> int __must_check i915_gem_ww_ctx_backoff(struct i915_gem_ww_ctx *ctx);
>> void i915_gem_ww_unlock_single(struct drm_i915_gem_object *obj);
>> +
>> +/* Internal functions used by the inlines! Don't use. */
>> +static inline int __i915_gem_ww_fini(struct i915_gem_ww_ctx *ww, int err)
>> +{
>> + ww->loop = 0;
>> + if (err == -EDEADLK) {
>> + err = i915_gem_ww_ctx_backoff(ww);
>> + if (!err)
>> + ww->loop = 1;
>> + }
>> +
>> + if (!ww->loop)
>> + i915_gem_ww_ctx_fini(ww);
>> +
>> + return err;
>> +}
>> +
>> +static inline void
>> +__i915_gem_ww_init(struct i915_gem_ww_ctx *ww, bool intr)
>> +{
>> + i915_gem_ww_ctx_init(ww, intr);
>> + ww->loop = 1;
>> +}
>> +
>> +#define for_i915_gem_ww(_ww, _err, _intr) \
>> + for (__i915_gem_ww_init(_ww, _intr); (_ww)->loop; \
>> + _err = __i915_gem_ww_fini(_ww, _err))
>> +
>> #endif
> With some more macro abuse, we should be able to kill off ww->loop,
Killing off ww->loop in itself is a good thing, I think. But the below
is a bit hard to follow, I think, :/
> for (err = ({i915_gem_ww_ctx_init(ww, intr), -EDEADLK}); err == -EDEADLK; err = (err == -EDEADLK && !(err = i915_gem_ww_ctx_backoff(ww))) ? -EDEADLK : err)
Could we simply keep the inlines and use err=-EDEADLK as the loop
condition instead?
/Thomas
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2021-06-16 11:21 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-15 13:14 [Intel-gfx] [PATCH v4 00/12] i915 TTM sync accelerated migration and clear Thomas Hellström
2021-06-15 13:14 ` [Intel-gfx] [PATCH v4 01/12] drm/i915: Reference objects on the ww object list Thomas Hellström
2021-06-15 13:14 ` [Intel-gfx] [PATCH v4 02/12] drm/i915: Break out dma_resv ww locking utilities to separate files Thomas Hellström
2021-06-15 13:14 ` [Intel-gfx] [PATCH v4 03/12] drm/i915: Introduce a ww transaction helper Thomas Hellström
2021-06-16 11:00 ` Maarten Lankhorst
2021-06-16 11:21 ` Thomas Hellström [this message]
2021-06-15 13:14 ` [Intel-gfx] [PATCH v4 04/12] drm/i915/gt: Add an insert_entry for gen8_ppgtt Thomas Hellström
2021-06-15 13:14 ` [Intel-gfx] [PATCH v4 05/12] drm/i915/gt: Add a routine to iterate over the pagetables of a GTT Thomas Hellström
2021-06-15 13:14 ` [Intel-gfx] [PATCH v4 06/12] drm/i915/gt: Export the pinned context constructor and destructor Thomas Hellström
2021-06-15 13:14 ` [Intel-gfx] [PATCH v4 07/12] drm/i915/gt: Pipelined page migration Thomas Hellström
2021-06-15 13:14 ` [Intel-gfx] [PATCH v4 08/12] drm/i915/gt: Pipelined clear Thomas Hellström
2021-06-15 13:14 ` [Intel-gfx] [PATCH v4 09/12] drm/i915/gt: Setup a default migration context on the GT Thomas Hellström
2021-06-15 13:14 ` [Intel-gfx] [PATCH v4 10/12] drm/i915/ttm: accelerated move implementation Thomas Hellström
2021-06-15 13:14 ` [Intel-gfx] [PATCH v4 11/12] drm/i915/gem: Zap the client blt code Thomas Hellström
2021-06-15 13:14 ` [Intel-gfx] [PATCH v4 12/12] drm/i915/gem: Zap the i915_gem_object_blt code Thomas Hellström
2021-06-15 13:36 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for i915 TTM sync accelerated migration and clear (rev3) Patchwork
2021-06-15 14:05 ` [Intel-gfx] ✓ Fi.CI.BAT: success " Patchwork
2021-06-15 21:19 ` [Intel-gfx] ✗ Fi.CI.IGT: failure " Patchwork
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=3c3fdf45-a1d0-b0e5-75c5-8521240e80e8@linux.intel.com \
--to=thomas.hellstrom@linux.intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=maarten.lankhorst@linux.intel.com \
--cc=matthew.auld@intel.com \
/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