The webview instrumentation test shell does run in hardware mode now, after that CL from sievers you found. It uses a SurfaceView to fake the private android rendering APIs, so two caveats:
* It's different from how webview renderings in production, and is only used in tests to exercise hardware rendering code path.
* Only the first webview created in the shell is hardware accelerated. This really only applies to tests, since there is no UI to create more than one webview in the shell.
I've updated the wiki page to say "non-production" instead of "software".