public inbox for intel-gfx@lists.freedesktop.org
 help / color / mirror / Atom feed
From: Michael Cheng <michael.cheng@intel.com>
To: intel-gfx@lists.freedesktop.org
Cc: michael.cheng@intel.com, wayne.boyer@intel.com,
	lucas.demarchi@intel.com, chris@chris-wilson.co.uk,
	mika.kuoppala@intel.com
Subject: [Intel-gfx] [PATCH 0/2] Use drm_clflush* instead of clflush
Date: Thu, 27 Jan 2022 15:41:16 -0800	[thread overview]
Message-ID: <20220127234118.111015-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 directly. This will prevent errors when building
for non-x86 architectures.


Michael Cheng (2):
  drm/i915/gt: Re-work intel_write_status_page
  drm/i915/gt: Re-work invalidate_csb_entries

 drivers/gpu/drm/i915/gt/intel_engine.h              | 13 ++++---------
 .../gpu/drm/i915/gt/intel_execlists_submission.c    |  4 ++--
 2 files changed, 6 insertions(+), 11 deletions(-)

-- 
2.25.1


             reply	other threads:[~2022-01-27 23:41 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-27 23:41 Michael Cheng [this message]
2022-01-27 23:41 ` [Intel-gfx] [PATCH 1/2] drm/i915/gt: Re-work intel_write_status_page Michael Cheng
2022-01-28  9:50   ` Matthew Auld
2022-01-29  7:20   ` Bowman, Casey G
2022-01-27 23:41 ` [Intel-gfx] [PATCH 2/2] drm/i915/gt: Re-work invalidate_csb_entries Michael Cheng
2022-01-28 10:00   ` Matthew Auld
2022-01-28  1:41 ` [Intel-gfx] ✗ Fi.CI.SPARSE: warning for Use drm_clflush* instead of clflush Patchwork
2022-01-28  2:15 ` [Intel-gfx] ✗ Fi.CI.BAT: 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=20220127234118.111015-1-michael.cheng@intel.com \
    --to=michael.cheng@intel.com \
    --cc=chris@chris-wilson.co.uk \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=lucas.demarchi@intel.com \
    --cc=mika.kuoppala@intel.com \
    --cc=wayne.boyer@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