Intel-GFX Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Michael Cheng <michael.cheng@intel.com>
To: intel-gfx@lists.freedesktop.org
Cc: michael.cheng@intel.com, lucas.demarchi@intel.com,
	dri-devel@lists.freedesktop.org
Subject: [Intel-gfx] [PATCH v4 0/4] Use drm_clflush* instead of clflush
Date: Thu,  3 Feb 2022 12:03:59 -0800	[thread overview]
Message-ID: <20220203200403.378958-1-michael.cheng@intel.com> (raw)

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

Michael Cheng (4):
  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

 drivers/gpu/drm/i915/gem/i915_gem_execbuffer.c  |  8 +++-----
 drivers/gpu/drm/i915/gt/intel_engine.h          | 13 ++++---------
 .../drm/i915/gt/intel_execlists_submission.c    | 17 +++++------------
 3 files changed, 12 insertions(+), 26 deletions(-)

-- 
2.25.1


             reply	other threads:[~2022-02-03 20:04 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-03 20:03 Michael Cheng [this message]
2022-02-03 20:04 ` [Intel-gfx] [PATCH v4 1/4] drm/i915/gt: Re-work intel_write_status_page Michael Cheng
2022-02-03 20:04 ` [Intel-gfx] [PATCH v4 2/4] drm/i915/gt: Drop invalidate_csb_entries Michael Cheng
2022-02-03 20:04 ` [Intel-gfx] [PATCH v4 3/4] drm/i915/gt: Re-work reset_csb Michael Cheng
2022-02-03 20:04 ` [Intel-gfx] [PATCH v4 4/4] drm/i915/: Re-work clflush_write32 Michael Cheng
2022-02-03 20:23 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for Use drm_clflush* instead of clflush (rev3) Patchwork
2022-02-03 20:24 ` [Intel-gfx] ✗ Fi.CI.SPARSE: " Patchwork
2022-02-03 20:57 ` [Intel-gfx] ✓ Fi.CI.BAT: success " Patchwork
2022-02-03 22:17 ` [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=20220203200403.378958-1-michael.cheng@intel.com \
    --to=michael.cheng@intel.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=lucas.demarchi@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