Re: [RFC v4 02/11] drm/amdgpu: Move scheduler init to after XGMI is ready

2022-03-04 Thread Christian König
Grodzovsky *Sent:* Thursday, February 24, 2022 11:24 AM *To:* Chen, JingWen ; Christian König ; dri-de...@lists.freedesktop.org ; amd-gfx@lists.freedesktop.org *Cc:* Liu, Monk ; Chen, Horace ; Lazar, Lijo ; Koenig, Christian ; dan...@ffwll.ch *Subject:* Re: [RFC v4 02/11] drm/amdgpu: Move

Re: [RFC v4 02/11] drm/amdgpu: Move scheduler init to after XGMI is ready

2022-03-03 Thread Chen, JingWen
;>>>>>> On 2/25/22 1:26 AM, Andrey Grodzovsky wrote: >>>>>>>> No problem if so but before I do, >>>>>>>> >>>>>>>> >>>>>>>> JingWen - why you think this patch is needed as a standalone no

Re: [RFC v4 02/11] drm/amdgpu: Move scheduler init to after XGMI is ready

2022-03-03 Thread Andrey Grodzovsky
.freedesktop.org *Cc:* Liu, Monk ; Chen, Horace ; Lazar, Lijo ; Koenig, Christian ; dan...@ffwll.ch *Subject:* Re: [RFC v4 02/11] drm/amdgpu: Move scheduler init to after XGMI is ready No because all the patch-set including this patch was landed into drm-misc-next and will reach amd-staging-

Re: [RFC v4 02/11] drm/amdgpu: Move scheduler init to after XGMI is ready

