[telemetry] Add WinRing0/MSR power monitor.

[telemetry] Add WinRing0/MSR power monitor.

This is a power monitor that reads the Intel RAPL MSRs to get energy measurements.
It uses a defunct open source DLL and kernel driver, WinRing0, to access the MSRs.
WinRing0 is a little wonky, and we have to install the kernel driver to the Python executable's directory.
Python must be run as Administrator for this to work.


BUG=336558
TEST=tools/telemetry/run_tests winring0

Committed: https://crrev.com/10d4df165c5ce09503738fdd0549b5287c00d713
Cr-Commit-Position: refs/heads/master@{#293277}

[dtu, 2014-09-03 23:44:05]

dtu@chromium.org changed reviewers:
+ tonyg@chromium.org

[tonyg, 2014-09-04 00:07:07]

lgtm

https://codereview.chromium.org/536243002/diff/20001/tools/telemetry/telemetr...
File
tools/telemetry/telemetry/core/platform/power_monitor/winring0_power_monitor.py
(right):

https://codereview.chromium.org/536243002/diff/20001/tools/telemetry/telemetr...
tools/telemetry/telemetry/core/platform/power_monitor/winring0_power_monitor.py:119:
class WinRing0PowerMonitor(power_monitor.PowerMonitor):
Should we consider calling this MsrPowerMonitor instead of WinRing0? The
WinRing0 part is kind of an implementation detail and we might even make this
code work on other platforms with another technique.

[dtu, 2014-09-04 00:59:20]

https://chromiumcodereview.appspot.com/536243002/diff/20001/tools/telemetry/t...
File
tools/telemetry/telemetry/core/platform/power_monitor/winring0_power_monitor.py
(right):

https://chromiumcodereview.appspot.com/536243002/diff/20001/tools/telemetry/t...
tools/telemetry/telemetry/core/platform/power_monitor/winring0_power_monitor.py:119:
class WinRing0PowerMonitor(power_monitor.PowerMonitor):
On 2014/09/04 00:07:07, tonyg wrote:
> Should we consider calling this MsrPowerMonitor instead of WinRing0? The
> WinRing0 part is kind of an implementation detail and we might even make this
> code work on other platforms with another technique.

Done. At first I felt like there wasn't enough shared code between platforms to
do that, but now I think we can make a clear separation and put the
platform-dependent code into platform_backend or something.

[dtu, 2014-09-04 00:59:28]

The CQ bit was checked by dtu@chromium.org

[commit-bot: I haz the power, 2014-09-04 01:02:03]

CQ is trying da patch. Follow status at
 https://chromium-status.appspot.com/cq/dtu@chromium.org/536243002/40001

[commit-bot: I haz the power, 2014-09-04 02:58:54]

The CQ bit was unchecked by commit-bot@chromium.org

[commit-bot: I haz the power, 2014-09-04 02:58:55]

Try jobs failed on following builders:
  android_clang_dbg_recipe on tryserver.chromium.linux
(http://build.chromium.org/p/tryserver.chromium.linux/builders/android_clang_d...)

[dtu, 2014-09-04 06:23:58]

The CQ bit was checked by dtu@chromium.org

[commit-bot: I haz the power, 2014-09-04 06:25:16]

CQ is trying da patch. Follow status at
 https://chromium-status.appspot.com/cq/dtu@chromium.org/536243002/40001

[commit-bot: I haz the power, 2014-09-04 06:59:32]

Committed patchset #3 (id:40001) as 1f745bba63c18483a8f3c58464bcb01940adb04b

[henrika (OOO until Aug 14), 2014-09-08 09:37:22]

A revert of this CL (patchset #3 id:40001) has been created in
https://codereview.chromium.org/547343003/ by henrika@chromium.org.

The reason for reverting is: Not sure but this CL was the only possible reason I
could find why we see so many issues on XP.

See http://build.chromium.org/p/chromium.win/builders/XP%20Tests%20%282%29 and 
http://build.chromium.org/p/chromium.win/builders/XP%20Tests%20%282%29/builds....

[commit-bot: I haz the power, 2014-09-10 03:30:32]

Patchset 3 (id:??) landed as
https://crrev.com/10d4df165c5ce09503738fdd0549b5287c00d713
Cr-Commit-Position: refs/heads/master@{#293277}