kernel/linux.git/drivers/gpu/drm/amd/amdgpu/amdgpu_ids.h, branch v6.1.168Linux kernel stable tree (mirror)https://git.radix-linux.su/kernel/linux.git/atom?h=v6.1.1682022-03-25T16:40:26+00:00drm/amdgpu: simplify VM update tracking a bit2022-03-25T16:40:26+00:00Christian Königchristian.koenig@amd.com2022-03-08T14:06:49+00:00urn:sha1:e997b82745a5b2419bc5b72735811d7162ac994a
Store the 64bit sequence directly. Makes it simpler to use and saves a bit
of fence reference counting overhead.
Signed-off-by: Christian König <christian.koenig@amd.com>
Acked-by: Felix Kuehling <Felix.Kuehling@amd.com>
Signed-off-by: Alex Deucher <alexander.deucher@amd.com>
drm, iommu: Change type of pasid to u322020-09-17T17:21:16+00:00Fenghua Yufenghua.yu@intel.com2020-09-15T16:30:05+00:00urn:sha1:c7b6bac9c72c5fcbd6e9e12545bd3022c7f21860
PASID is defined as a few different types in iommu including "int",
"u32", and "unsigned int". To be consistent and to match with uapi
definitions, define PASID and its variations (e.g. max PASID) as "u32".
"u32" is also shorter and a little more explicit than "unsigned int".
No PASID type change in uapi although it defines PASID as __u64 in
some places.
Suggested-by: Thomas Gleixner <tglx@linutronix.de>
Signed-off-by: Fenghua Yu <fenghua.yu@intel.com>
Signed-off-by: Borislav Petkov <bp@suse.de>
Reviewed-by: Tony Luck <tony.luck@intel.com>
Reviewed-by: Lu Baolu <baolu.lu@linux.intel.com>
Acked-by: Felix Kuehling <Felix.Kuehling@amd.com>
Acked-by: Joerg Roedel <jroedel@suse.de>
Link: https://lkml.kernel.org/r/1600187413-163670-2-git-send-email-fenghua.yu@intel.com
dma-buf: rename reservation_object to dma_resv2019-08-13T07:09:30+00:00Christian Königchristian.koenig@amd.com2019-08-11T08:06:32+00:00urn:sha1:52791eeec1d9f4a7e7fe08aaba0b1553149d93bc
Be more consistent with the naming of the other DMA-buf objects.
Signed-off-by: Christian König <christian.koenig@amd.com>
Reviewed-by: Chris Wilson <chris@chris-wilson.co.uk>
Link: https://patchwork.freedesktop.org/patch/323401/
drm/amdgpu: update the PASID mapping only on demand2018-02-19T19:20:18+00:00Christian Königchristian.koenig@amd.com2018-02-05T16:38:01+00:00urn: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: make VMID owner none atomic v22018-02-19T19:19:15+00:00Christian Königchristian.koenig@amd.com2018-01-31T10:17:56+00:00urn: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>
drm/amdgpu: add amdgpu_pasid_free_delayed v22018-02-19T19:17:45+00:00Christian Königchristian.koenig@amd.com2018-01-05T10:16:22+00:00urn:sha1:4b5f75504975b42377fa198b0672c9a52eb728e0
Free up a pasid after all fences signaled.
v2: also handle the case when we can't allocate a fence array.
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: separate VMID and PASID handling2017-12-27T16:33:52+00:00Christian Königchristian.koenig@amd.com2017-12-18T15:53:03+00:00urn:sha1:620f774f4687d86c420152309eefb0ef0fcc7e51
Move both into the new files amdgpu_ids.[ch]. No functional change.
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>