Linux kernel stable tree (mirror) https://git.radix-linux.su/kernel/linux.git/atom?h=v6.12.80 2024-08-16T18:27:50+00:00 2024-08-16T18:27:50+00:00 Victor Skvortsov victor.skvortsov@amd.com 2024-08-02T18:22:26+00:00 urn:sha1:19cff16559a4f2d763faf4f8392bf86d3a21b93c Stop waiting for the KIQ to return back when there is a reset pending. It's quite likely that the KIQ will never response. Signed-off-by: Koenig Christian <Christian.Koenig@amd.com> Suggested-by: Lazar Lijo <Lijo.Lazar@amd.com> Tested-by: Victor Skvortsov <victor.skvortsov@amd.com> Signed-off-by: Victor Skvortsov <victor.skvortsov@amd.com> Reviewed-by: Hawking Zhang <Hawking.Zhang@amd.com> Signed-off-by: Alex Deucher <alexander.deucher@amd.com> 2024-06-05T15:25:13+00:00 Eric Huang jinhuieric.huang@amd.com 2024-06-03T15:56:03+00:00 urn:sha1:2656e1ce783a90fa1aa0e11f2915d7c0442bf06f reset source or reset cause is very useful info for reset context, it will be used by events API. Suggested-by: Lijo Lazar <Lijo.Lazar@amd.com> Signed-off-by: Eric Huang <jinhuieric.huang@amd.com> Reviewed-by: Lijo Lazar <lijo.lazar@amd.com> Signed-off-by: Alex Deucher <alexander.deucher@amd.com> 2024-05-02T19:40:50+00:00 Yunxiang Li Yunxiang.Li@amd.com 2024-04-22T18:44:38+00:00 urn:sha1:25c01191c2555351922e5515b6b6d31357975031 There are other reset sources that pass NULL as the job pointer, such as amdgpu_amdkfd_reset_work. Therefore, using the job pointer to check if the FLR comes from the host does not work. Add a flag in reset_context to explicitly mark host triggered reset, and set this flag when we receive host reset notification. Signed-off-by: Yunxiang Li <Yunxiang.Li@amd.com> Reviewed-by: Emily Deng <Emily.Deng@amd.com> Reviewed-by: Zhigang Luo <zhigang.luo@amd.com> Signed-off-by: Alex Deucher <alexander.deucher@amd.com> 2024-04-19T03:46:45+00:00 Ahmad Rehman Ahmad.Rehman@amd.com 2024-04-16T18:29:15+00:00 urn:sha1:ea137071ada1591a05ce0366de350158bf8dd6c7 In passthrough environment, the driver triggers the mode-1 reset on reload. The reset causes the core dump collection which is delayed task and prevents driver from unloading until it is completed. Since we do not need to collect data on "reset on reload" case, we can skip core dump collection. v2: Use the same flag to avoid calling amdgpu_reset_reg_dumps as well. Signed-off-by: Ahmad Rehman <Ahmad.Rehman@amd.com> Reviewed-by: Lijo Lazar <lijo.lazar@amd.com> Signed-off-by: Alex Deucher <alexander.deucher@amd.com> 2024-03-22T19:51:48+00:00 Sunil Khatri sunil.khatri@amd.com 2024-03-20T19:23:35+00:00 urn:sha1:9022f01b9709331c485703e49b3a8b2633513a92 Refractor devcoredump code into new files since its functionality is expanded further and better to slit and devcoredump to have its own file. v2: Fix the build failure caught by arm compiler of implicit function declaration with #ifdef v3: squash in fix for implicit declaration error Cc: Ivan Lipski <ivan.lipski@amd.com> Acked-by: Christian König <christian.koenig@amd.com> Signed-off-by: Sunil Khatri <sunil.khatri@amd.com> Signed-off-by: Alex Deucher <alexander.deucher@amd.com> 2024-03-06T20:24:50+00:00 Sunil Khatri sunil.khatri@amd.com 2024-03-01T12:05:35+00:00 urn:sha1:5e592956cc36abd2e568245dcf12b36c85d9462d Add ring timeout related information in the amdgpu devcoredump file for debugging purposes. During the gpu recovery process the registered call is triggered and add the debug information in data file created by devcoredump framework under the directory /sys/class/devcoredump/devcdx/ Signed-off-by: Sunil Khatri <sunil.khatri@amd.com> Reviewed-by: Christian König <christian.koenig@amd.com> Signed-off-by: Alex Deucher <alexander.deucher@amd.com> 2024-01-18T20:42:20+00:00 Christian König christian.koenig@amd.com 2024-01-10T14:19:29+00:00 urn:sha1:087a3e13ec49358eda582176a50068d38d94080f Calling amdgpu_device_ip_resume_phase1() during shutdown leaves the HW in an active state and is an unbalanced use of the IP callbacks. Using the IP callbacks like this can lead to memory leaks, double free and imbalanced reference counters. Leaving the HW in an active state can lead to DMA accesses to memory now freed by the driver. Both is a complete no-go for driver unload so completely revert the workaround for now. This reverts commit f5c7e7797060255dbc8160734ccc5ad6183c5e04. Signed-off-by: Christian König <christian.koenig@amd.com> Acked-by: Alex Deucher <alexander.deucher@amd.com> Signed-off-by: Alex Deucher <alexander.deucher@amd.com> 2023-10-20T19:11:29+00:00 André Almeida andrealmeid@igalia.com 2023-09-15T16:44:53+00:00 urn:sha1:de009982c6aa8363b2bc8800fb0a13896d264853 Even if there's nothing currently parsing amdgpu's coredump files, if we eventually have such tools they will be glad to find a version field to properly read the file. Create a version number to be displayed on top of coredump file, to be incremented when the file format or content get changed. Signed-off-by: André Almeida <andrealmeid@igalia.com> Reviewed-by: Shashank Sharma <shashank.sharma@amd.com> Signed-off-by: Alex Deucher <alexander.deucher@amd.com> 2023-10-20T19:11:29+00:00 André Almeida andrealmeid@igalia.com 2023-09-15T14:44:16+00:00 urn:sha1:69619868d39bf364721db8d9d2429420704417a3 Giving that we use codedump just for device resets, move it's functions and structs to a more semantic file, the amdgpu_reset.{c, h}. Signed-off-by: André Almeida <andrealmeid@igalia.com> Signed-off-by: Shashank Sharma <shashank.sharma@amd.com> Reviewed-by: Shashank Sharma <shashank.sharma@amd.com> Signed-off-by: Alex Deucher <alexander.deucher@amd.com> 2023-08-30T18:57:54+00:00 Lijo Lazar lijo.lazar@amd.com 2023-08-05T09:57:01+00:00 urn:sha1:f8a499aed290667bd37011ad534c66320dc48257 Instead of maintaining a list per device, keep the reset handlers common per ASIC family. A pointer to the list of handlers is maintained in reset control. Signed-off-by: Lijo Lazar <lijo.lazar@amd.com> Reviewed-by: Le Ma <le.ma@amd.com> Reviewed-by: Asad Kamal <asad.kamal@amd.com> Tested-by: Asad Kamal <asad.kamal@amd.com> Signed-off-by: Alex Deucher <alexander.deucher@amd.com>