All of lore.kernel.org
 help / color / mirror / Atom feed
From: Friedrich Vock <friedrich.vock@gmx.de>
To: "Alex Deucher" <alexdeucher@gmail.com>,
	"Christian König" <christian.koenig@amd.com>
Cc: amd-gfx@lists.freedesktop.org, dri-devel@lists.freedesktop.org,
	"Sharma, Shashank" <Shashank.Sharma@amd.com>,
	Alex Deucher <Alexander.Deucher@amd.com>,
	Bas Nieuwenhuizen <bas@basnieuwenhuizen.nl>,
	Tatsuyuki Ishi <ishitatsuyuki@gmail.com>
Subject: Re: [PATCH v3 0/3] drm/amdgpu: Explicit sync for GEM VA operations
Date: Thu, 6 Feb 2025 18:33:28 +0100	[thread overview]
Message-ID: <49914965-e9ca-44ae-8bdf-6ea61a6b0b28@gmx.de> (raw)
In-Reply-To: <CADnq5_NC1ZxjCS8-cHsLTB_2DAeiMr_+LeRXwMtUQQ7MrrX_bg@mail.gmail.com>

On 04.02.25 14:58, Alex Deucher wrote:
> On Tue, Feb 4, 2025 at 8:37 AM Christian König <christian.koenig@amd.com> wrote:
>>
>> Hi Friedrich,
>>
>> adding Alex.
>>
>> Am 04.02.25 um 13:32 schrieb Friedrich Vock:
>>> Hi,
>>>

<snip>

>>>
>>> Bumping this again - it's been quite a while, what became of that KFD
>>> bugfix and the userqueue stuff? It'd be nice to finally make progress
>>> here, whether it's using the user queue interface you worked on or a
>>> re-spin of this. Maybe it's possible to split this off from the rest of
>>> the userqueue stuff and merge it beforehand if you're reasonably certain
>>> about how the uapi should look? Let me know.
>>
>> That is merged into amd-staging-drm-next for quite a while now, but we
>> only defined the interface and dropped all optimizations to initially
>> get it upstream.
>>
>> @Alex IIRC we pushed the KFD part upstream already, but the userqueue
>> part is still waiting for the final firmware release, right?
>
> Correct.

Right. Any rough timeline for when we can expect that firmware to release?

Thanks,
Friedrich

>
> Alex
>
>>
>> Regards,
>> Christian.
>>
>>>
>>> Thanks,
>>> Friedrich
>>>
>>>>
>>>> Regards,
>>>> Christian.
>>>>
>>>>>
>>>>> Userspace changes for this new version can be found at [1][2], and a
>>>>> kernel
>>>>> branch containing these patches can be found at [3].
>>>>>
>>>>> [1] https://gitlab.freedesktop.org/pixelcluster/drm/-/commits/vm-
>>>>> explicit-sync
>>>>> [2] https://gitlab.freedesktop.org/pixelcluster/mesa/-/commits/vm-
>>>>> explicit-sync
>>>>> [3] https://gitlab.freedesktop.org/pixelcluster/linux/-/commits/
>>>>> amdgpu-vm-explicit-sync
>>>>>
>>>>> v3 changes:
>>>>> - Rebased onto current amd-staging-drm-next
>>>>> - Added option to wait for drm_syncobjs instead of executing
>>>>> immediately
>>>>>
>>>>> Tatsuyuki Ishi (3):
>>>>>     drm/amdgpu: Don't implicit sync PRT maps.
>>>>>     drm/amdgpu: Add optional explicit sync fences for GEM operations.
>>>>>     drm/amdgpu: Bump amdgpu driver version.
>>>>>
>>>>>    .../gpu/drm/amd/amdgpu/amdgpu_amdkfd_gpuvm.c  |  2 +-
>>>>>    drivers/gpu/drm/amd/amdgpu/amdgpu_csa.c       |  2 +-
>>>>>    drivers/gpu/drm/amd/amdgpu/amdgpu_drv.c       |  3 +-
>>>>>    drivers/gpu/drm/amd/amdgpu/amdgpu_gem.c       | 76
>>>>> ++++++++++++++++---
>>>>>    drivers/gpu/drm/amd/amdgpu/amdgpu_object.h    | 23 +++++-
>>>>>    drivers/gpu/drm/amd/amdgpu/amdgpu_trace.h     |  6 +-
>>>>>    drivers/gpu/drm/amd/amdgpu/amdgpu_umsch_mm.c  |  2 +-
>>>>>    drivers/gpu/drm/amd/amdgpu/amdgpu_vm.c        | 68 +++++++++++------
>>>>>    drivers/gpu/drm/amd/amdgpu/amdgpu_vm.h        | 30 ++++----
>>>>>    drivers/gpu/drm/amd/amdgpu/amdgpu_vm_cpu.c    | 12 ++-
>>>>>    drivers/gpu/drm/amd/amdgpu/amdgpu_vm_pt.c     |  2 +-
>>>>>    drivers/gpu/drm/amd/amdgpu/amdgpu_vm_sdma.c   |  9 +++
>>>>>    drivers/gpu/drm/amd/amdkfd/kfd_svm.c          | 18 ++---
>>>>>    include/uapi/drm/amdgpu_drm.h                 |  7 ++
>>>>>    14 files changed, 194 insertions(+), 66 deletions(-)
>>>>>
>>>>> --
>>>>> 2.46.0
>>>>>
>>>
>>


      reply	other threads:[~2025-02-06 17:40 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-08-19  7:21 [PATCH v3 0/3] drm/amdgpu: Explicit sync for GEM VA operations Friedrich Vock
2024-08-19  7:21 ` [PATCH v3 1/3] drm/amdgpu: Don't implicit sync PRT maps Friedrich Vock
2024-08-19  7:21 ` [PATCH v3 2/3] drm/amdgpu: Add optional explicit sync fences for GEM operations Friedrich Vock
2024-08-19  7:21 ` [PATCH v3 3/3] drm/amdgpu: Bump amdgpu driver version Friedrich Vock
2024-08-19 11:21 ` [PATCH v3 0/3] drm/amdgpu: Explicit sync for GEM VA operations Christian König
2024-08-20 13:36   ` Sharma, Shashank
2025-02-04 12:32   ` Friedrich Vock
2025-02-04 13:36     ` Christian König
2025-02-04 13:58       ` Alex Deucher
2025-02-06 17:33         ` Friedrich Vock [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=49914965-e9ca-44ae-8bdf-6ea61a6b0b28@gmx.de \
    --to=friedrich.vock@gmx.de \
    --cc=Alexander.Deucher@amd.com \
    --cc=Shashank.Sharma@amd.com \
    --cc=alexdeucher@gmail.com \
    --cc=amd-gfx@lists.freedesktop.org \
    --cc=bas@basnieuwenhuizen.nl \
    --cc=christian.koenig@amd.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=ishitatsuyuki@gmail.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.