Add VaapiVideoEncodeAccelerator for HW-accelerated video encode.

content/browser/renderer_host/render_process_host_impl.cc

 // Copyright (c) 2012 The Chromium Authors. All rights reserved.
 // Use of this source code is governed by a BSD-style license that can be
 // found in the LICENSE file.
 
 // Represents the browser side of the browser <--> renderer communication
 // channel. There will be one RenderProcessHost per renderer process.
 
 #include "content/browser/renderer_host/render_process_host_impl.h"
 
 #include <algorithm>
@@ skipping 1231 matching lines @@
     switches::kDisableWebAudio,
 #endif
 #if defined(OS_MACOSX)
     // Allow this to be set when invoking the browser and relayed along.
     switches::kEnableSandboxLogging,
 #endif
 #if defined(OS_WIN)
     switches::kDisableDirectWrite,
     switches::kEnableHighResolutionTime,
 #endif
+#if defined(OS_CHROMEOS)
+    switches::kEnableVaapiAcceleratedVideoEncode,
+#endif

[piman, 2014/06/20 17:10:22]

I don't see where this is used in the renderer.

[Pawel Osciak, 2014/06/20 22:28:11]

Yeah, this is a bit convoluted. We need a way to be able to tell which
codecs/profiles are supported by a hw encoder from the renderer on request from
libjingle, before we make a decision to instantiate the codec in GPU process.

The method used to retrieve the list of supported codecs is currently a hack, a
hardcoded in each accelerator VEA::GetSupportedProfiles, which is actually a
static method in HW accelerators executed in renderer from
RTCVideoEncoderFactory
(https://code.google.com/p/chromium/codesearch#chromium/src/content/renderer/m...)
and then used to decide if we would be able to fulfill webrtc's request for a HW
codec that would support given profile
(https://code.google.com/p/chromium/codesearch#chromium/src/content/renderer/m...).

We are working on a proper solution for this (crbug.com/350197) which will add
codec feature autodetection, this is temporary.
Until that is ready however, the flag is checked in GetSupportedProfiles in HW
encoders when called from renderer and is used to decide what can be added to
the list of supported profiles. In
VaapiVideoEncodeAccelerator::GetSupportedProfiles, the flag gates everything, so
no profiles will be added to the list if it's not on. Not having any profiles on
the list will result in that we'll not match any requested codecs in
RTCVideoEncoderFactory and VaapiVideoEncodeAccelerator will never be
instantiated.

   };
   renderer_cmd->CopySwitchesFrom(browser_cmd, kSwitchNames,
                                  arraysize(kSwitchNames));
 
   if (browser_cmd.HasSwitch(switches::kTraceStartup) &&
       BrowserMainLoop::GetInstance()->is_tracing_startup()) {
     // Pass kTraceStartup switch to renderer only if startup tracing has not
     // finished.
     renderer_cmd->AppendSwitchASCII(
         switches::kTraceStartup,
@@ skipping 1096 matching lines @@
 void RenderProcessHostImpl::GpuMemoryBufferAllocated(
     IPC::Message* reply,
     const gfx::GpuMemoryBufferHandle& handle) {
   DCHECK_CURRENTLY_ON(BrowserThread::UI);
   ChildProcessHostMsg_SyncAllocateGpuMemoryBuffer::WriteReplyParams(reply,
                                                                     handle);
   Send(reply);
 }
 
 }  // namespace content