Open Bug 1708023 Opened 3 years ago Updated 4 days ago

Use IO Surfaces for WebGPU presentation on macOS

Categories

(Core :: Graphics: WebGPU, enhancement, P5)

All
macOS
enhancement

Tracking

()

People

(Reporter: kvark, Assigned: sotaro)

References

(Blocks 3 open bugs)

Details

Attachments

(2 files, 2 obsolete files)

See RenderMacIOSurfaceTextureHost

This should allow us to avoid CPU readback of frames.

Blocks: webgpu-v1

AIUI, we've de-scoped Mac support for webgpu-v1 for now. I don't know how to tweak the dependency graph right now, since I'm getting some validation errors, but I think this needs to be broken out from the webgpu-v1 milestone for now.

Severity: -- → S3
Priority: -- → P3
Blocks: webgpu-phase-2
No longer blocks: webgpu-v1
Summary: Use IO Surfaces for WebGPU presentation on maCOS → Use IO Surfaces for WebGPU presentation on macOS
No longer depends on: webgpu-cts-macos

In chromium, mac iosurface related to WebGPU is handled by the followings.

It seems that third_party\rust\metal does not have enough api binding for mac iosurface.

Blocks: 1886808
Assignee: nobody → sotaro.ikeda.g
No longer blocks: 1886808
Priority: P3 → P5

Current idea on macos.

wgpu/WebGPU in gecko does not handle Mac IOSurface nor MTLSharedEvent. Their handling needs to be added.

Attachment #9399290 - Attachment is obsolete: true
Attachment #9399539 - Attachment is obsolete: true
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: