[PATCH] drm/amd/pm: Enable ecc_info table support for smu v13_0_10

2023-02-28 Thread Candice Li
Support EccInfoTable which includes umc ras error count and error address. Signed-off-by: Candice Li Reviewed-by: Evan Quan --- .../drm/amd/pm/swsmu/smu13/smu_v13_0_0_ppt.c | 75 +++ 1 file changed, 75 insertions(+) diff --git

[PATCH] drm/amdgpu: Support umc node harvest config on umc v8_10

2023-02-28 Thread Candice Li
Don't need to query error count and error address on harvest umc nodes. v2: Fix code bug, use active_mask instead of harvsest_config and remove unnecessary argument in LOOP macro. v3: Leave adev->gmc.num_umc unchanged. Signed-off-by: Candice Li Reviewed-by: Tao Zhou ---

RE: [PATCH] drm/amdgpu: fix no previous prototype warning

2023-02-28 Thread Quan, Evan
[AMD Official Use Only - General] Please add proper tag as instructed. Other than this , the patch is Reviewed-by: Evan Quan "If you fix the issue, kindly add following tag where applicable | Reported-by: kernel test robot | Link:

Re: [PATCH] drm/amdgpu: Stop clearing kiq position during fini

2023-02-28 Thread Yin, ZhenGuo (Chris)
Acked-by: ZhenGuo Yin On 2/27/2023 2:45 PM, Yaoyao Lei wrote: Do not clear kiq position in RLC_CP_SCHEDULER so that CP could perform IDLE-SAVE after VF fini. Otherwise it could cause GFX hang if another Win guest is rendering. Signed-off-by: Yaoyao Lei ---

[PATCH] drm/amdgpu: fix no previous prototype warning

2023-02-28 Thread Kun Liu
add static prefix for vangogh_set_apu_thermal_limit function Signed-off-by: Kun Liu --- drivers/gpu/drm/amd/pm/swsmu/smu11/vangogh_ppt.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/drivers/gpu/drm/amd/pm/swsmu/smu11/vangogh_ppt.c

[PATCH] Revert "drm/amdgpu/display: change pipe policy for DCN 2.1"

2023-02-28 Thread Alex Deucher
This reverts commit fa458eb10dc7218146a84e6d2e072424e64d188a. The issue is no longer present even with this commit present as verified by the original reporter. Signed-off-by: Alex Deucher Link: https://gitlab.freedesktop.org/drm/amd/-/issues/1849#note_1759599 ---

Re: [PATCH 1/9] drm: execution context for GEM buffers v3

2023-02-28 Thread Danilo Krummrich
On 2/28/23 09:33, Christian König wrote: This adds the infrastructure for an execution context for GEM buffers which is similar to the existinc TTMs execbuf util and intended to replace "existing" it in the long term. The basic functionality is that we abstracts the necessary loop to lock

Re: Common DRM execution context v3

2023-02-28 Thread Danilo Krummrich
Hi Christian, On 2/28/23 09:33, Christian König wrote: Hi guys, thrid round for those patches. They have been in my queue for nearly a year now because I couldn't find much time to push into this. Danilo wants to use this for his GPU VAs tracker work and Arun needs it for hist secure

Re: [PATCH v2 1/1] drm/doc: Document DRM device reset expectations

2023-02-28 Thread Rob Clark
On Mon, Feb 27, 2023 at 12:40 PM André Almeida wrote: > > Create a section that specifies how to deal with DRM device resets for > kernel and userspace drivers. > > Signed-off-by: André Almeida > --- > Documentation/gpu/drm-uapi.rst | 51 ++ > 1 file changed, 51

Re: [PATCH 7/9] drm/radeon: switch over to drm_exec

