All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Thomas Hellström" <thomas.hellstrom@linux.intel.com>
To: intel-xe@lists.freedesktop.org
Subject: [Intel-xe] [CI] drm/xe: Always flush TLB on rebind.
Date: Tue, 13 Jun 2023 12:19:09 +0200	[thread overview]
Message-ID: <20230613101909.10193-1-thomas.hellstrom@linux.intel.com> (raw)

Signed-off-by: Thomas Hellström <thomas.hellstrom@linux.intel.com>
---
 drivers/gpu/drm/xe/xe_pt.c | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/drivers/gpu/drm/xe/xe_pt.c b/drivers/gpu/drm/xe/xe_pt.c
index 2c472fafc811..e817fa9fe65e 100644
--- a/drivers/gpu/drm/xe/xe_pt.c
+++ b/drivers/gpu/drm/xe/xe_pt.c
@@ -1309,7 +1309,7 @@ __xe_pt_bind_vma(struct xe_tile *tile, struct xe_vma *vma, struct xe_engine *e,
 	 * non-faulting LR, in particular on user-space batch buffer chaining,
 	 * it needs to be done here.
 	 */
-	if ((rebind && !xe_vm_no_dma_fences(vm) && !vm->batch_invalidate_tlb) ||
+	if ((rebind && !xe_vm_no_dma_fences(vm)) ||
 	    (!rebind && vm->scratch_bo[tile->id] && xe_vm_in_compute_mode(vm))) {
 		ifence = kzalloc(sizeof(*ifence), GFP_KERNEL);
 		if (!ifence)
-- 
2.39.2


             reply	other threads:[~2023-06-13 10:20 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-13 10:19 Thomas Hellström [this message]
2023-06-13 11:09 ` [Intel-xe] ✓ CI.Patch_applied: success for drm/xe: Always flush TLB on rebind Patchwork
2023-06-13 11:10 ` [Intel-xe] ✗ CI.checkpatch: warning " Patchwork
2023-06-13 11:11 ` [Intel-xe] ✓ CI.KUnit: success " Patchwork
2023-06-13 11:15 ` [Intel-xe] ✓ CI.Build: " Patchwork
2023-06-13 11:15 ` [Intel-xe] ✓ CI.Hooks: " Patchwork
2023-06-13 11:16 ` [Intel-xe] ✓ CI.checksparse: " Patchwork
2023-06-13 12:01 ` [Intel-xe] ○ CI.BAT: info " 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=20230613101909.10193-1-thomas.hellstrom@linux.intel.com \
    --to=thomas.hellstrom@linux.intel.com \
    --cc=intel-xe@lists.freedesktop.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.