From: "Teres Alexis, Alan Previn" <alan.previn.teres.alexis@intel.com>
To: "dri-devel@lists.freedesktop.org"
<dri-devel@lists.freedesktop.org>,
"Brost, Matthew" <matthew.brost@intel.com>,
"intel-gfx@lists.freedesktop.org"
<intel-gfx@lists.freedesktop.org>
Cc: "De Marchi, Lucas" <lucas.demarchi@intel.com>
Subject: Re: [Intel-gfx] [PATCH] drm/i915: Drop stealing of bits from i915_sw_fence function pointer
Date: Thu, 11 Nov 2021 20:18:37 +0000 [thread overview]
Message-ID: <db127308f71debac7d2b8ce5cf790dd726b0630b.camel@intel.com> (raw)
In-Reply-To: <20210922154713.1109-1-matthew.brost@intel.com>
Hey Matt, apologies for the delay, went thru all the code, LGTM.
Reviewed-by: Alan Previn <alan.previn.teres.alexis@intel.com>
P.S. - As a side note, would be interesting to replay the original reason behind the overloading of the
func ptr bits to begin with... to see what the initial intention was.
...alan
On Wed, 2021-09-22 at 08:47 -0700, Matthew Brost wrote:
> Rather than stealing bits from i915_sw_fence function pointer use
> seperate fields for function pointer and flags. If using two different
> fields, the 4 byte alignment for the i915_sw_fence function pointer can
> also be dropped.
>
> v2:
> (CI)
> - Set new function field rather than flags in __i915_sw_fence_init
> v3:
> (Tvrtko)
> - Remove BUG_ON(!fence->flags) in reinit as that will now blow up
> - Only define fence->flags if CONFIG_DRM_I915_SW_FENCE_CHECK_DAG is
> defined
>
> Signed-off-by: Matthew Brost <matthew.brost@intel.com>
> Acked-by: Jani Nikula <jani.nikula@intel.com>
> ---
> drivers/gpu/drm/i915/display/intel_display.c | 2 +-
> drivers/gpu/drm/i915/gem/i915_gem_context.c | 2 +-
> drivers/gpu/drm/i915/i915_request.c | 4 +--
> drivers/gpu/drm/i915/i915_sw_fence.c | 28 +++++++++++--------
> drivers/gpu/drm/i915/i915_sw_fence.h | 23 +++++++--------
> drivers/gpu/drm/i915/i915_sw_fence_work.c | 2 +-
> .../gpu/drm/i915/selftests/i915_sw_fence.c | 2 +-
> drivers/gpu/drm/i915/selftests/lib_sw_fence.c | 8 +++---
> 8 files changed, 39 insertions(+), 32 deletions(-)
>
>
> --
> 2.32.0
>
next prev parent reply other threads:[~2021-11-11 20:18 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-22 15:47 [Intel-gfx] [PATCH] drm/i915: Drop stealing of bits from i915_sw_fence function pointer Matthew Brost
2021-09-22 17:21 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for drm/i915: Drop stealing of bits from i915_sw_fence function pointer (rev3) Patchwork
2021-09-22 17:50 ` [Intel-gfx] ✓ Fi.CI.BAT: success " Patchwork
2021-09-22 19:47 ` [Intel-gfx] ✗ Fi.CI.IGT: failure " Patchwork
2021-11-11 20:18 ` Teres Alexis, Alan Previn [this message]
-- strict thread matches above, loose matches on Subject: below --
2021-11-16 19:49 [Intel-gfx] [PATCH] drm/i915: Drop stealing of bits from i915_sw_fence function pointer Matthew Brost
2021-09-22 14:57 Matthew Brost
2021-09-22 15:21 ` Tvrtko Ursulin
2021-09-22 15:25 ` Tvrtko Ursulin
2021-09-22 15:40 ` Matthew Brost
2021-09-22 2:13 Matthew Brost
2021-09-22 11:12 ` Jani Nikula
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=db127308f71debac7d2b8ce5cf790dd726b0630b.camel@intel.com \
--to=alan.previn.teres.alexis@intel.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=lucas.demarchi@intel.com \
--cc=matthew.brost@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