From: "Christian König" <ckoenig.leichtzumerken-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: amd-gfx-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
Subject: [PATCH 1/4] drm/amdgpu: remove unused member
Date: Thu, 19 Apr 2018 11:29:50 +0200 [thread overview]
Message-ID: <20180419092953.2188-1-christian.koenig@amd.com> (raw)
This lock isn't used any more.
Signed-off-by: Christian König <christian.koenig@amd.com>
---
drivers/gpu/drm/amd/amdgpu/amdgpu_vm.h | 3 ---
1 file changed, 3 deletions(-)
diff --git a/drivers/gpu/drm/amd/amdgpu/amdgpu_vm.h b/drivers/gpu/drm/amd/amdgpu/amdgpu_vm.h
index 30f080364c97..aef897b93866 100644
--- a/drivers/gpu/drm/amd/amdgpu/amdgpu_vm.h
+++ b/drivers/gpu/drm/amd/amdgpu/amdgpu_vm.h
@@ -186,9 +186,6 @@ struct amdgpu_vm {
struct amdgpu_vm_pt root;
struct dma_fence *last_update;
- /* protecting freed */
- spinlock_t freed_lock;
-
/* Scheduler entity for page table updates */
struct drm_sched_entity entity;
--
2.14.1
_______________________________________________
amd-gfx mailing list
amd-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/amd-gfx
next reply other threads:[~2018-04-19 9:29 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-19 9:29 Christian König [this message]
[not found] ` <20180419092953.2188-1-christian.koenig-5C7GfCeVMHo@public.gmane.org>
2018-04-19 9:29 ` [PATCH 2/4] drm/amdgpu: rework VM state machine lock handling Christian König
2018-04-19 9:29 ` [PATCH 3/4] drm/amdgpu: further optimize amdgpu_vm_validate_pt_bos Christian König
[not found] ` <20180419092953.2188-3-christian.koenig-5C7GfCeVMHo@public.gmane.org>
2018-04-19 11:07 ` Christian König
2018-04-19 9:29 ` [PATCH 4/4] drm/amdgpu: further optimize amdgpu_vm_handle_moved Christian König
[not found] ` <20180419092953.2188-4-christian.koenig-5C7GfCeVMHo@public.gmane.org>
2018-04-20 3:07 ` zhoucm1
2018-04-20 2:49 ` [PATCH 1/4] drm/amdgpu: remove unused member zhoucm1
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=20180419092953.2188-1-christian.koenig@amd.com \
--to=ckoenig.leichtzumerken-re5jqeeqqe8avxtiumwx3w@public.gmane.org \
--cc=amd-gfx-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.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.