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 2/2] drm/i915/gt: Re-work invalidate_csb_entries
Date: Thu, 27 Jan 2022 15:41:18 -0800 [thread overview]
Message-ID: <20220127234118.111015-3-michael.cheng@intel.com> (raw)
In-Reply-To: <20220127234118.111015-1-michael.cheng@intel.com>
Re-work invalidate_csb_entries to use drm_clflush_virt_range. This will
prevent compiler errors when building for non-x86 architectures.
Signed-off-by: Michael Cheng <michael.cheng@intel.com>
---
drivers/gpu/drm/i915/gt/intel_execlists_submission.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/drivers/gpu/drm/i915/gt/intel_execlists_submission.c b/drivers/gpu/drm/i915/gt/intel_execlists_submission.c
index 960a9aaf4f3a..90b5daf9433d 100644
--- a/drivers/gpu/drm/i915/gt/intel_execlists_submission.c
+++ b/drivers/gpu/drm/i915/gt/intel_execlists_submission.c
@@ -1647,8 +1647,8 @@ cancel_port_requests(struct intel_engine_execlists * const execlists,
static void invalidate_csb_entries(const u64 *first, const u64 *last)
{
- clflush((void *)first);
- clflush((void *)last);
+ drm_clflush_virt_range((void *)first, sizeof(*first));
+ drm_clflush_virt_range((void *)last, sizeof(*last));
}
/*
--
2.25.1
next prev parent 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 [Intel-gfx] [PATCH 0/2] Use drm_clflush* instead of clflush Michael Cheng
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 ` Michael Cheng [this message]
2022-01-28 10:00 ` [Intel-gfx] [PATCH 2/2] drm/i915/gt: Re-work invalidate_csb_entries 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-3-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