On Fri, Dec 1, 2023 at 7:18 PM Friedrich Vock wrote:
>
> This improves latency if the GPU is already busy with other work.
> This is useful for VR compositors that submit highly latency-sensitive
> compositing work on high-priority compute queues while the GPU is busy
> rendering the next frame.
On 2023-12-08 18:59, Alex Deucher wrote:
> On Fri, Dec 8, 2023 at 12:27 PM Joshua Ashton wrote:
>>
>> I heard some musings about dmabuf deadline kernel work recently, but not
>> sure if any of that is applicable to AMD.
>
> I think something like a workload hint would be more useful. We did a
>
On Fri, Dec 8, 2023 at 1:37 PM Alex Deucher wrote:
> On Fri, Dec 8, 2023 at 12:27 PM Joshua Ashton wrote:
> >
> > FWIW, we are shipping this right now in SteamOS Preview channel
> > (probably going to Stable soon) and it seems to be working as expected
> > and fixing issues there in instances
On Fri, Dec 8, 2023 at 12:27 PM Joshua Ashton wrote:
>
> FWIW, we are shipping this right now in SteamOS Preview channel
> (probably going to Stable soon) and it seems to be working as expected
> and fixing issues there in instances we need to composite, compositor
> work we are forced to do
FWIW, we are shipping this right now in SteamOS Preview channel
(probably going to Stable soon) and it seems to be working as expected
and fixing issues there in instances we need to composite, compositor
work we are forced to do would take longer than the compositor redzone
to vblank.
On Fri, Dec 8, 2023 at 9:57 AM Christian König
wrote:
> Am 08.12.23 um 12:43 schrieb Friedrich Vock:
> > On 08.12.23 10:51, Christian König wrote:
> >> Well longer story short Alex and I have been digging up the
> >> documentation for this and as far as we can tell this isn't correct.
> > Huh. I
: December 8, 2023 09:38
To: Friedrich Vock ; amd-gfx@lists.freedesktop.org
Cc: Deucher, Alexander ; Olsak, Marek
Subject: Re: [PATCH] drm/amdgpu: Enable tunneling on high-priority compute
queues
Am 08.12.23 um 12:43 schrieb Friedrich Vock:
> On 08.12.23 10:51, Christian König wrote:
>> We
Am 08.12.23 um 12:43 schrieb Friedrich Vock:
On 08.12.23 10:51, Christian König wrote:
Well longer story short Alex and I have been digging up the
documentation for this and as far as we can tell this isn't correct.
Huh. I initially talked to Marek about this, adding him in Cc.
Yeah, from
It's correct according to our documentation.
Reviewed-by: Marek Olšák
Marek
On Fri, Dec 8, 2023 at 5:47 AM Christian König
wrote:
> Well longer story short Alex and I have been digging up the
> documentation for this and as far as we can tell this isn't correct.
>
> You need to do quite a
On 08.12.23 10:51, Christian König wrote:
Well longer story short Alex and I have been digging up the
documentation for this and as far as we can tell this isn't correct.
Huh. I initially talked to Marek about this, adding him in Cc.
You need to do quite a bit more before you can turn on this
Well longer story short Alex and I have been digging up the
documentation for this and as far as we can tell this isn't correct.
You need to do quite a bit more before you can turn on this feature.
What userspace side do you refer to?
Regards,
Christian.
Am 08.12.23 um 09:19 schrieb
Friendly ping on this one.
Userspace side got merged, so would be great to land this patch too :)
On 02.12.23 01:17, Friedrich Vock wrote:
This improves latency if the GPU is already busy with other work.
This is useful for VR compositors that submit highly latency-sensitive
compositing work on
Interesting!
Gamescope also uses a high priority dedicated compute queue.
I'll see if this improves things on Deck with FSR, and other (sad) times
we have to composite.
Have you looked at how things change with gpuvis at all by the way?
- Joshie ✨
On 12/2/23 00:17, Friedrich Vock wrote:
This improves latency if the GPU is already busy with other work.
This is useful for VR compositors that submit highly latency-sensitive
compositing work on high-priority compute queues while the GPU is busy
rendering the next frame.
Userspace merge request:
14 matches
Mail list logo
