All of lore.kernel.org
 help / color / mirror / Atom feed
From: David Rosca <david.rosca@amd.com>
To: Alex Deucher <alexdeucher@gmail.com>
Cc: amd-gfx@lists.freedesktop.org
Subject: Re: [PATCH] drm/amdgpu: Fix VCE 3 ring align_mask
Date: Thu, 20 Aug 2026 17:53:57 +0200	[thread overview]
Message-ID: <880c1dfa-5422-4fa2-88b5-c4c1fbe06add@amd.com> (raw)
In-Reply-To: <CADnq5_M+r+Sr3GXRr9O_jqu9zcVYRuihVfczpU1PwFoO1vw7AA@mail.gmail.com>


On 8/20/26 17:05, Alex Deucher wrote:
> On Thu, Aug 20, 2026 at 11:01 AM David Rosca <david.rosca@amd.com> wrote:
>> The largest frame is 20 dwords, so 0xf mask is too small.
>> This was always wrong, but we were lucky with the VCE_CMD_END
>> commands inserted after fence and vm_flush.
>>
>> Fixes: 7591335141a0 ("drm/amdgpu: Implement insert_end for VCE 3")
>> Signed-off-by: David Rosca <david.rosca@amd.com>
> Do any other VCE versions need their masks fixed?

No, only VCE 3 was wrong.

David

>
> Acked-by: Alex Deucher <alexander.deucher@amd.com>
>
>> ---
>>   drivers/gpu/drm/amd/amdgpu/vce_v3_0.c | 2 +-
>>   1 file changed, 1 insertion(+), 1 deletion(-)
>>
>> diff --git a/drivers/gpu/drm/amd/amdgpu/vce_v3_0.c b/drivers/gpu/drm/amd/amdgpu/vce_v3_0.c
>> index 9809a23fa521..d5adccd3e689 100644
>> --- a/drivers/gpu/drm/amd/amdgpu/vce_v3_0.c
>> +++ b/drivers/gpu/drm/amd/amdgpu/vce_v3_0.c
>> @@ -890,7 +890,7 @@ static const struct amdgpu_ring_funcs vce_v3_0_ring_phys_funcs = {
>>
>>   static const struct amdgpu_ring_funcs vce_v3_0_ring_vm_funcs = {
>>          .type = AMDGPU_RING_TYPE_VCE,
>> -       .align_mask = 0xf,
>> +       .align_mask = 0x1f,
>>          .nop = VCE_CMD_NO_OP,
>>          .support_64bit_ptrs = false,
>>          .no_user_fence = true,
>> --
>> 2.43.0
>>

      reply	other threads:[~2026-08-20 15:54 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-20 14:47 [PATCH] drm/amdgpu: Fix VCE 3 ring align_mask David Rosca
2026-08-20 15:05 ` Alex Deucher
2026-08-20 15:53   ` David Rosca [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=880c1dfa-5422-4fa2-88b5-c4c1fbe06add@amd.com \
    --to=david.rosca@amd.com \
    --cc=alexdeucher@gmail.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 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.