2022-03-02 Thread Andrey Grodzovsky
--- *From:* amd-gfx on behalf of Andrey Grodzovsky *Sent:* Thursday, February 24, 2022 11:24 AM *To:* Chen, JingWen ; Christian König ; dri-de...@lists.freedesktop.org ; amd-gfx@lists.freedesktop.org *Cc:* Liu, Monk ; Chen, Horace ; Lazar, Lijo ; Koenig, Christian ; dan...@ffwll.ch *Subject:* Re: [

Re: [RFC v4 02/11] drm/amdgpu: Move scheduler init to after XGMI is ready

2022-03-02 Thread Chen, JingWen
gt;>>> Andrey >>>>> >>>>> >>>>> On 2022-02-24 12:12, Deucher, Alexander wrote: >>>>>> [Public] >>>>>> >>>>>> >>>>>> If it applies cleanly, feel free to drop it in. I'll dro

Re: [RFC v4 02/11] drm/amdgpu: Move scheduler init to after XGMI is ready

2022-03-02 Thread Andrey Grodzovsky
From:* amd-gfx on behalf of Andrey Grodzovsky *Sent:* Thursday, February 24, 2022 11:24 AM *To:* Chen, JingWen ; Christian König ; dri-de...@lists.freedesktop.org ; amd-gfx@lists.freedesktop.org *Cc:* Liu, Monk ; Chen, Horace ; Lazar, Lijo ; Koenig, Christian ; dan...@ffwll.ch *Subject:*

Re: [RFC v4 02/11] drm/amdgpu: Move scheduler init to after XGMI is ready

2022-03-02 Thread JingWen Chen
'll drop those patches >>>> for drm-next since they are already in drm-misc. >>>> >>>> Alex >>>> >>>> >>>> *From:* amd-gfx on behalf of >>

Re: [RFC v4 02/11] drm/amdgpu: Move scheduler init to after XGMI is ready

2022-02-25 Thread Andrey Grodzovsky
hen, Horace ; Lazar, Lijo ; Koenig, Christian ; dan...@ffwll.ch *Subject:* Re: [RFC v4 02/11] drm/amdgpu: Move scheduler init to after XGMI is ready No because all the patch-set including this patch was landed into drm-misc-next and will reach amd-staging-drm-next on the next upstream rebase i guess. A

Re: [RFC v4 02/11] drm/amdgpu: Move scheduler init to after XGMI is ready

2022-02-24 Thread JingWen Chen
ndrey >> Grodzovsky >> *Sent:* Thursday, February 24, 2022 11:24 AM >> *To:* Chen, JingWen ; Christian König >> ; dri-de...@lists.freedesktop.org >> ; amd-gfx@lists.freedesktop.org >> >> *Cc:* Liu, Monk ; Chen, Horace ; >> Lazar, Lijo ; Koenig

Re: [RFC v4 02/11] drm/amdgpu: Move scheduler init to after XGMI is ready

2022-02-24 Thread Andrey Grodzovsky
M *To:* Chen, JingWen ; Christian König ; dri-de...@lists.freedesktop.org ; amd-gfx@lists.freedesktop.org *Cc:* Liu, Monk ; Chen, Horace ; Lazar, Lijo ; Koenig, Christian ; dan...@ffwll.ch *Subject:* Re: [RFC v4 02/11] drm/amdgpu: Move scheduler init to after XGMI is ready No because all the

Re: [RFC v4 02/11] drm/amdgpu: Move scheduler init to after XGMI is ready

2022-02-24 Thread Deucher, Alexander
stian König ; dri-de...@lists.freedesktop.org ; amd-gfx@lists.freedesktop.org Cc: Liu, Monk ; Chen, Horace ; Lazar, Lijo ; Koenig, Christian ; dan...@ffwll.ch Subject: Re: [RFC v4 02/11] drm/amdgpu: Move scheduler init to after XGMI is ready No because all the patch-set including this patc

Re: [RFC v4 02/11] drm/amdgpu: Move scheduler init to after XGMI is ready

2022-02-24 Thread Andrey Grodzovsky
No because all the patch-set including this patch was landed into drm-misc-next and will reach amd-staging-drm-next on the next upstream rebase i guess. Andrey On 2022-02-24 01:47, JingWen Chen wrote: Hi Andrey, Will you port this patch into amd-staging-drm-next? on 2/10/22 2:06 AM, Andrey

Re: [RFC v4 02/11] drm/amdgpu: Move scheduler init to after XGMI is ready

2022-02-23 Thread JingWen Chen
Hi Andrey, Will you port this patch into amd-staging-drm-next? on 2/10/22 2:06 AM, Andrey Grodzovsky wrote: > All comments are fixed and code pushed. Thanks for everyone > who helped reviewing. > > Andrey > > On 2022-02-09 02:53, Christian König wrote: >> Am 09.02.22 um 01:23 schrieb Andrey Grodz

Re: [RFC v4 02/11] drm/amdgpu: Move scheduler init to after XGMI is ready

2022-02-09 Thread Andrey Grodzovsky
All comments are fixed and code pushed. Thanks for everyone who helped reviewing. Andrey On 2022-02-09 02:53, Christian König wrote: Am 09.02.22 um 01:23 schrieb Andrey Grodzovsky: Before we initialize schedulers we must know which reset domain are we in - for single device there iis a single

Re: [RFC v4 02/11] drm/amdgpu: Move scheduler init to after XGMI is ready

2022-02-08 Thread Christian König
Am 09.02.22 um 01:23 schrieb Andrey Grodzovsky: Before we initialize schedulers we must know which reset domain are we in - for single device there iis a single domain per device and so single wq per device. For XGMI the reset domain spans the entire XGMI hive and so the reset wq is per hive. Si

[RFC v4 02/11] drm/amdgpu: Move scheduler init to after XGMI is ready

2022-02-08 Thread Andrey Grodzovsky
Before we initialize schedulers we must know which reset domain are we in - for single device there iis a single domain per device and so single wq per device. For XGMI the reset domain spans the entire XGMI hive and so the reset wq is per hive. Signed-off-by: Andrey Grodzovsky --- drivers/gpu/d