2023-02-28 Thread kernel test robot
Hi Christian, I love your patch! Yet something to improve: [auto build test ERROR on drm-misc/drm-misc-next] [also build test ERROR on drm/drm-next drm-intel/for-linux-next linus/master next-20230228] [cannot apply to drm-exynos/exynos-drm-next drm-intel/for-linux-next-fixes v6.2] [If your

Re: [PATCH 8/9] drm/qxl: switch to using drm_exec

2023-02-28 Thread kernel test robot
Hi Christian, I love your patch! Yet something to improve: [auto build test ERROR on drm-misc/drm-misc-next] [also build test ERROR on drm/drm-next drm-intel/for-linux-next linus/master next-20230228] [cannot apply to drm-intel/for-linux-next-fixes v6.2] [If your patch is applied to the wrong

Re: [PATCH 8/9] drm/qxl: switch to using drm_exec

2023-02-28 Thread kernel test robot
Hi Christian, I love your patch! Yet something to improve: [auto build test ERROR on drm-misc/drm-misc-next] [also build test ERROR on drm/drm-next drm-intel/for-linux-next linus/master next-20230228] [cannot apply to drm-exynos/exynos-drm-next drm-intel/for-linux-next-fixes v6.2] [If your

Re: [PATCH v2 1/1] drm/doc: Document DRM device reset expectations

2023-02-28 Thread André Almeida
Hi Pekka, Thank you for your feedback, On 2/28/23 05:02, Pekka Paalanen wrote: On Mon, 27 Feb 2023 15:40:00 -0500 André Almeida wrote: Create a section that specifies how to deal with DRM device resets for kernel and userspace drivers. Signed-off-by: André Almeida ---

[linux-next:master] BUILD REGRESSION 058f4df42121baadbb8a980c06011e912784dbd2

2023-02-28 Thread kernel test robot
tree/branch: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master branch HEAD: 058f4df42121baadbb8a980c06011e912784dbd2 Add linux-next specific files for 20230228 Error/Warning reports: https://lore.kernel.org/oe-kbuild-all/202302111601.jty4lkra-...@intel.com https

Re: amdgpu didn't start with pci=nocrs parameter, get error "Fatal error during GPU init"

2023-02-28 Thread Christian König
Am 28.02.23 um 10:52 schrieb Mikhail Gavrilov: On Mon, Feb 27, 2023 at 3:22 PM Christian König Unfortunately yes. We could clean that up a bit more so that you don't run into a BUG() assertion, but what essentially happens here is that we completely fail to talk to the hardware. In this

Re: [PATCH v2 1/1] drm/doc: Document DRM device reset expectations

2023-02-28 Thread Pekka Paalanen
On Mon, 27 Feb 2023 15:40:00 -0500 André Almeida wrote: > Create a section that specifies how to deal with DRM device resets for > kernel and userspace drivers. > > Signed-off-by: André Almeida > --- > Documentation/gpu/drm-uapi.rst | 51 ++ > 1 file changed,

Re: amdgpu didn't start with pci=nocrs parameter, get error "Fatal error during GPU init"

2023-02-28 Thread Mikhail Gavrilov
On Mon, Feb 27, 2023 at 3:22 PM Christian König > > Unfortunately yes. We could clean that up a bit more so that you don't > run into a BUG() assertion, but what essentially happens here is that we > completely fail to talk to the hardware. > > In this situation we can't even re-enable vesa or

Re: [PATCH 2/6] drm/amdgpu: Implement a new userqueue fence driver

2023-02-28 Thread Arunpravin Paneer Selvam
Hi Christian, On 2/27/2023 6:12 PM, Christian König wrote: Am 26.02.23 um 17:54 schrieb Arunpravin Paneer Selvam: Developed a userqueue fence driver for the userqueue process shared BO synchronization. Create a dma fence having write pointer as the seqno and allocate a seq64 memory for each

[PATCH 5/9] drm/amdgpu: use drm_exec for MES testing

2023-02-28 Thread Christian König
Start using the new component here as well. Signed-off-by: Christian König --- drivers/gpu/drm/amd/amdgpu/amdgpu_mes.c | 86 +++-- 1 file changed, 39 insertions(+), 47 deletions(-) diff --git a/drivers/gpu/drm/amd/amdgpu/amdgpu_mes.c

[PATCH 9/9] drm: move ttm_execbuf_util into vmwgfx

2023-02-28 Thread Christian König
VMWGFX is the only remaining user of this and should probably moved over to drm_exec when it starts using GEM as well. Signed-off-by: Christian König --- drivers/gpu/drm/ttm/Makefile | 4 ++-- drivers/gpu/drm/vmwgfx/Makefile| 2 +-

[PATCH 7/9] drm/radeon: switch over to drm_exec

2023-02-28 Thread Christian König
Just a straightforward conversion without any optimization. Signed-off-by: Christian König --- drivers/gpu/drm/radeon/radeon.h| 7 ++-- drivers/gpu/drm/radeon/radeon_cs.c | 45 +- drivers/gpu/drm/radeon/radeon_gem.c| 40 +--

[PATCH 8/9] drm/qxl: switch to using drm_exec

2023-02-28 Thread Christian König
Just a straightforward conversion without any optimization. Only compile tested for now. Signed-off-by: Christian König --- drivers/gpu/drm/qxl/qxl_drv.h | 7 ++-- drivers/gpu/drm/qxl/qxl_release.c | 67 --- 2 files changed, 38 insertions(+), 36 deletions(-)

[PATCH 6/9] drm/amdgpu: use the new drm_exec object for CS v2

2023-02-28 Thread Christian König
Use the new component here as well and remove the old handling. v2: drop dupplicate handling Signed-off-by: Christian König --- drivers/gpu/drm/amd/amdgpu/amdgpu.h | 1 - drivers/gpu/drm/amd/amdgpu/amdgpu_bo_list.c | 71 ++- drivers/gpu/drm/amd/amdgpu/amdgpu_bo_list.h | 5 +-

[PATCH 3/9] drm/amdkfd: switch over to using drm_exec

2023-02-28 Thread Christian König
Avoids quite a bit of logic and kmalloc overhead. Signed-off-by: Christian König --- drivers/gpu/drm/amd/amdgpu/amdgpu_amdkfd.h| 5 +- .../gpu/drm/amd/amdgpu/amdgpu_amdkfd_gpuvm.c | 302 +++--- drivers/gpu/drm/amd/amdgpu/amdgpu_vm.c| 14 +

[PATCH 4/9] drm/amdgpu: use drm_exec for GEM and CSA handling

2023-02-28 Thread Christian König
Start using the new component here as well. Signed-off-by: Christian König --- drivers/gpu/drm/amd/amdgpu/amdgpu_csa.c | 42 ++ drivers/gpu/drm/amd/amdgpu/amdgpu_gem.c | 77 +++-- 2 files changed, 53 insertions(+), 66 deletions(-) diff --git

[PATCH 2/9] drm: add drm_exec selftests

2023-02-28 Thread Christian König
Largely just the initial skeleton. Signed-off-by: Christian König --- drivers/gpu/drm/Kconfig | 1 + drivers/gpu/drm/tests/Makefile| 3 +- drivers/gpu/drm/tests/drm_exec_test.c | 73 +++ 3 files changed, 76 insertions(+), 1 deletion(-) create

[PATCH 1/9] drm: execution context for GEM buffers v3

2023-02-28 Thread Christian König
This adds the infrastructure for an execution context for GEM buffers which is similar to the existinc TTMs execbuf util and intended to replace it in the long term. The basic functionality is that we abstracts the necessary loop to lock many different GEM buffers with automated deadlock and

Common DRM execution context v3

2023-02-28 Thread Christian König
Hi guys, thrid round for those patches. They have been in my queue for nearly a year now because I couldn't find much time to push into this. Danilo wants to use this for his GPU VAs tracker work and Arun needs it for hist secure semaphore work, so we should probably get it reviewed now.

Re: [PATCH v2 3/3] drm/amd: Add special handling for system s0ix state w/ dGPUs

2023-02-28 Thread Lazar, Lijo
On 2/28/2023 10:13 AM, Mario Limonciello wrote: With dGPUs that support BACO or BOCO we want them to go into those states when the system goes to s2idle. Detect that the system will be targeting this state and force the call into runtime suspend. If the runtime suspend call fails for any