Increasing the simbling array size to fix the warning of
array-index-out-of-bounds. The VCRAT_SIZE_FOR_GPU is also
increased accrordingly.
Signed-off-by: Ma Jun
---
drivers/gpu/drm/amd/amdkfd/kfd_crat.c | 2 +-
drivers/gpu/drm/amd/amdkfd/kfd_crat.h | 2 +-
2 files changed, 2 insertions(+), 2
[AMD Official Use Only - General]
Yes, thanks for helping explanation.
Regards,
Likun
-Original Message-
From: Zhu, Jiadong
Sent: Saturday, October 8, 2022 1:17 PM
To: Zhang, Hawking ; Gao, Likun ;
amd-gfx@lists.freedesktop.org
Cc: Grodzovsky, Andrey ; Michel Dänzer
; Tuikov, Luben
I think Likun means to stop creating sw ring if there is no gfx ring existed.
Thanks,
Jiadong
-Original Message-
From: Zhang, Hawking
Sent: Saturday, October 8, 2022 12:37 PM
To: Gao, Likun ; Zhu, Jiadong ;
amd-gfx@lists.freedesktop.org
Cc: Grodzovsky, Andrey ; Michel Dänzer
;
I agree, let me update the patch.
Thanks,
Jiadong
-Original Message-
From: Gao, Likun
Sent: Saturday, October 8, 2022 11:52 AM
To: Zhu, Jiadong ; amd-gfx@lists.freedesktop.org
Cc: Tuikov, Luben ; Michel Dänzer ;
Zhu, Jiadong ; Koenig, Christian
; Grodzovsky, Andrey
Subject: RE:
[AMD Official Use Only - General]
I don't think so. In such case, current cwsr and user queue mechanism handle
the pre-emption very well. The command submission actually bypass drm GPU
scheduler.
Regards,
Hawking
-Original Message-
From: amd-gfx On Behalf Of Gao, Likun
Sent:
[AMD Official Use Only - General]
Shall we need to deal with the situation that no real gfx ring exist?
(adev->gfx.num_gfx_rings is 0)
Regards,
Likun
-Original Message-
From: amd-gfx On Behalf Of
jiadong@amd.com
Sent: Thursday, September 29, 2022 5:07 PM
To:
[AMD Official Use Only - General]
Tested-by: Bokun, Zhang
This patch is better since it extracted the unset code and only execute it in
the SRIOV routine.
I have tested it with multi-VF.
Thanks!
-Original Message-
From: Alex Deucher
Sent: Thursday, October 6, 2022 3:56 PM
To:
tree/branch:
https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
branch HEAD: 082fce125e57cff60687181c97f3a8ee620c38f5 Add linux-next specific
files for 20221007
Error/Warning reports:
https://lore.kernel.org/linux-doc/202209201326.sy9kholm-...@intel.com
https
On 10/6/2022 16:26, Qingqing Zhuo wrote:
From: Alvin Lee
Watermark calculation was incorrect
due to missing brackets.
Reviewed-by: Rodrigo Siqueira
Acked-by: Qingqing Zhuo
Signed-off-by: Alvin Lee
This just landed upstream for 6.0 and is a trivial fix for what the
intention was, it
On 10/6/2022 16:26, Qingqing Zhuo wrote:
From: Nicholas Kazlauskas
[Why]
Request from PMFW to change the messaging format to specify whether we
support z-state via individual bits.
[How]
Update the args we pass in the support message.
Reviewed-by: Charlene Liu
Acked-by: Qingqing Zhuo
On Thu, Oct 6, 2022 at 1:50 PM Sudip Mukherjee
wrote:
>
> > And it looks like Sudip's proposed fix for this particular code is
> > additionally fixing unsigned vs signed as well. I think -Warray-bounds
> > did its job (though, with quite a confusing index range in the report).
>
> Not my.
On 10/6/2022 23:28, Shirish S wrote:
[Why]
If psr_feature_enable is set to true by default, it continues to be enabled
for non capable links.
[How]
explicitly disable the feature on links that are not capable of the same.
Signed-off-by: Shirish S
Reviewed-by: Leo Li
This has been a problem
On 2022-10-07 00:28, Shirish S wrote:
[Why]
If psr_feature_enable is set to true by default, it continues to be enabled
for non capable links.
[How]
explicitly disable the feature on links that are not capable of the same.
Signed-off-by: Shirish S
Reviewed-by: Leo Li
Thanks!
---
13 matches
Mail list logo
