1 /**************************************************************************
3 * Copyright (c) 2007-2009 VMware, Inc., Palo Alto, CA., USA
6 * Permission is hereby granted, free of charge, to any person obtaining a
7 * copy of this software and associated documentation files (the
8 * "Software"), to deal in the Software without restriction, including
9 * without limitation the rights to use, copy, modify, merge, publish,
10 * distribute, sub license, and/or sell copies of the Software, and to
11 * permit persons to whom the Software is furnished to do so, subject to
12 * the following conditions:
14 * The above copyright notice and this permission notice (including the
15 * next paragraph) shall be included in all copies or substantial portions
18 * THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
19 * IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
20 * FITNESS FOR A PARTICULAR PURPOSE AND NON-INFRINGEMENT. IN NO EVENT SHALL
21 * THE COPYRIGHT HOLDERS, AUTHORS AND/OR ITS SUPPLIERS BE LIABLE FOR ANY CLAIM,
22 * DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR
23 * OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE
24 * USE OR OTHER DEALINGS IN THE SOFTWARE.
26 **************************************************************************/
28 * Authors: Thomas Hellstrom <thellstrom-at-vmware-dot-com>
32 * This file implements a simple replacement for the buffer manager use
33 * of the DRM heavyweight hardware lock.
34 * The lock is a read-write lock. Taking it in read mode and write mode
35 * is relatively fast, and intended for in-kernel use only.
37 * The vt mode is used only when there is a need to block all
38 * user-space processes from validating buffers.
39 * It's allowed to leave kernel space with the vt lock held.
40 * If a user-space process dies while having the vt-lock,
41 * it will be released during the file descriptor release. The vt lock
42 * excludes write lock and read lock.
44 * The suspend mode is used to lock out all TTM users when preparing for
45 * and executing suspend operations.
52 #include <linux/wait.h>
53 #include <linux/atomic.h>
55 #include "ttm_object.h"
60 * @base: ttm base object used solely to release the lock if the client
61 * holding the lock dies.
62 * @queue: Queue for processes waiting for lock change-of-status.
63 * @lock: Spinlock protecting some lock members.
64 * @rw: Read-write lock counter. Protected by @lock.
65 * @flags: Lock state. Protected by @lock.
66 * @kill_takers: Boolean whether to kill takers of the lock.
67 * @signal: Signal to send when kill_takers is true.
71 struct ttm_base_object base
;
72 wait_queue_head_t queue
;
78 struct ttm_object_file
*vt_holder
;
85 * @lock: Pointer to a struct ttm_lock
86 * Initializes the lock.
88 extern void ttm_lock_init(struct ttm_lock
*lock
);
93 * @lock: Pointer to a struct ttm_lock
95 * Releases a read lock.
97 extern void ttm_read_unlock(struct ttm_lock
*lock
);
102 * @lock: Pointer to a struct ttm_lock
103 * @interruptible: Interruptible sleeping while waiting for a lock.
105 * Takes the lock in read mode.
107 * -ERESTARTSYS If interrupted by a signal and interruptible is true.
109 extern int ttm_read_lock(struct ttm_lock
*lock
, bool interruptible
);
114 * @lock: Pointer to a struct ttm_lock
115 * @interruptible: Interruptible sleeping while waiting for a lock.
117 * Tries to take the lock in read mode. If the lock is already held
118 * in write mode, the function will return -EBUSY. If the lock is held
119 * in vt or suspend mode, the function will sleep until these modes
123 * -EBUSY The lock was already held in write mode.
124 * -ERESTARTSYS If interrupted by a signal and interruptible is true.
126 extern int ttm_read_trylock(struct ttm_lock
*lock
, bool interruptible
);
131 * @lock: Pointer to a struct ttm_lock
133 * Releases a write lock.
135 extern void ttm_write_unlock(struct ttm_lock
*lock
);
140 * @lock: Pointer to a struct ttm_lock
141 * @interruptible: Interruptible sleeping while waiting for a lock.
143 * Takes the lock in write mode.
145 * -ERESTARTSYS If interrupted by a signal and interruptible is true.
147 extern int ttm_write_lock(struct ttm_lock
*lock
, bool interruptible
);
152 * @lock: Pointer to a struct ttm_lock
154 * Downgrades a write lock to a read lock.
156 extern void ttm_lock_downgrade(struct ttm_lock
*lock
);
161 * @lock: Pointer to a struct ttm_lock
163 * Takes the lock in suspend mode. Excludes read and write mode.
165 extern void ttm_suspend_lock(struct ttm_lock
*lock
);
170 * @lock: Pointer to a struct ttm_lock
172 * Releases a suspend lock
174 extern void ttm_suspend_unlock(struct ttm_lock
*lock
);
179 * @lock: Pointer to a struct ttm_lock
180 * @interruptible: Interruptible sleeping while waiting for a lock.
181 * @tfile: Pointer to a struct ttm_object_file to register the lock with.
183 * Takes the lock in vt mode.
185 * -ERESTARTSYS If interrupted by a signal and interruptible is true.
186 * -ENOMEM: Out of memory when locking.
188 extern int ttm_vt_lock(struct ttm_lock
*lock
, bool interruptible
,
189 struct ttm_object_file
*tfile
);
194 * @lock: Pointer to a struct ttm_lock
196 * Releases a vt lock.
198 * -EINVAL If the lock was not held.
200 extern int ttm_vt_unlock(struct ttm_lock
*lock
);
205 * @lock: Pointer to a struct ttm_lock
207 * Releases a write lock.
209 extern void ttm_write_unlock(struct ttm_lock
*lock
);
214 * @lock: Pointer to a struct ttm_lock
215 * @interruptible: Interruptible sleeping while waiting for a lock.
217 * Takes the lock in write mode.
219 * -ERESTARTSYS If interrupted by a signal and interruptible is true.
221 extern int ttm_write_lock(struct ttm_lock
*lock
, bool interruptible
);
226 * @lock: Pointer to a struct ttm_lock
227 * @val: Boolean whether to kill processes taking the lock.
228 * @signal: Signal to send to the process taking the lock.
230 * The kill-when-taking-lock functionality is used to kill processes that keep
231 * on using the TTM functionality when its resources has been taken down, for
232 * example when the X server exits. A typical sequence would look like this:
233 * - X server takes lock in write mode.
234 * - ttm_lock_set_kill() is called with @val set to true.
235 * - As part of X server exit, TTM resources are taken down.
236 * - X server releases the lock on file release.
237 * - Another dri client wants to render, takes the lock and is killed.
240 static inline void ttm_lock_set_kill(struct ttm_lock
*lock
, bool val
,
243 lock
->kill_takers
= val
;
245 lock
->signal
= signal
;