From: Tvrtko Ursulin <tvrtko.ursulin@linux.intel.com>
To: Michael Cheng <michael.cheng@intel.com>, intel-gfx@lists.freedesktop.org
Cc: lucas.demarchi@intel.com, dri-devel@lists.freedesktop.org
Subject: Re: [Intel-gfx] [PATCH v5 0/5] Use drm_clflush* instead of clflush
Date: Mon, 7 Feb 2022 12:03:56 +0000 [thread overview]
Message-ID: <f245951e-6f6c-1eab-7cba-ccb774db1194@linux.intel.com> (raw)
In-Reply-To: <20220204163711.439403-1-michael.cheng@intel.com>
On 04/02/2022 16:37, Michael Cheng wrote:
> This patch series re-work a few i915 functions to use drm_clflush_virt_range
> instead of calling clflush or clflushopt directly. This will prevent errors
> when building for non-x86 architectures.
>
> v2: s/PAGE_SIZE/sizeof(value) for Re-work intel_write_status_page and added
> more patches to convert additional clflush/clflushopt to use drm_clflush*.
> (Michael Cheng)
>
> v3: Drop invalidate_csb_entries and directly invoke drm_clflush_virt_ran
>
> v4: Remove extra memory barriers
>
> v5: s/cache_clflush_range/drm_clflush_virt_range
Is anyone interested in this story noticing my open? I will repeat:
How about we add i915_clflush_virt_range as static inline and by doing
so avoid adding function calls to code paths which are impossible on Arm
builds? Case in point relocations, probably execlists backend as well.
Downside would be effectively duplicating drm_clfush_virt_range code.
But for me, (Also considering no other driver calls it so why it is
there? Should it be deleted?), that would be okay.
Regards,
Tvrtko
> Michael Cheng (5):
> drm/i915/gt: Re-work intel_write_status_page
> drm/i915/gt: Drop invalidate_csb_entries
> drm/i915/gt: Re-work reset_csb
> drm/i915/: Re-work clflush_write32
> drm/i915/gt: replace cache_clflush_range
>
> .../gpu/drm/i915/gem/i915_gem_execbuffer.c | 8 +++-----
> drivers/gpu/drm/i915/gt/gen8_ppgtt.c | 12 ++++++------
> drivers/gpu/drm/i915/gt/intel_engine.h | 13 ++++---------
> .../drm/i915/gt/intel_execlists_submission.c | 19 ++++++-------------
> drivers/gpu/drm/i915/gt/intel_gtt.c | 2 +-
> drivers/gpu/drm/i915/gt/intel_ppgtt.c | 2 +-
> .../gpu/drm/i915/gt/uc/intel_guc_submission.c | 2 +-
> 7 files changed, 22 insertions(+), 36 deletions(-)
>
next prev parent reply other threads:[~2022-02-07 12:04 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-04 16:37 [Intel-gfx] [PATCH v5 0/5] Use drm_clflush* instead of clflush Michael Cheng
2022-02-04 16:37 ` [Intel-gfx] [PATCH v5 1/5] drm/i915/gt: Re-work intel_write_status_page Michael Cheng
2022-02-04 16:37 ` [Intel-gfx] [PATCH v5 2/5] drm/i915/gt: Drop invalidate_csb_entries Michael Cheng
2022-02-07 11:57 ` Tvrtko Ursulin
2022-02-07 18:47 ` Michael Cheng
2022-02-04 16:37 ` [Intel-gfx] [PATCH v5 3/5] drm/i915/gt: Re-work reset_csb Michael Cheng
2022-02-04 16:37 ` [Intel-gfx] [PATCH v5 4/5] drm/i915/: Re-work clflush_write32 Michael Cheng
2022-02-04 16:37 ` [Intel-gfx] [PATCH v5 5/5] drm/i915/gt: replace cache_clflush_range Michael Cheng
2022-02-04 16:53 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for Use drm_clflush* instead of clflush (rev4) Patchwork
2022-02-04 16:55 ` [Intel-gfx] ✗ Fi.CI.SPARSE: " Patchwork
2022-02-04 17:27 ` [Intel-gfx] ✓ Fi.CI.BAT: success " Patchwork
2022-02-04 18:53 ` [Intel-gfx] ✗ Fi.CI.IGT: failure " Patchwork
2022-02-07 12:03 ` Tvrtko Ursulin [this message]
2022-02-07 12:44 ` [Intel-gfx] [PATCH v5 0/5] Use drm_clflush* instead of clflush Jani Nikula
2022-02-08 9:02 ` Tvrtko Ursulin
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=f245951e-6f6c-1eab-7cba-ccb774db1194@linux.intel.com \
--to=tvrtko.ursulin@linux.intel.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=lucas.demarchi@intel.com \
--cc=michael.cheng@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