From: "Christian König" <ckoenig.leichtzumerken@gmail.com>
To: chong li <chongli2@amd.com>, amd-gfx@lists.freedesktop.org
Cc: HaiJun.Chang@amd.com, Emily.Deng@amd.com,
Cursor <cursoragent@cursor.com>
Subject: Re: [PATCH 2/2] drm/amdgpu: improve the amdgpu device init progress in sriov mode
Date: Mon, 6 Jul 2026 13:39:28 +0200 [thread overview]
Message-ID: <6151568f-037e-4a2e-9a38-aa1ad692dba2@gmail.com> (raw)
In-Reply-To: <20260701055355.20478-2-chongli2@amd.com>
On 7/1/26 07:53, chong li wrote:
> Move the initialization of non-GPU resources
> out of the full GPU access region during AMDGPU device initialization
As far as I can see that won't work like this.
There are a lot of steps which require full GPU access.
What exactly is the justification of the change?
Regards,
Christian.
>
> Signed-off-by: chong li <chongli2@amd.com>
> Co-authored-by: Cursor <cursoragent@cursor.com>
> ---
> drivers/gpu/drm/amd/amdgpu/amdgpu_device.c | 10 ++++++----
> 1 file changed, 6 insertions(+), 4 deletions(-)
>
> diff --git a/drivers/gpu/drm/amd/amdgpu/amdgpu_device.c b/drivers/gpu/drm/amd/amdgpu/amdgpu_device.c
> index 610d82b79de3..c2ce4659ddc7 100644
> --- a/drivers/gpu/drm/amd/amdgpu/amdgpu_device.c
> +++ b/drivers/gpu/drm/amd/amdgpu/amdgpu_device.c
> @@ -1994,10 +1994,6 @@ static int amdgpu_device_ip_early_init(struct amdgpu_device *adev)
> amdgpu_device_enable_virtual_display(adev);
>
> if (amdgpu_sriov_vf(adev)) {
> - r = amdgpu_virt_request_full_gpu(adev, true);
> - if (r)
> - return r;
> -
> r = amdgpu_virt_init_critical_region(adev);
> if (r)
> return r;
> @@ -2159,6 +2155,12 @@ static int amdgpu_device_ip_early_init(struct amdgpu_device *adev)
> if (!total)
> return -ENODEV;
>
> + if (amdgpu_sriov_vf(adev)) {
> + r = amdgpu_virt_request_full_gpu(adev, true);
> + if (r)
> + return r;
> + }
> +
> if (adev->gmc.xgmi.supported)
> amdgpu_xgmi_early_init(adev);
>
next prev parent reply other threads:[~2026-07-06 11:39 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-01 5:53 [PATCH 1/2] drm/amdgpu: read FB through BAR0 when aperture is unavailable chong li
2026-07-01 5:53 ` [PATCH 2/2] drm/amdgpu: improve the amdgpu device init progress in sriov mode chong li
2026-07-06 11:39 ` Christian König [this message]
2026-07-06 11:36 ` [PATCH 1/2] drm/amdgpu: read FB through BAR0 when aperture is unavailable Christian König
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=6151568f-037e-4a2e-9a38-aa1ad692dba2@gmail.com \
--to=ckoenig.leichtzumerken@gmail.com \
--cc=Emily.Deng@amd.com \
--cc=HaiJun.Chang@amd.com \
--cc=amd-gfx@lists.freedesktop.org \
--cc=chongli2@amd.com \
--cc=cursoragent@cursor.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.