Revert "[Windows][Host][Logging] Adding EtwTraceConsumer class"

This reverts commit 341aef47f2373a68361f9dde477164917813a7e4.

Reason for revert: Tree-closing compilation failure. For example, https://ci.chromium.org/p/chromium/builders/ci/Win%20x64%20Builder/96007?
../../remoting/host/win/etw_trace_consumer.cc(119,11): error: use of undeclared identifier 'thread_checker_'
  DCHECK(!thread_checker_.CalledOnValidThread());
          ^
../../remoting/host/win/etw_trace_consumer.cc(125,11): error: use of undeclared identifier 'thread_checker_'
  DCHECK(!thread_checker_.CalledOnValidThread());

Original change's description:
> [Windows][Host][Logging] Adding EtwTraceConsumer class
>
> This CL adds the class which consumes the ETW events from
> Windows.  The class is fairly straight-forward but there
> is one interesting bit as the call to consumer events
> blocks us from running tasks on that thread.  In order to
> receive events and not block any of the existing threads,
> we create a new AutoThread which we use to listen for and
> handle events on.  When it is time to clean up, we unblock
> the listening thread by stopping the trace session.
>
> Future CLs will add the logic needed to parse the events
> and redirect the output to a new location (likely based on
> registry settings).  I've kept that out of this CL to keep
> its size on the smaller side.
>
> Bug: 1144185
> Change-Id: Ibf494251d0929a1741cb2796f26d69d258d96a64
> Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2515140
> Reviewed-by: Jamie Walch <jamiewalch@chromium.org>
> Commit-Queue: Joe Downing <joedow@chromium.org>
> Cr-Commit-Position: refs/heads/master@{#823596}

TBR=jamiewalch@chromium.org,joedow@chromium.org

Change-Id: Id754b4ac043c4ae34196e6df3e2b621b60673591
No-Presubmit: true
No-Tree-Checks: true
No-Try: true
Bug: 1144185
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2518104
Reviewed-by: Matthew Wolenetz <wolenetz@chromium.org>
Commit-Queue: Matthew Wolenetz <wolenetz@chromium.org>
Cr-Commit-Position: refs/heads/master@{#823605}
4 files changed
tree: 519aa9d42ed5b7c0a96244cd599a9272d7c2f2a7
  1. android_webview/
  2. apps/
  3. ash/
  4. base/
  5. build/
  6. build_overrides/
  7. buildtools/
  8. cc/
  9. chrome/
  10. chromecast/
  11. chromeos/
  12. cloud_print/
  13. codelabs/
  14. components/
  15. content/
  16. courgette/
  17. crypto/
  18. dbus/
  19. device/
  20. docs/
  21. extensions/
  22. fuchsia/
  23. gin/
  24. google_apis/
  25. google_update/
  26. gpu/
  27. headless/
  28. infra/
  29. ios/
  30. ipc/
  31. jingle/
  32. media/
  33. mojo/
  34. native_client_sdk/
  35. net/
  36. pdf/
  37. ppapi/
  38. printing/
  39. remoting/
  40. rlz/
  41. sandbox/
  42. services/
  43. skia/
  44. sql/
  45. storage/
  46. styleguide/
  47. testing/
  48. third_party/
  49. tools/
  50. ui/
  51. url/
  52. weblayer/
  53. .clang-format
  54. .clang-tidy
  55. .eslintrc.js
  56. .git-blame-ignore-revs
  57. .gitattributes
  58. .gitignore
  59. .gn
  60. .vpython
  61. .vpython3
  62. .yapfignore
  63. AUTHORS
  64. BUILD.gn
  65. CODE_OF_CONDUCT.md
  66. codereview.settings
  67. DEPS
  68. DIR_METADATA
  69. ENG_REVIEW_OWNERS
  70. LICENSE
  71. LICENSE.chromium_os
  72. OWNERS
  73. PRESUBMIT.py
  74. PRESUBMIT_test.py
  75. PRESUBMIT_test_mocks.py
  76. README.md
  77. WATCHLISTS
README.md

Logo 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.

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.