[AMD Official Use Only - AMD Internal Distribution Only]
Nack to the revert. The FLR sequence is defined as the following
(host-initiated reset):
1) host sends FLR_NOTIFICATION
2) Guest gets interrupt and queues FLR work item
3) Guest sends READY_TO_RESET
4) Host sends
[AMD Official Use Only - General]
> -Original Message-
> From: amd-gfx On Behalf Of Lazar,
> Lijo
> Sent: Friday, March 15, 2024 6:47 AM
> To: Luo, Zhigang ; amd-gfx@lists.freedesktop.org
> Cc: Zhang, Hawking ; Saye, Sashank
> ; Chan, Hing Pong
> Subject: Re: [PATCH] drm/amdgpu: trigger
[AMD Official Use Only - General]
Acked-by: Victor Skvortsov
-Original Message-
From: Lazar, Lijo
Sent: Monday, June 19, 2023 3:30 AM
To: amd-gfx@lists.freedesktop.org
Cc: Zhang, Hawking ; Deucher, Alexander
; Kuehling, Felix ;
Skvortsov, Victor
Subject: [PATCH v2] drm/amdgpu
[AMD Official Use Only]
+Shaoyun
-Original Message-
From: Zhang, Bokun
Sent: Monday, February 14, 2022 4:09 PM
To: Skvortsov, Victor ; amd-gfx@lists.freedesktop.org
Cc: Skvortsov, Victor
Subject: RE: [PATCH] drm/amdgpu: Fix wait for RLCG command completion
[AMD Official Use Only
[AMD Official Use Only]
Reviewed-by: Victor Skvortsov
Thanks,
Victor
-Original Message-
From: Zhang, Hawking
Sent: Friday, February 11, 2022 1:42 AM
To: Chen, Guchun ; amd-gfx@lists.freedesktop.org; Zhou,
Peng Ju ; Koenig, Christian ;
Deucher, Alexander ; Skvortsov, Victor
[AMD Official Use Only]
Hi Guchun,
RLCG read is available on Aldebaran if amdgpu_sriov_reg_indirect_gc() flag is
set. Instead of adding a new function, I think we should simply add a check
inside amdgpu_virt_get_rlcg_reg_access_flag():
diff --git a/drivers/gpu/drm/amd/amdgpu/amdgpu_virt.c
[AMD Official Use Only]
+Shaoyun
-Original Message-
From: Chen, JingWen
Sent: Thursday, January 13, 2022 11:09 PM
To: amd-gfx@lists.freedesktop.org
Cc: Liu, Monk ; Chen, Horace ;
Skvortsov, Victor ; Chen, JingWen
Subject: [PATCH v3] drm/amd/amdgpu: fixing read wrong pf2vf data
-Original Message-
From: Alex Deucher
Sent: Thursday, December 16, 2021 3:18 PM
To: Skvortsov, Victor
Cc: amd-gfx list ; Deng, Emily
; Liu, Monk ; Ming, Davis
; Liu, Shaoyun ; Zhou, Peng Ju
; Chen, JingWen ; Chen, Horace
; Nieto, David M
Subject: Re: [PATCH v3 4/5] drm/amdgpu: get xgmi info
[AMD Official Use Only]
Gotcha, I will skip this patch for drm-next
-Original Message-
From: Alex Deucher
Sent: Thursday, December 16, 2021 8:53 AM
To: Skvortsov, Victor
Cc: amd-gfx list ; Deng, Emily
; Liu, Monk ; Ming, Davis
; Liu, Shaoyun ; Zhou, Peng Ju
; Chen, JingWen ; Chen
is kind of ugly. I don't know where
else to put it if we do need to call get_xgmi_info() in early_init.
Thanks,
Victor
-Original Message-
From: Alex Deucher
Sent: Wednesday, December 15, 2021 4:38 PM
To: Skvortsov, Victor
Cc: amd-gfx list ; Deng, Emily
; Liu, Monk ; Ming, Davis
; Liu
[AMD Official Use Only]
This was a bug in the original definition, but it functionally it makes no
difference (in both cases the macros resolve to the same value).
From: Nieto, David M
Sent: Wednesday, December 15, 2021 2:16 PM
To: Skvortsov, Victor ;
amd-gfx@lists.freedesktop.org; Deng
[AMD Official Use Only]
I wanted to keep the order the same as in amdgpu_device_lock_adev()
(Set flag then acquire lock) to prevent any weird race conditions.
Thanks,
Victor
-Original Message-
From: Liu, Shaoyun
Sent: Thursday, December 9, 2021 1:25 PM
To: Skvortsov, Victor ; amd-gfx
12 matches
Mail list logo
