a55ea67117
GpuVideoDecodeAccelerator/Host runs IPCs between renderer and GPU processes, sharing a route with a specific CommandBufferStub/ProxyImpl. This is a bit tricky to do with Mojo because Media IPCs are a layer above GPU, and we therefore need CommandBuffer-associated interfaces that CommandBuffer doesn't know about. To facilitate this we introduce a generic BindMediaReceiver API on CommandBuffer which takes a mojo::GenericPendingAssociatedReceiver, i.e. an associated interface endpoint that can be of any type. We then introduce a GPU-side hook that the Media stack can use to handle such requests. The primordial associated interface introduced here is GpuAcceleratedVideoDecoderProvider, which in turn has a single IPC for binding a GpuAcceleratedVideoDecoder/Client pair, also associated with the CommandBuffer. This migration removes the last remaining legacy IPC messages used by the GPU process, so once this is landed we can altogether remove IPC Channel from GPU code. Bug: 1196476, 993189 Change-Id: Ife986434b3c10b5796ce995d837a37c29514af49 Test: manually tested with custom extension doing a hardware VP9 decode via pp::VideoDecoder Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2956897 Reviewed-by: Tom Sepez <tsepez@chromium.org> Reviewed-by: Avi Drissman <avi@chromium.org> Reviewed-by: Sean Topping <seantopping@chromium.org> Reviewed-by: Robert Sesek <rsesek@chromium.org> Reviewed-by: Sunny Sachanandani <sunnyps@chromium.org> Reviewed-by: Dan Sanders <sandersd@chromium.org> Commit-Queue: Ken Rockot <rockot@google.com> Cr-Commit-Position: refs/heads/master@{#893111}
Chromium
Chromium is an open-source browser project that aims to build a safer, faster, and more stable way for all users to experience the web.
The project's web site is https://www.chromium.org.
To check out the source code locally, don't use git clone! Instead,
follow the instructions on how to get the code.
Documentation in the source is rooted in docs/README.md.
Learn how to Get Around the Chromium Source Code Directory Structure .
For historical reasons, there are some small top level directories. Now the guidance is that new top level directories are for product (e.g. Chrome, Android WebView, Ash). Even if these products have multiple executables, the code should be in subdirectories of the product.
If you found a bug, please file it at https://crbug.com/new.