From: Matthew Auld <matthew.auld@intel.com>
To: intel-gfx@lists.freedesktop.org
Cc: dri-devel@lists.freedesktop.org,
Maarten Lankhorst <maarten.lankhorst@linux.intel.com>
Subject: [Intel-gfx] [PATCH v2 09/10] drm/i915: Drain the ttm delayed workqueue too
Date: Fri, 29 Oct 2021 09:31:17 +0100 [thread overview]
Message-ID: <20211029083118.3386312-9-matthew.auld@intel.com> (raw)
In-Reply-To: <20211029083118.3386312-1-matthew.auld@intel.com>
From: Maarten Lankhorst <maarten.lankhorst@linux.intel.com>
Lets be thorough here. Users of the TTM backend would likely expect this
behaviour.
Signed-off-by: Maarten Lankhorst <maarten.lankhorst@linux.intel.com>
Reviewed-by: Matthew Auld <matthew.auld@intel.com>
Signed-off-by: Matthew Auld <matthew.auld@intel.com>
---
drivers/gpu/drm/i915/i915_drv.h | 1 +
1 file changed, 1 insertion(+)
diff --git a/drivers/gpu/drm/i915/i915_drv.h b/drivers/gpu/drm/i915/i915_drv.h
index 57f2f8da931e..1dc30ee26771 100644
--- a/drivers/gpu/drm/i915/i915_drv.h
+++ b/drivers/gpu/drm/i915/i915_drv.h
@@ -1818,6 +1818,7 @@ static inline void i915_gem_drain_freed_objects(struct drm_i915_private *i915)
*/
while (atomic_read(&i915->mm.free_count)) {
flush_work(&i915->mm.free_work);
+ flush_delayed_work(&i915->bdev.wq);
rcu_barrier();
}
}
--
2.26.3
next prev parent reply other threads:[~2021-10-29 8:33 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-29 8:31 [Intel-gfx] [PATCH v2 01/10] drm/i915: Remove unused bits of i915_vma/active api Matthew Auld
2021-10-29 8:31 ` [Intel-gfx] [PATCH v2 02/10] drm/i915: Remove gen6_ppgtt_unpin_all Matthew Auld
2021-10-29 8:31 ` [Intel-gfx] [PATCH v2 03/10] drm/i915: Create a dummy object for gen6 ppgtt Matthew Auld
2021-10-29 8:31 ` [Intel-gfx] [PATCH v2 04/10] drm/i915: Create a full object for mock_ring, v2 Matthew Auld
2021-10-29 8:31 ` [Intel-gfx] [PATCH v2 05/10] drm/i915: vma is always backed by an object Matthew Auld
2021-10-29 8:31 ` [Intel-gfx] [PATCH v2 06/10] drm/i915/pm: Move CONTEXT_VALID_BIT check Matthew Auld
2021-10-29 8:31 ` [Intel-gfx] [PATCH v2 07/10] drm/i915: Remove resv from i915_vma Matthew Auld
2021-10-29 8:31 ` [Intel-gfx] [PATCH v2 08/10] drm/i915: Rework context handling in hugepages selftests Matthew Auld
2021-10-29 8:31 ` Matthew Auld [this message]
2021-10-29 8:31 ` [Intel-gfx] [PATCH v2 10/10] drm/i915: Require object lock when freeing pages during destruction Matthew Auld
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=20211029083118.3386312-9-matthew.auld@intel.com \
--to=matthew.auld@intel.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=maarten.lankhorst@linux.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