linux/drivers/gpu/drm/amd/amdgpu/amdgpu_ids.c, branch v4.20Mirror of https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/
https://git.shady.money/linux/atom?h=v4.202018-10-16T20:08:08Zdrm/amdgpu: Fix typo in amdgpu_vmid_mgr_init2018-10-16T20:08:08ZRex ZhuRex.Zhu@amd.com2018-10-12T14:26:11Zurn:sha1:3df27645395e8f79c0dc20a15cf1da61f376000d
fix a typo in for loop: i->j
Reviewed-by: Christian König <christian.koenig@amd.com>
Signed-off-by: Rex Zhu <Rex.Zhu@amd.com>
Signed-off-by: Alex Deucher <alexander.deucher@amd.com>
Cc: stable@vger.kernel.org
drm/amdgpu: remove duplicated codes2018-07-05T21:38:46ZFlora CuiFlora.Cui@amd.com2018-06-27T05:53:53Zurn:sha1:cc450654291bb40c2d67a04d7e2fb42bff7e162a
the fence_context and seqno is init in amdgpu_vm_manager_init() &
amdgpu_vmid_mgr_init(). remove the amdgpu_vmid_mgr_init() copy.
Signed-off-by: Flora Cui <Flora.Cui@amd.com>
Reviewed-by: Junwei Zhang <Jerry.Zhang@amd.com>
Reviewed-by: Chunming Zhou <david1.zhou@amd.com>
Signed-off-by: Alex Deucher <alexander.deucher@amd.com>
drm/amdgpu: update the PASID mapping only on demand2018-02-19T19:20:18ZChristian Königchristian.koenig@amd.com2018-02-05T16:38:01Zurn:sha1:b3cd285fa68d162a53c2eb4e23bc4fc1ab7d97f6
Updating the PASID is rather heavyweight and shouldn't be done all the
time.
Signed-off-by: Christian König <christian.koenig@amd.com>
Reviewed-by: Felix Kuehling <Felix.Kuehling@amd.com>
Signed-off-by: Alex Deucher <alexander.deucher@amd.com>
drm/amdgpu: Fix potential uninitialized use of 'idle' in amdgpu_ids.c2018-02-19T19:19:57ZHarry Wentlandharry.wentland@amd.com2018-02-09T17:15:45Zurn:sha1:ed024578e703da96c71339a73cf5c3ff4317dd9a
v2: Use NULL and reverse christmas tree ordering
Signed-off-by: Harry Wentland <harry.wentland@amd.com>
Reviewed-by: Alex Deucher <alexander.deucher@amd.com>
Signed-off-by: Alex Deucher <alexander.deucher@amd.com>
drm/amdgpu: cache the fence to wait for a VMID2018-02-19T19:19:18ZChristian Königchristian.koenig@amd.com2018-01-31T15:03:19Zurn:sha1:3af81440a9b02e2c6e244539ee567063c3d62292
Beneficial when a lot of processes are waiting for VMIDs.
Signed-off-by: Christian König <christian.koenig@amd.com>
Reviewed-by: Chunming Zhou <david1.zhou@amd.com>
Signed-off-by: Alex Deucher <alexander.deucher@amd.com>
drm/amdgpu: restructure amdgpu_vmid_grab2018-02-19T19:19:17ZChristian Königchristian.koenig@amd.com2018-01-31T13:24:45Zurn:sha1:58592a095c981a002137221205411f538b9f0fb9
Now that we have the different cases for grabbing a VMID in separate
functions, restructure the top level function to only have one place
where VMIDs are assigned to jobs.
Signed-off-by: Christian König <christian.koenig@amd.com>
Acked-by: Chunming Zhou <david1.zhou@amd.com>
Signed-off-by: Alex Deucher <alexander.deucher@amd.com>
drm/amdgpu: move reusing VMIDs into separate function2018-02-19T19:19:16ZChristian Königchristian.koenig@amd.com2018-01-31T12:35:25Zurn:sha1:25ddf75bb3aa5e1f47eb9c04f0d50bf37269702b
Let's try this once more.
Signed-off-by: Christian König <christian.koenig@amd.com>
Reviewed-by: Chunming Zhou <david1.zhou@amd.com>
Signed-off-by: Alex Deucher <alexander.deucher@amd.com>
drm/amdgpu: cleanup and simplify amdgpu_vmid_grab_reserved2018-02-19T19:19:16ZChristian Königchristian.koenig@amd.com2018-01-31T10:56:53Zurn:sha1:cb5372ace9a3eaf9c0f8cd950bf68c2f3ce1c511
Drop the "_locked" from the name, cleanup and simplify the logic a bit.
Add missing comments.
Signed-off-by: Christian König <christian.koenig@amd.com>
Reviewed-by: Chunming Zhou <david1.zhou@amd.com>
Signed-off-by: Alex Deucher <alexander.deucher@amd.com>
drm/amdgpu: stop checking GPU reset counter during VMID grab2018-02-19T19:19:15ZChristian Königchristian.koenig@amd.com2018-01-31T10:21:23Zurn:sha1:782dcfdfd9c1c30e0b8304915297cef665a9867c
We do this later on when we flush the VMID anyway.
Signed-off-by: Christian König <christian.koenig@amd.com>
Reviewed-by: Chunming Zhou <david1.zhou@amd.com>
Signed-off-by: Alex Deucher <alexander.deucher@amd.com>
drm/amdgpu: make VMID owner none atomic v22018-02-19T19:19:15ZChristian Königchristian.koenig@amd.com2018-01-31T10:17:56Zurn:sha1:102374488dd608a9dd3fda962b9bb725848f8c3b
The variable is protected by the VMID mutex anyway.
v2: grab the mutex while resetting the VMID as well
Signed-off-by: Christian König <christian.koenig@amd.com>
Reviewed-by: Chunming Zhou <david1.zhou@amd.com>
Signed-off-by: Alex Deucher <alexander.deucher@amd.com>