| Commit message (Collapse) | Author | Age | Files | Lines | |
|---|---|---|---|---|---|
| * | drm/vmwgfx: Make the object handles idr-generated | Thomas Hellstrom | 2018-09-27 | 1 | -1/+1 |
| | | | | | | | | | | | | | | | | Instead of generating user-space object handles based on a, possibly processed, hash of the kernel address of the object, use idr to generate and lookup those handles. This might improve somewhat on security since we loose all connections to the object's kernel address. Also idr is designed to do just this. As a todo-item, since user-space handles are now generated in sequence, we can probably use a much simpler hash function to hash them. Signed-off-by: Thomas Hellstrom <thellstrom@vmware.com> Reviewed-by: Sinclair Yeh <syeh@vmware.com> Reviewed-by: Deepak Rawat <drawat@vmware.com> | ||||
| * | drm/ttm, drm/vmwgfx: Move the lock- and object functionality to the vmwgfx ↵ | Thomas Hellstrom | 2018-09-27 | 1 | -0/+294 |
| driver No other driver is using this functionality so move it out of TTM and into the vmwgfx driver. Update includes and remove exports. Also annotate to remove false static analyzer lock balance warnings. Signed-off-by: Thomas Hellstrom <thellstrom@vmware.com> Reviewed-by: Christian König <christian.koenig@amd.com> | |||||
 |
index : talos-obmc-linux | |
| Talos™ II Linux sources for OpenBMC | Raptor Computing Systems |
| summaryrefslogtreecommitdiffstats |
|