From: "Thomas Hellström" <thomas.hellstrom@linux.intel.com>
To: Oak Zeng <oak.zeng@intel.com>, intel-xe@lists.freedesktop.org
Subject: Re: [PATCH] drm/xe: Reject BO eviction if BO is bound to current VM
Date: Sun, 12 Jan 2025 11:44:13 +0100 [thread overview]
Message-ID: <267564116c6bcfe8052b8821c0237d22854f0ae2.camel@linux.intel.com> (raw)
In-Reply-To: <20250110210137.3181576-1-oak.zeng@intel.com>
On Fri, 2025-01-10 at 16:01 -0500, Oak Zeng wrote:
> This is a follow up fix for
> https://patchwork.freedesktop.org/patch/msgid/20241203021929.1919730-1-oak.zeng@intel.com
> The overall goal is to fail vm_bind when there is memory pressure.
> See more
> details in the commit message of above patch. Abbove patch fixes the
> issue
> when user pass in a vm_id parameter during gem_create. If user
> doesn't pass
> in a vm_id during gem_create, above patch doesn't help.
>
> This patch further reject BO eviction (which could be triggered by bo
> validation)
> if BO is bound to the current VM. vm_bind could fail due to the
> eviction failure.
> The BO to VM reverse mapping structure is used to determine whether
> BO is bound
> to VM.
>
> v2:
> Move vm_bo definition from function scope to if(evict) clause
> (Thomas)
> Further constraint the condition by adding ctx->resv (Thomas)
> Add a short comment describe the change.
>
> Suggested-by: Thomas Hellström <thomas.hellstrom@linux.intel.com>
> Signed-off-by: Oak Zeng <oak.zeng@intel.com>
> ---
> drivers/gpu/drm/xe/xe_bo.c | 15 +++++++++++++++
> 1 file changed, 15 insertions(+)
>
> diff --git a/drivers/gpu/drm/xe/xe_bo.c b/drivers/gpu/drm/xe/xe_bo.c
> index 4a623a98d9f1f..b024c63d8d296 100644
> --- a/drivers/gpu/drm/xe/xe_bo.c
> +++ b/drivers/gpu/drm/xe/xe_bo.c
> @@ -713,6 +713,21 @@ static int xe_bo_move(struct ttm_buffer_object
> *ttm_bo, bool evict,
> goto out;
> }
>
> + /* Reject BO eviction if BO is bound to current VM. */
> + if (evict && ctx->resv) {
> + struct drm_gpuvm_bo *vm_bo;
> +
> + drm_gem_for_each_gpuvm_bo(vm_bo, &bo->ttm.base) {
> + struct xe_vm *vm = gpuvm_to_vm(vm_bo->vm);
> +
> + if (xe_vm_resv(vm) == ctx->resv &&
> + xe_vm_in_preempt_fence_mode(vm)) {
> + ret = -EBUSY;
> + goto out;
> + }
> + }
> + }
> +
> /*
> * Failed multi-hop where the old_mem is still marked as
> * TTM_PL_FLAG_TEMPORARY, should just be a dummy move.
Reviewed-by: Thomas Hellström <thomas.hellstrom@linux.intel.com>
next prev parent reply other threads:[~2025-01-12 10:44 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-10 21:01 [PATCH] drm/xe: Reject BO eviction if BO is bound to current VM Oak Zeng
2025-01-12 10:44 ` Thomas Hellström [this message]
2025-01-13 5:43 ` ✓ CI.Patch_applied: success for drm/xe: Reject BO eviction if BO is bound to current VM (rev3) Patchwork
2025-01-13 5:43 ` ✗ CI.checkpatch: warning " Patchwork
2025-01-13 5:45 ` ✓ CI.KUnit: success " Patchwork
2025-01-13 6:12 ` ✓ CI.Build: " Patchwork
2025-01-13 6:16 ` ✓ CI.Hooks: " Patchwork
2025-01-13 6:18 ` ✓ CI.checksparse: " Patchwork
2025-01-13 6:46 ` ✓ Xe.CI.BAT: " Patchwork
2025-01-13 20:48 ` ✗ Xe.CI.Full: failure " Patchwork
-- strict thread matches above, loose matches on Subject: below --
2024-12-17 23:13 [PATCH] drm/xe: Reject BO eviction if BO is bound to current VM Oak Zeng
2025-01-10 14:45 ` Thomas Hellström
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=267564116c6bcfe8052b8821c0237d22854f0ae2.camel@linux.intel.com \
--to=thomas.hellstrom@linux.intel.com \
--cc=intel-xe@lists.freedesktop.org \
--cc=oak.zeng@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