Open Bug 1860735 Opened 1 year ago Updated 11 months ago

How to handle force_fallback_adapter with dx12

Categories

(Core :: Graphics: WebGPU, task, P2)

task

Tracking

()

People

(Reporter: sotaro, Unassigned, NeedInfo)

References

(Blocks 1 open bug)

Details

With dx12, same adapter needs to be used as WebRender. If wgpu uses a different adapter than WebRender, textures created by webgpu::ExternalTexture do not work with wgpu.

It seems that there are 2 choices
[1] ignore force_fallback_adapter
[2] disable webgpu::ExternalTexture usage.

If [2] is chosen, hardware decoded video frame handling by wgpu also going to have a problem.

Blocks: 1843891
Severity: -- → S3
Priority: -- → P2

:jimb, :nical, how force_fallback_adapter should be handled with dx12?

Flags: needinfo?(nical.bugzilla)
Flags: needinfo?(jimb)

I don't have all of the implications of this question in my head right now but I guess if we are using a fallback adapter (assuming in general that means a CPU emulated adapter), then we just don't use hardware textures when interoperating with it and always that readback/upload fallback path for data that goes it or comes out of webgpu.

Flags: needinfo?(nical.bugzilla)
You need to log in before you can comment on or make changes to this bug.