drm/nouveau: Fix ttm move init with multiple GPUs
The pointer used to walk the table of move ops and pick the right one for the current GPU was declared static, meaning its state was carried over between invocations of the function, and also made the function non-rentrant and thread-unsafe. Since the table is ordered such that newer GPU methods are listed first, the result of this was that initializing newer GPUs after older GPUs would result in no suitable ttm move acceleration operations being found, and ttm would fall back to CPU blits on the older GPUs. This change declares the walking pointer separately from the table and makes it non-static to fix the logic. Signed-off-by: James Jones <jajones@nvidia.com> Signed-off-by: Ben Skeggs <bskeggs@redhat.com>
This commit is contained in:
parent
b4229fc67d
commit
72ecb0a6ce
|
@ -1162,7 +1162,7 @@ nouveau_bo_move_m2mf(struct ttm_buffer_object *bo, int evict, bool intr,
|
|||
void
|
||||
nouveau_bo_move_init(struct nouveau_drm *drm)
|
||||
{
|
||||
static const struct {
|
||||
static const struct _method_table {
|
||||
const char *name;
|
||||
int engine;
|
||||
s32 oclass;
|
||||
|
@ -1192,7 +1192,8 @@ nouveau_bo_move_init(struct nouveau_drm *drm)
|
|||
{ "M2MF", 0, 0x0039, nv04_bo_move_m2mf, nv04_bo_move_init },
|
||||
{},
|
||||
{ "CRYPT", 0, 0x88b4, nv98_bo_move_exec, nv50_bo_move_init },
|
||||
}, *mthd = _methods;
|
||||
};
|
||||
const struct _method_table *mthd = _methods;
|
||||
const char *name = "CPU";
|
||||
int ret;
|
||||
|
||||
|
|
Loading…
Reference in New Issue