From: SRINIVASAN SHANMUGAM <srinivasan.shanmugam@amd.com>
To: Alex Deucher <alexander.deucher@amd.com>, amd-gfx@lists.freedesktop.org
Subject: Re: [PATCH 1/2] drm/amdgpu/gfx11: return early in preempt_ib()
Date: Tue, 27 Aug 2024 11:37:29 +0530 [thread overview]
Message-ID: <b6778f7e-5b40-409e-a37e-f8bd4e21e1bb@amd.com> (raw)
In-Reply-To: <20240815170030.2582607-1-alexander.deucher@amd.com>
On 8/15/2024 10:30 PM, Alex Deucher wrote:
> When MES is enabled KIQ is not available. Return an error
> when someone uses the debugfs preempt test interface in
> that case.
>
> Signed-off-by: Alex Deucher <alexander.deucher@amd.com>
> ---
> drivers/gpu/drm/amd/amdgpu/gfx_v11_0.c | 3 +++
> 1 file changed, 3 insertions(+)
>
> diff --git a/drivers/gpu/drm/amd/amdgpu/gfx_v11_0.c b/drivers/gpu/drm/amd/amdgpu/gfx_v11_0.c
> index 5685aee479df..5704ad25a49d 100644
> --- a/drivers/gpu/drm/amd/amdgpu/gfx_v11_0.c
> +++ b/drivers/gpu/drm/amd/amdgpu/gfx_v11_0.c
> @@ -5924,6 +5924,9 @@ static int gfx_v11_0_ring_preempt_ib(struct amdgpu_ring *ring)
> struct amdgpu_ring *kiq_ring = &kiq->ring;
> unsigned long flags;
>
> + if (adev->enable_mes)
> + return -EINVAL;
> +
> if (!kiq->pmf || !kiq->pmf->kiq_unmap_queues)
> return -EINVAL;
>
With MES feature enabled, based on allowing multiple command streams to
be executed concurrently on the GPU Vs KIQ that is used to send commands
to the GPU in a sequential manner, having both of them active at the
same time could lead to conflicts.
Therefore, when the MES is enabled, the KIQ becomes unavailable.
With this understanding, this series is:
Acked-by: Srinivasan Shanmugam <srinivasan.shanmugam@amd.com>
prev parent reply other threads:[~2024-08-27 6:07 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-15 17:00 [PATCH 1/2] drm/amdgpu/gfx11: return early in preempt_ib() Alex Deucher
2024-08-15 17:00 ` [PATCH 2/2] drm/amdgpu/gfx12: " Alex Deucher
2024-08-26 18:54 ` [PATCH 1/2] drm/amdgpu/gfx11: " Alex Deucher
2024-08-27 6:07 ` SRINIVASAN SHANMUGAM [this message]
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=b6778f7e-5b40-409e-a37e-f8bd4e21e1bb@amd.com \
--to=srinivasan.shanmugam@amd.com \
--cc=alexander.deucher@amd.com \
--cc=amd-gfx@lists.freedesktop.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox